Hello,

At Fri, 30 Jul 2004 13:49:55 -0400 ,
lex at cc.gatech.edu wrote:
> 
> Ned Konz <ned at bike-nomad.com> wrote:
> > All previously-existing code expected that text streams would return 
> > Characters that had a 1:1 mapping to the bytes in the file.
> 
> Actually, there are CrLfFileStream and TextFile, both of which do not
> necessarily give 1:1 mappings.  Those of us that use one of these
> classes think your discussions about CR versus LF are amusing.  Those of
> you who do not use these classes think our complaints about the
> incorrect 1:1 assumption are amusing.  
> 
> Anyway, the point is that those of us who sufered through using
> CrLfFileStream in a 1:1-assuming world, have already managed to get some
> things in Squeak fixed over time.  Also, I can tell you that it's not
> too bad to just switch over like this.  It's easy to fix the individual
> broken cases; it is just frustrating that the upstream developers
> frequently don't really care.

  This is a good argument and I agree with it.  The proper text/binary
use, most of the Squeak code does today, is the way to go.

  Just FYI, but CrLfFileStream is integrated with MultiByteFileStream
now.  Sending new to CrLfFileStream results in a MultiByteFileStream
with a flag set.

-- Yoshiki