[Cuis-dev] [Integrated] Re: #forceChangesToDisk

[Andres Valloud]

I meant today.  Nevertheless, unfortunately the large audience that 
consumes flaky software does not demand quality implementations, even if 
it is to their own detriment.

On 9/16/19 19:04, Phil B wrote:
> You're kidding, right? (re: not being able to trust systems in the 90's)
> 
> On Mon, Sep 16, 2019 at 9:41 PM Andres Valloud via Cuis-dev 
> <cuis-dev at lists.cuis.st <mailto:cuis-dev at lists.cuis.st>> wrote:
> 
>     On 9/16/19 17:45, Phil B wrote:
>      > It's the flushing of the buffer (which is still there) that is the
>      > important bit.  That signals to the OS 'OK, make sure this data
>      > written'.
> 
>     Exactly :).
> 
>      > The rest of the code was a hack to basically try to force the
>      > OS to do the write immediately.  This used to work[2], but per the
>      > conversation on squeak-dev, no longer does.  My position is that
>     even if
>      > it still does work in some cases, it's a hack that was based on a
>     set of
>      > assumptions that are no longer valid today.
> 
>     Yeah, what's the deal with asking the OS to flush the file and then not
>     trusting it did its job?
> 
>     Andres.
>     -- 
>     Cuis-dev mailing list
>     Cuis-dev at lists.cuis.st <mailto:Cuis-dev at lists.cuis.st>
>     https://lists.cuis.st/mailman/listinfo/cuis-dev
>