[Cuis-dev] #forceChangesToDisk

[Phil B]

Changeset attached.  I was reading a thread on squeak-dev and this subject
came up re: the current implementation of #forceChangesToDisk being fairly
pointless (i.e. modern OSes will see what's being done and effectively
ignore the attempt to force the write by closing and re-opening)  But let's
say that isn't the case: it's not the 90's anymore and we're not running
Win 3.x/9x or OS 7-9 where a VM crash could and would bring down your
system.   On top of that, the vast majority of us are running with
journaling filesystems these days so even in a worst-case scenario, the old
behavior adds no value that I can see. (i.e. if the write can't be
ensured/recovered at the OS level, it's unlikely that the old code is going
to do anything to help)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cuis.st/mailman/archives/cuis-dev/attachments/20190829/068109b9/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 3853-forceChangesToDisk-enough-already-its-2019-PhilBellalouna-2019Aug28-23h07m-pb.1.cs.st
Type: application/octet-stream
Size: 390 bytes
Desc: not available
URL: <http://lists.cuis.st/mailman/archives/cuis-dev/attachments/20190829/068109b9/attachment.obj>