[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue DEFCONSTANT-NOT-WIRED
- To: firstname.lastname@example.org (Sandra J Loosemore)
- Subject: Re: Issue DEFCONSTANT-NOT-WIRED
- From: David N Gray <Gray@DSG.csc.ti.com>
- Date: Fri, 7 Oct 88 14:19:38 CDT
- Cc: CL-Compiler@sail.stanford.edu
- In-reply-to: Msg of Fri, 7 Oct 88 10:59:46 MDT from email@example.com (Sandra J Loosemore)
- Sender: GRAY@Kelvin.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.