[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
short form of define-method-combination
- To: DLW@ALDERAAN.SCRC.Symbolics.COM
- Subject: short form of define-method-combination
- From: Sonya E. Keene <skeene@STONY-BROOK.SCRC.Symbolics.COM>
- Date: Wed, 19 Aug 87 09:32 EDT
- Cc: Moon@STONY-BROOK.SCRC.Symbolics.COM, Common-Lisp-Object-System@sail.stanford.edu
- In-reply-to: <870818190658.2.DLW@CHICOPEE.SCRC.Symbolics.COM>
Initially, I had the same opinion you state -- that having the qualifier
in the defmethod form enhances readability, and that it was preferable
to make that qualifier be required rather than forbidden.
The reason for including the qualifier in the defmethod form is to
document the method (how it will be combined with other methods). But
we already provide a way to document a method, via the documentation
string. So now I'm in favor of having the methods be unqualified
instead of requiring that they be qualified.
Either of the new suggestions would be better than the way it is now,
where you can choose whether to include the qualifier or not.