🚀 go-pugleaf

In article <1993Jan8.220317@di.epfl.ch> matomira@di.epfl.ch (Fernando Mato Mira) writes:

   Here is a way of implementing the rule for implementing metaclass
   inheritance proposed in my previous post...

   (defmethod ensure-class-using-class :around ((class t) name 
						&rest args
						&key (direct-superclasses nil)
						     (metaclass nil))
     ...)


This is a nice hack, and it is probably good enough to get some work
done, but I guess I should point out that it is illegal, in portable
code, according to the rules on pages 142, 143 and 144 of AMOP.
Specifically the rule that:

  Any method defined by a portable program on a specified generic
  function must have at least one specializer that is neither a
  specified class nor an {\bf eql} specializer whose associated
  value is an instance of a specified class.

The basic problem with methods like this is that two programs, written
separately, which both have methods like this, will interfere with each
other if they are loaded together.  That is why this rule is there.  We
talk about this, and the origin of all these rules, in more detail in
our OOPSLA'92 paper.