At 09:05 AM 8/13/98 -0400, you wrote:
[snip]
>I run Squeak under Linux, and I've
>found that sometimes when I read files with the file browser there are no
>carriage returns at the end of each line.  I filein'ed the CrLf fix on the
>UIUC ftp site, and after a bit of hacking to get it to work I STILL find
>that some files have no carriage returns when read.  Am I missing something
>important?
[snip]

Squeak seems to use a number of characters to indicate line termination.
I've found Cr, CrLf, and Lf.  The predominate convention on DOS/Windows x86
is CrLf and (I think) UNIX is Lf.

I briefly considered modifying Squeak to use Cr internally and the native
platform externally, but am in the middle of a large project.  Trace though
how code is filed in/out and also how it is retrieved/stored in the source
and changes files and you'll see what's happening.  A code file you may have
gotten from a Windows Squeak may use Cr and you need Lf on your UNIX Squeak.
The #next, #nextPut:, #nextChunk, #getSource, . . . are the methods that
need to translate from/to the internal and the native platform external
line termination conventions.

I guess I'll do it later so its 3,692th on my list.  Or is it 3,693th after
the application to manage my list of thing to do.

--
Richard A. Harmon          "The only good zombie is a dead zombie"
harmonra at webname.com           E. G. McCarthy