On Tue, Dec 12, 2000 at 09:17:09PM +0100, martin@... wrote:
> Daniel Barlow wrote:
> > Odd. I'm using 2.4.19 as well :
> > :; lisp
> > ; Loading #p"/home/dan/init.lisp".
> > CMU Common Lisp release x86-linux 2.4.19 8 February 2000 build 455, running on protege
> > [...]
> > * (find-package "LISP")
> > #<The COMMON-LISP package, 1556/3910 internal, 989/1242 external>
> > * (describe 'common-lisp::*already-evaled-this*)
> > *ALREADY-EVALED-THIS* is an internal symbol in the COMMON-LISP package.
> > It is a special variable; its value is NIL.
> Yes. I get the same.
> Really odd. Perhaps I'm missing something very obvious, but what I get
> with the
> modifications you described is (in first genesis I think):
> [relevant portions]
> caught WARNING
> This variable is undefined:
> ; caught 1 WARNING condition
> ; caught 9 STYLE-WARNING conditions
> obj/from-xc/code/lisp-stream.lisp-obj deleted
> Error in batch processing:
> Error in function COMPILE-STEM
> This may not be related to *already-evaled-this* at all, though.
I think at least some of the problems weren't related to
*ALREADY-EVALED-THIS*, but were instead because I removed EVAL-WHEN
wrappers around DEFCONSTANT, and CMU CL doesn't like that, and
furthermore likes to issue full WARNINGs (not just STYLE-WARNINGs)
about variables which are undefined at compile time.
I hacked on these problems until I got the system to build under
cmucl-2.4.19 on my machine here. The result has been checked into CVS
as version 0.6.9.7.
William Harold Newman <william.newman@...>
PGP key fingerprint 85 CE 1C BA 79 8D 51 8C B9 25 FB EE E0 C3 E5 7C