[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Encodings.

This page is part of the web mail archives of SRFI 52 from before July 7th, 2015. The new archives for SRFI 52 contain all messages, not just those from before July 7th, 2015.

At Sun, 15 Feb 2004 23:18:13 -0500, Paul Schlie wrote:
> Just to close the issue out in my mine, looked at the reader code, it seems
> to strip \r characters following \n characters, treating the sequence as a
> single \n character, allowing it to conveniently read generic DOS'ish files,
> but writes /n characters to terminate lines, which older Mac C compilers
> substitutes with an LF ironically I recall. (so you've got basically a
> universal reader for binary based port text, authored using one of three
> typical newline conventions, which would seem to be apparently adequate).

In fact, it is just the read-line primitive that does that "magic" to
treat a variety of eol annotations as ends of lines. If you use
read-char, you'll still precisely what's there. That's the best
compromise we (actually mostly just Matthew Flatt) found, after some
non-trivial searching.

Sorry for leading us down this non-extended-char-sets-related path.