[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


re: My understanding of JonL's comments on this were that Lucid only does
    compile-time evaluation of the value form when the DEFCONSTANT appears
    at top-level.

No, this isn't correct.  Lucid's DEFCONSTANT is implemented as a very
ordinary macro which expands into an eval-when(eval compile load); so
the non-top-level behaviour depends on the treatment of eval-when at
non-top-level.  Lucid's current behaviour for eval-when is not too far 
off from the cl-compiler proposal, but of course it doesn't match

-- JonL --