Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
From: Bruno Haible <haible@il...> - 2000-04-19 21:03:08
Don Cohen asks:
> (defpackage "SSS" (:use "LISP" #+clisp "CLOS") ...)
> I need that clos in order to use the clos stuff in my package.
> Why is that?
So that you can use package "PCL" instead of "CLOS" if you like.
> Shouldn't these things be exported from the lisp package?
Not in CLtL1.
If you want to assume ANSI CL behaviour, then you should better use
package "COMMON-LISP" instead of "LISP", because ANSI-CL makes no
claims about package "LISP" but standardizes package "COMMON-LISP".
From: Hannu Koivisto <azure@ik...> - 2000-04-19 21:19:03
donc@... (Don Cohen) writes:
| (defpackage "SSS" (:use "LISP" #+clisp "CLOS") ...)
What is going on here is probably that you are confusing LISP
package with COMMON-LISP package, which is especially easy to do if
you have been using CMUCL where COMMON-LISP package has a
non-standard (in a sense that it is not required to have such
nickname; I think the standard allows it to have additional
nicknames, though, so what CMUCL does is ok) nickname LISP in
addition to required nickname CL. In CLISP there is a completely
separate package called LISP that provides CLtL1/CLtL2 stuff
excluding CLOS. So what you probably want to do is to say:
(defpackage :sss (:use :common-lisp) ...)