On Mon, Apr 30, 2001 at 12:59:50PM -0400, Sam Steingold wrote:
[ from a discussion on clocc-devel ]
> > In ANSI mode? Because, as you quite rightly pointed out, clisp in
> > non-ANSI mode doesn't do logical-pathnames in quite the way that
> > defsystem might expect.
> I always wrap logical pathnames in explicit `translate-logical-pathname'
> calls, so I do not need -a.
> > This is latest CVS, which for some as yet unfathomed reason seems to
> > come up in ansi mode by default here.
> this is not the case.
> if you read the CHANGES.LOG file, as you should have,
Yup. Missed that one.
> you would have
> known that :cltl2 has been replaced with :ansi-cl in the features, which
> doesn't mean that all the "-a" settings are in place now by default.
That's a pity, since :ansi-cl can no longer be used to test for ANSI
Is this really what you meant to do? Because it seems roughly as
broken by design as "Ooo, uppercase is ugly; I think we'll break
user-level code in an incompatible way."
Jesus College, Cambridge, CB5 8BL +44 1223 524 842
http://www-jcsu.jesus.cam.ac.uk/~csr21/ (defun pling-dollar
(str schar arg) (first (last +))) (make-dispatch-macro-character #\! t)
(set-dispatch-macro-character #\! #\$ #'pling-dollar)
From: Sam Steingold <sds@gn...> - 2001-05-04 22:25:54
> * In message <20010430183632.A29624@...>
> * On the subject of "Re: defsystem.lisp"
> * Sent on Mon, 30 Apr 2001 18:36:32 +0100
> * Honorable Christophe Rhodes <csr21@...> writes:
> > doesn't mean that all the "-a" settings are in place now by default.
> That's a pity, since :ansi-cl can no longer be used to test for ANSI
> conforming implementations.
CLISP _is_ a mostly conforming implementation, and if you think you
depend on the ANSI features disabled by default in CLISP (you are
probably wrong thinking so), you can add
#+clisp (setq ext:*ansi* t)
in your preamble (or, better yet, turn the features on individually).
> Is this really what you meant to do? Because it seems roughly as
> broken by design as "Ooo, uppercase is ugly; I think we'll break
> user-level code in an incompatible way."
you were not supposed to think that #+ansi-cl tests for various ANSI
variables. It was a mistake on my part to give you a reason to think
It is a violation of the ANSI standard to have both #+ansi-cl and
#+cltl2 (see CLHS for *FEATURES*).
#+ansi-cl indicates that CLISP "purports to conform" to the ANSI CL
standard. Yes, CLISP does deviate from the ANSI CL standard on certain
issues (which we, the implementors, think ANSI got wrong - and on some
of these issues some members of X3J13 agree that the standard is
brain-damaged). If you depend on there particular features, please run
CLISP with the '-ansi' flag or dump you images or set EXT:*ANSI* to T.
Sam Steingold (http://www.podval.org/~sds)
Support Israel's right to defend herself! <http://www.i-charity.com/go/israel>
Read what the Arab leaders say to their people on <http://www.memri.org/>
Those who don't know lisp are destined to reinvent it, poorly.