October 2017 - cmucl-imp - mailman3.common-lisp.net

[cmucl-imp] Release 21c
by Raymond Toy 28 Oct '17

28 Oct '17

We are pleased to announce CMUCL Release 21c. Binaries will be available soon. The release notes can be found here: https://gitlab.common-lisp.net/cmucl/cmucl/blob/master/src/general-info/rel… -- Ray

1 0

Re: [cmucl-imp] Compiling files with traditional Mac EOL in CMUCL
by Raymond Toy 12 Oct '17

12 Oct '17

On Wed, Oct 11, 2017 at 2:13 AM, Chun Tian <binghe.lisp(a)gmail.com> wrote: > > Hi Raymond, > > I’m so sorry, but somehow I've never received your previous email, that’s why I didn’t reply. > > After my initial post for this issue, I actually received a private mail from James Anderson (the author of CL-XML and many other utilities), the following reader macro, which allows the correct handling of Mac EOL in every CL implementation: > > (defun |universal-comment-reader| (stream char) > (declare (ignore char)) > (loop (case (read-char stream nil nil) > ((#\return #\linefeed nil) (return)) > (t ))) > (values)) > > (set-macro-character #\; '|universal-comment-reader|) > > But any way, I just tried (compile-file "foo.lisp" :external-format '(:utf8 :cr)), and I confirm it also works. I don’t know how to let ASDF compile files with additional parameters in COMPILE-FILE, but anyway there should be a solution (for CMUCL, maybe also SBCL?), it’s still a problem for some other CL implementations. Thanks for letting me know; glad it works for you. As for asdf, you can define your own classes and operations. I'm not an expert on this, but here is an example from f2cl (that Fare basically updated for me): https://gitlab.common-lisp.net/f2cl/f2cl/blob/master/src/f2cl-asdf.lisp. I think the relevant part is the perform method where you can specify options when compiling. > > Regards, > > Chun Tian > > > Il giorno 11 ott 2017, alle ore 05:37, Raymond Toy <toy.raymond(a)gmail.com> ha scritto: > > > >>>>>> "Raymond" == Raymond Toy <toy.raymond(a)gmail.com> writes: > > > >>>>>> "Chun" == Chun Tian <(binghe)" <binghe.lisp(a)gmail.com>> writes: > > Chun> OK, sorry, I carefully checked again. SBCL also doesn't support compiling > > Chun> files with Mac EOLs. Clozure CL, which I confirmed now, indeed support Mac > > Chun> EOLs. > > > > Chun> For the reason I can't convert the source files to UNIX line endings, > > Chun> there's a Lisp function for parsing (multi-line) literal strings defined in > > Chun> source files with MAC line endings. It seems that, #\Newline was mapped to > > Chun> "\r" in MCL, thus Lisp forms like (position #\Newline string) doesn't work > > Chun> in MCL for other line endings, especially the UNIX endings, because in this > > Chun> case there would be no #\Newline in the string at all! > > > > Raymond> I haven't tried this out in a long time, but maybe something like this > > Raymond> will work: > > > > Raymond> (compile-file "foo.lisp" :external-format '(:utf8 :cr)) > > > > Did you get a chance to try this out? > > > > -- > > Ray > > > > _______________________________________________ > > cmucl-imp mailing list > > cmucl-imp(a)cmucl.cons.org > > https://lists.zs64.net/mailman/listinfo/cmucl-imp > -- Ray

1 0

[cmucl-imp] Snapshot 2017-10
by Raymond Toy 11 Oct '17

11 Oct '17

The 2017-10 snapshot has been tagged. Binaries will be uploaded soon ot the usual place. The release notes can be found at https://gitlab.common-lisp.net/cmucl/cmucl/tags/snapshot-2017-10 and also on the wiki: https://gitlab.common-lisp.net/cmucl/cmucl/wikis/Home -- Ray

1 0

[cmucl-imp] Compiling files with traditional Mac EOL in CMUCL
by Chun Tian (binghe) 11 Oct '17

11 Oct '17

Hi, 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. Is this a CMUCL bug that can be fixed? Regards, Chun Tian -- Chun Tian (binghe) University of Bologna (Italy)

3 4