Re: Issue DEFCONSTANT-NOT-WIRED

[David N Gray <Gray@DSG.csc.ti.com>]

> CLtL says that a change to a DEFPARAMETER'ed variable should be
> considered a change to the program.  There are lots of other
> situations where making a change to the program might cause situations
> that "are an error", such as redefining a function as a macro.
> Although CLtL does not explicitly allow or disallow it, some (many?)
> implementations choose to issue warnings in such cases.  Therefore I
> think it is legitimate both for users to use DEFPARAMETER for
> situations where an error may result if the variable is changed, and
> for implementations to be allowed (but not required) to issue warnings
> about changing the values of DEFPARAMETER'ed variables.

One might construe CLtL to mean that, but it is too big of an
incompatible change from current practice to be seriously considered.