home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!math.fu-berlin.de!ira.uka.de!scsing.switch.ch!univ-lyon1.fr!ghost.dsi.unimi.it!rpi!usc!howland.reston.ans.net!spool.mu.edu!agate!stanford.edu!apple!cambridge.apple.com!bill@cambridge.apple.com
- From: bill@cambridge.apple.com (Bill St. Clair)
- Newsgroups: comp.lang.lisp.mcl
- Subject: Re: Porting to MCL: Package problems
- Message-ID: <9301281503.AA22652@cambridge.apple.com>
- Date: 28 Jan 93 16:05:01 GMT
- Sender: owner-info-mcl@cambridge.apple.com
- Lines: 18
- Approved: comp.lang.lisp.mcl@Cambridge.Apple.C0M
-
- At 11:24 1/28/93 +0000, Ranson wrote:
- >IN-PACKAGE was changed incompatibly in the 2nd version of Common Lisp. The
- >problem is there, not in MCL. In this version, the argument of IN-PACKAGE is
- >not evaluated. To increase portability, use keywords:
- >
- >(in-package :tms)
- >
- > Daniel.
-
- MCL comes with a CLtL1 compatibility package. It doesn't make everything
- work exactly as in CLtL1, but it does provide the LISP & USER packages
- (CLtL2 renames these to COMMON-LISP & COMMON-LISP-USER), and provides
- CLtL1 versions of LISP:IN-PACKAGE, LISP:FUNCTIONP, and LISP:CHAR-BITS &
- friends. You might try evaluating the following two forms before loading
- your code:
-
- (require "LISP-PACKAGE")
- (in-package :user)
-