Re: Compiling files with traditional Mac EOL in CMUCL

"Chun Tian (binghe)" <[email protected]> wrote:
>I'm surprised that CMUCL doesn't support lisp files with traditional Mac
>EOL, that is, lines are separated by a single '\r', there's no `\n` at all.
>
>Here is my recent story: I'm porting some old Lisp code originally
>developed in Macintosh Common Lisp 4.2. All files use Mac EOL. I can't
>convert them to Unix EOL, because that will break some Lisp functions in
>MCL.  The problem when compiling these files in CMUCL is, if there's a
>line-based comment starting with semicolon ";", CMUCL compiler will
>consider all the rest code in the file is at the "same" line, thus they're
>all commented!  It looks like CMUCL has correctly compiled the file
>(because there's no warning at all), but actually it compiled almost
>nothing.
>
>SBCL and LispWorks have no such issues, I can imagine Clozure CL must
>natively support Mac EOL.

Are you sure that SBCL is doing what you want ? The definitions of
read-comment look very similar in CMUCL and SBCL.

I also don't understand why you can't convert the source files to UNIX
line endings.


_______________________________________________
cmucl-imp mailing list
[email protected]
https://lists.zs64.net/mailman/listinfo/cmucl-imp