Re: CLOS defining macros & compilation

[kempf@Sun.COM]

>vague.  (Basically, that DEFCLASS makes the class name recognizable as
>a valid type name in subsequent declarations, but leaving unspecified
>whether or not real class, method, etc. objects are fully defined at
>compile-time.)  It may well happen that at some point the MOP

This is going to put a crimp in the usual style of OO programming, namely
to define classes at the top of a file, then the methods applicable to
them thereafter. What you're saying is that this style would be
potentially nonportable.

		jak