[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: commonloops.pa@Xerox.COM
- Subject: exporting standard-class
- From: firstname.lastname@example.org (Bruce Esrig)
- Date: Fri, 19 Aug 88 14:00:10 EDT
- Redistributed: commonloops.pa
In a previous query, we asked whether there were any problems
porting pcl to Lucid; we reported that when we make an instance,
we get a message stating that there is no matching method for
the generic function initialize-instance. We now know that
the cause of the problem was that we had created a class with
an undefined metaclass.
The following definition illustrates our problem.
(in-package 'my-package :use '(lisp pcl system))
(defclass topmost_class (standard-class) ())
In this definition, standard-class refers to the internal symbol
of my-package. Should the classes standard-class and above be
exported by the pcl package ? If they were, this problem would not occur.
Alternatively, should there be a way to get warning messages when
forward definitions of class names occur ?
Odyssey Research Associates