[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: issue COMPILE-ENVIRONMENT-CONSISTENCY, version 4
- To: firstname.lastname@example.org
- Subject: Re: issue COMPILE-ENVIRONMENT-CONSISTENCY, version 4
- From: masinter.pa@Xerox.COM
- Date: 15 Mar 89 05:00 PST
- Cc: masinter.pa@Xerox.COM
- In-reply-to: email@example.com (Sandra J Loosemore)'s message of Mon, 13 Mar 89 15:50:07 -0700
I think I know what this means, but I worry that the language isn't precise
enough and we will have some problems with misreading. This leaves it an
"editorial" issue, I suppose, but I don't envy the job of the editor. Just
(b) In conforming code, variables that are intended to be bound
specially must be declared SPECIAL in the compiletime environment
before any bindings of that variable are processed by the compiler.
The compiler must treat any binding of an undeclared variable as a
The terms I'd wish defined are
"intended" - by whom?
"declared... in the compiletime environment before"
- probably you mean that the compiler must process an appropriate
DECLARE or PROCLAIM, not that such a DECLARE or PROCLAIM actually
be evaluated. Probably "before" means either chronologically or
in some appropriate lexically enclosing scope.
"processed by the compiler"
- probably "processed" doesn't include READ.