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 buffering, no encoding, no text conversion. And so clean the usage of MultiByteCharacterMaybeTextMaybeBufferedMaybeBinaryMaybeReadMaybeWrite streams. Buffering, encoding, convertion to text and other facilities can be obtained by using the already provided Zn* facilities: - ZnBufferedRead/WriteStream - ZnEncodedStream and so on. Nice thing: the Zn* thingys are well tested, documented, and already used for socket streams. We can reuse them for files for free :) Guille -------- Original Message --------
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 shoulders and just had to trust the author.
----- Cheers, Sean -- View this message in context: http://forum.world.st/could-we-discuss-19006-tp4913965p4914079.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.