exporting standard-class

[oravax!esrig@cu-arpa.cs.cornell.edu (Bruce Esrig)]

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) ())
	(make-instance 'topmost_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 ?

	Bruce Esrig
	Odyssey Research Associates
	esrig%oravax.uucp@cs.cornell.edu