(EOL CR), (EOL CRLF)

[MASINTER.PA]

I fixed it in Interlisp-10 so that the EOL mode is settable on
a per-file basis, as one of the MACHINE.DEPENDENT.PARAMETERS using
a (EOL type) element in the list. (I was in search of why I couldn't
load files directly from Phylum using PUPFTP, and it was because 
Interlisp-10 was trying to gobble a LF after a CR and gobbled too
much.)

Is there any good reason why Interlisp-D shouldn't support this too?
I imagine the EOL mode should be read/settable via GETFILEINFO, and
perhaps #EOLCHARS should be a GETFILEINFO parameter too...

Larry