Re: package "CLOS" not found

The code uses features of the CLOS MOP here. Since the CLOS MOP is not
part of ANSI Common Lisp, the symbols that name CLOS MOP functionality
cannot be part of the common-lisp package (ANSI Common Lisp forbids such
extensions of the common-lisp package). Therefore, implementations have
to be put these symbols in another package. Unfortunately, the CLOS MOP
doesn't specify a package name for its symbols, so every implementation
has its own idea where to put the package. Typical names are "CLOS",
"MOP", "CLOS-MOP" or some more implementation-specific name.

A good way to find the right package is to do an (apropos "CLASS-SLOTS")
(or an apropos on some other CLOS MOP identifier), and/or check out the
documentation of the respective implementation. Another way is to use
the Closer to MOP library which, apart from fixing some compatibility
issues, provides a common package name for all implementations. See
http://common-lisp/project/closer


Pascal

Thanks, I mean thanks a lot.
Wow :).
dg
--
?If we knew what it was we were doing, it would not be called research,
would it??
--Albert Einstein
.

Relevant Pages

  • Re: package "CLOS" not found
    ... part of ANSI Common Lisp, the symbols that name CLOS MOP functionality cannot be part of the common-lisp package. ... Unfortunately, the CLOS MOP doesn't specify a package name for its symbols, so every implementation has its own idea where to put the package. ... Another way is to use the Closer to MOP library which, apart from fixing some compatibility issues, provides a common package name for all implementations. ...
    (comp.lang.lisp)
  • Re: Declaring *print-case* special in SBCL seems broken
    ... I'm not aware of an exception in the standard. ... Some Exceptions to Constraints on the COMMON-LISP Package ... Declaring a special a special is not ...
    (comp.lang.lisp)
  • Re: CLX/CMUCL: warning on load
    ... > in those declarations, there is also a stub DEFPACKAGE "XLIB" ... The COMMON-LISP package used to contain a lot of extraneous ... is that since the XLIB package is defined during the build process, ...
    (comp.lang.lisp)
  • Re: Python syntax in Lisp and Scheme
    ... which have a different defined semantics, one places their names in a package ... one does not want to specialize the standard operators other than in the ... > programmer is not in the spirit of Lisp, ... :common-lisp package itself, but instead use it's internal functions. ...
    (comp.lang.python)
  • Re: Python syntax in Lisp and Scheme
    ... which have a different defined semantics, one places their names in a package ... one does not want to specialize the standard operators other than in the ... > programmer is not in the spirit of Lisp, ... :common-lisp package itself, but instead use it's internal functions. ...
    (comp.lang.lisp)