[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
What does LOAD use for read table & package?
- To: "David A. Moon" <Moon@SCRC-STONY-BROOK.ARPA>
- Subject: What does LOAD use for read table & package?
- From: "Scott E. Fahlman" <Fahlman@C.CS.CMU.EDU>
- Date: Fri, 28 Feb 1986 00:40:00 -0000
- Cc: common-lisp@SU-AI.ARPA
- In-reply-to: Msg of 27 Feb 1986 14:15-EST from David A. Moon <Moon at SCRC-STONY-BROOK.ARPA>
- Sender: FAHLMAN@C.CS.CMU.EDU
I believe that the only viable possibility for LOAD of a compiled file
is to bind *PACKAGE* to the same value that it had when the file was
compiled. This means that the compiler must transmit this information
to the loader in some way. If there are SETQs of *PACKAGE* in the
source file (perhaps disguised as IN-PACKAGE), then they should do the
same thing at load time as they did at compile time.
For those of us who want to learn from your experience, could you
elaborate a bit on the above pronouncement? Why is it a good idea to
bind *PACKAGE* to the compile-time value, rather than using what is
current at load time? What if the compile-time package doesn't exist at