CLISP READ-CHAR reads bytes 10 and 13 as #\Newline:
Is it possible to read them differently?
Logged In: YES
I don't see any compatibility issues.
any text stream knows its preferred encoding, so #\Newline is never written as its char-code.
the woe32 editing of fas files issue is fairly rare, and the only problem there would occur if there are embedded newlines in strings.
this should be addressed by always quoting CR&LF in all strings, symbols and package names in compiled files (we know that we are reading from a compiled file when stream is the same as *load-file*).