[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
EXPORT after USE
- To: common-lisp@su-ai
- Subject: EXPORT after USE
- From: David.Dill@CMU-CS-A (L170DD60)
- Date: Tue, 24 May 1983 19:36:00 -0000
It is really not clear to me why the effects of EXPORT after USE have to
be the same in all common lisp implementations. It is not hard to
imagine debugging tools that can track down and help resolve symbol
conflicts caused by this in various ways for various implementations.
The proposed scheme is not the only way to do this.
I'm not complaining about this because I want to implement a "copy"
system in Spice Lisp. It just seems to me that there is a natural
division between a common subset of the current proposal requiring
that all symbols be exported before the package is used, and the
wizard-level hacking necessary during development, which can be
implementation-dependent (it is clearly not going to be possible to
move code to another dialect of common lisp when it would take
two or three weeks to rebuild it from sources).
This seems to be consistent with the principles just applied to the
error system revisions.