Some aside-answers on the issue:
The AbstractFileStream and its two childs are not "a stream library
implementation" but low level streams that implement the primitives to
talk to files.
And their purpose is to provide a clean implementation of binary file
streams that implement no
stepharo wrote
> Note that I'm not against. I just want to understand.
Me too. I looked over the issue, and it seemed one would already have to
understand the issue very well. I wished there was more explanation about
the problem and why the solution was a good one. In the end, I shrugged my
, with sync(2) or
fsync(2).
(but on Windows they're implemented identically)
Sent: Saturday, September 03, 2016 at 3:34 PM
From: stepharo <steph...@free.fr>
To: "Pharo Development List" <pharo-dev@lists.pharo.org>
Subject: [Pharo-dev] could we discuss 19006
Hi
m: stepharo <steph...@free.fr>
> To: "Pharo Development List" <pharo-dev@lists.pharo.org>
> Subject: [Pharo-dev] could we discuss 19006
>
> Hi guys
>
> The change 19006 is adding a lot of streams AbstractBinaryStream and I
> do not really get the visi
Hi guys
The change 19006 is adding a lot of streams AbstractBinaryStream and I
do not really get the vision.
Note that I'm not against. I just want to understand.
Do we add these and remove some old ones?
What is sync?
Ideally I would like to throw away all the streams and use xtreams
