[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Where Pure Common Lisp lives
- To: "David A. Moon" <Moon@SCRC-STONY-BROOK.ARPA>
- Subject: Where Pure Common Lisp lives
- From: "Scott E. Fahlman" <Fahlman@C.CS.CMU.EDU>
- Date: Fri, 23 May 1986 18:57:00 -0000
- Cc: COMMON-LISP@SU-AI.ARPA
- In-reply-to: Msg of 23 May 1986 13:55-EDT from David A. Moon <Moon at SCRC-STONY-BROOK.ARPA>
- Sender: FAHLMAN@C.CS.CMU.EDU
If you want to make a package that uses the same exported symbols as the
user package, you do (MAKE-PACKAGE "MY-VERY-OWN-PACKAGE"
:USE (PACKAGE-USE-LIST (PACKAGE "USER"))).
I don't see any reason why we need to add a new language feature that
duplicates this. I agree completely with the people who say that the default
for :USE in MAKE-PACKAGE should be the portable default, not the full
Hmmmm...is USER allowed to start up with random local extensions in it,
or is it supposed to inherit ONLY from the LISP package, which is now
pure Common Lisp? How have people been reading this? Part of my
objection to making LISP pure was because I assumed that this meant USER
had to be pure as well, which means that we need another standard place
to look for the default local environment.