🚀 go-pugleaf

In article <328@tekchips.UUCP> willc@tekchips.UUCP (Will Clinger) writes:
>I don't know how Common Lisp stands on this issue.  To judge by the
>program-analyzing algorithm on page 57 of Steele's "Common Lisp: the
>Language", the names of special forms are reserved when they appear
>in the car of a form, but I don't know what happens when they appear
>in other contexts.

I think the Common Lisp definition describes the reserved status of
these symbols by saying that they cannot be given new function
definitions.  The user is perfectly free to change the value cell,
package cell, and property list.

>  Common Lisp distinguishes between special forms
>and macros, however, and it is clear that macro names can be shadowed
>because they live in the "function" environment, which is lexical
>except for some special treatment of the global function environment.
>On the other hand, implementations of Common Lisp are explicitly
>allowed to implement certain macros as special forms, and I don't
>know how their names can be simultaneously reserved (because they
>are special forms) and shadowable (because they are macros).  I'd
>appreciate any pointers to authoritative explanations of these two
>matters.

No problem, the compiler/interpreter merely has to check whether the
user has redefined the function binding before using the built-in
definition of the macro.  Only the special forms listed in the language
definition are required to be reserved.  When it says that
implementations may implement macros as special forms, it is actually
saying that they are allowed to skip the explicit macro-expansion step,
i.e. interpret the macro in whatever special way they interpret special
forms.
-- 
    Barry Margolin
    ARPA: barmar@MIT-Multics
    UUCP: ..!genrad!mit-eddie!barmar