From: David J. Braunegg
Subject: answer to eval-when bug in AKCL
Date:
Message-ID: <127532@linus.mitre.org>
I received a reply from Bill Schelter about my eval-when question:
Date: Thu, 3 Jan 91 11:20:42 -0600
From: ···@nicolas.ma.utexas.edu (Bill Schelter)
Only certain top level package operations get eval'd BEFORE the read of the
big constant vector. Because the make-package is hidden in a conditional
it is not getting read before the constant vector is read.
Putting all package information in a separate file loaded before your other
files, seems the only portable way of getting things to work in all systems.
In akcl if you did
(in-package "ABC")
(in-package "USER")
It would have been ok.
From: Jeff Dalton
Subject: Re: answer to eval-when bug in AKCL
Date:
Message-ID: <4007@skye.ed.ac.uk>
In article <······@linus.mitre.org> ···@arnold.mitre.org (David J. Braunegg) writes:
>
>I received a reply from Bill Schelter about my eval-when question:
>Only certain top level package operations get eval'd BEFORE the read of the
>big constant vector. Because the make-package is hidden in a conditional
>it is not getting read before the constant vector is read.
Wouldn't it work better of items were read one at a time, interleaved
with the evaluation of top-level forms, rather than being read all at
once as a vector? Then the package operations would have happened by
the time they were needed, just as they do when loading source.