[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gcl-devel] Re: "COMMON-LISP" package in GCL 2.5.0

From: Matt Kaufmann
Subject: [Gcl-devel] Re: "COMMON-LISP" package in GCL 2.5.0
Date: Sat, 10 Aug 2002 10:33:50 -0500 (CDT)

Thanks.  Will COMMON-LISP and LISP ultimately be the same package?  That is,
will this form return true?

(eq (find-package "LISP") (find-package "COMMON-LISP"))

Thanks --
-- Matt
   Cc: address@hidden, address@hidden
   From: Camm Maguire <address@hidden>
   Date: 10 Aug 2002 10:28:14 -0400


   Matt Kaufmann <address@hidden> writes:

   > Hi --
   > The COMMON-LISP package exists in GCL 2.5.0 but is only populated by 
   > and LISP::NIL.  I'm surprised that although the COMMON-LISP package 
exists, it
   > refers to a package different from the LISP package.

   Yes, we are working toward an ansi compliant compier, but this will
   take some time!  I should refrain from inserting the common-lisp
   package in the default configuration, which you are apparently using,
   to avoid confusion.  But if you want to see the state so far, you can
   ./configure --enable-ansi, and you will get an image with clcs and pcl
   compiled in.  Still needs considerable work.  And yes, this will be
   changing as gcl develops.

   Take care,

   >   GCL (GNU Common Lisp)  Version(2.5.0) Fri Aug  9 15:33:00 CDT 2002
   >   Licensed under GNU Library General Public License
   >   Contains Enhancements by W. Schelter
   >   >(do-symbols
   >     (sym "COMMON-LISP")
   >     (format t "~s~%" (list sym (eq sym (intern (symbol-name sym) 
   >   (T T)
   >   (NIL T)
   >   NIL
   >   >
   > Will this change in future GCL releases?  I've got a workaround for my
   > purposes; I include it below in case you're interested or have comments.  
   > the way, I really appreciate the availability of GCL and have successfully 
   > the ACL2 regression suite (which takes about 3 hours on a fast machine) 
   > GCL 2.5.0 built on Debian 3.0.
   > (let ((lisp-pkg (find-package "LISP")))
   >   (if lisp-pkg
   >       (let ((cl-pkg (find-package "COMMON-LISP")))
   >         (cond
   >          ((and cl-pkg (eq cl-pkg lisp-pkg)))
   >          (t
   >           (when cl-pkg ; but by the test above, cl-pkg is not lisp-pkg
   >             #-gcl
   >             (error "This Lisp is unsuitable for ACL2, because the ~
   >                     COMMON-LISP~% package is defined but is not the LISP ~
   >                     package.")
   >             #+gcl
   > ; GCL 2.5.0 has a "COMMON-LISP" package that is initially populated only 
   > ; LISP::T and LISP::NIL.  It seems safe to move any GCL COMMON-LISP 
package out
   > ; of the way before we make "COMMON-LISP" a nickname for "LISP".
   >             (rename-package "COMMON-LISP" "COMMON-LISP-renamed"))
   >           (let ((old-name (package-name lisp-pkg)) ; reuse old name, 
   >                 (old-nicknames (package-nicknames lisp-pkg)))
   >             (rename-package "LISP"
   >                             old-name
   >                             (cons "COMMON-LISP" old-nicknames))))))))
   > Thanks --
   > -- Matt Kaufmann

   Camm Maguire                                         address@hidden
   "The earth is but one country, and mankind its citizens."  --  Baha'u'llah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]