[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: issue CONSTANT-CIRCULAR-COMPILATION, version 7
- To: firstname.lastname@example.org
- Subject: Re: issue CONSTANT-CIRCULAR-COMPILATION, version 7
- From: masinter.pa@Xerox.COM
- Date: 16 Mar 89 06:38 PST
- In-reply-to: email@example.com (Sandra J Loosemore)'s message of Mon, 13 Mar 89 09:19:28 -0700
I think the 'error terminology' is probably misapplied in the use
"State that the consequences are undefined if an object containing a
circular reference appears as a constant to be compiled."
We speak of "... the consequences are undefined... " in reference to the
consequences of execution of a particular construct during the normal
evaluation process, either in interpreted or compiled code.
The appearance of the object itself does not have undefined consequences, I
don't think. Is it the consequence of attempting to invoke COMPILE or
COMPILE-FILE that is undefined, or is it the consequence of attempting to
execute the result of the COMPILE or COMPILE-FILE that you wish to leave
If I say
(defun frob ()
(when nil #1=(nil . #1#)))
are the consequences undefined?
Maybe I'm just quibbling.