Re: [clisp-list] Rationale for behaviour of EXT:EXPAND-FORM

[Sam S. <sd...@gn...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tobias C. Rittweiler wrote:
> Sam Steingold <sd...@gn...> writes:
> 
>>> P.S.: Is it already known that CLISP seems not to take top-levelness
>>> into account in EVAL-WHEN expressions with the deprecated situations
>>> symbols COMPILE &c? I.e.
>> http://clisp.podval.org/impnotes/eval-comp.html#eval-when
>> ...The situations EVAL, LOAD and COMPILE are deprecated by the [ANSI CL
>> standard], and they are not equivalent to the new standard situations
>> :EXECUTE, :LOAD-TOPLEVEL  and :COMPILE-TOPLEVEL in that they ignore the
>> top-level form versus non-top-level form distinction...
> 
> Ok. I just wondered because this non-conforming behaviour is retained

I think this is a useful extension: rather than have a deprecated way to
achieve something already available in a standard way, you can get
something extra.

> even when -ansi is passed.

http://clisp.cons.org/impnotes/ansi.html does not mention eval-when,
does it?

> Thanks for your reply,
you are welcome.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHfQWVPp1Qsf2qnMcRAvI5AKCtPz9Kc7vaB0iuQdrVASINRBF4VACgrWdz
n0XmizYBWg9Dm728yhC6zRA=
=+a45
-----END PGP SIGNATURE-----