[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[no subject]
- To: KRONJ at MIT-MC
- From: Robert W. Kerns <RWK at MIT-MC>
- Date: Sun, 14 Jun 81 23:12:00 GMT
- Cc: BUG-LISP at MIT-MC, WGD at MIT-MC, RLB at MIT-MC
- In-reply-to: The message of 12 Jun 81 21:33-EDT from David Eppstein <KRONJ at MIT-MC>
- Original-date: Sunday, 14 June 1981, 19:12-EDT
Date: 12 June 1981 21:33-EDT
From: David Eppstein <KRONJ at MIT-MC>
To: BUG-LISP at MIT-MC
What is EVAL-ORDERED* and why does it have an autoload property of
((LISP) AUTOLOAD FASL), which upon not being found gives me an IO-LOSSAGE
error when I try to load my file ((AR1 GUEST2) GENE >).
As far as I can tell, it is in the middle of a DEFVST when it has that problem.
EVAL-ORDERED* is an internal function which tries to keep the evaluated
parts of a SETF spec evaluated in left-to-right order despite the fact
that some things which SETF expands into take their arguments in funny
orders. It had an absurd autoload property because JONL's mind wandered
while he was changing the file to use his new DEF-OR-AUTOLOAD macro.
I have fixed this.