[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: CLOS defining macros & compilation
- To: sandra%defun@cs.utah.edu (Sandra J Loosemore)
- Subject: Re: CLOS defining macros & compilation
- From: kempf@Sun.COM
- Date: Thu, 23 Feb 89 15:16:58 PST
- Cc: cl-compiler@sail.stanford.edu, common-lisp-object-system@sail.stanford.edu
- In-reply-to: Your message of Thu, 23 Feb 89 14:13:57 -0700. <8902232113.AA10372@defun.utah.edu>
>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