[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: draft of built-in method combination types
- To: common-lisp-object-system@SAIL.STANFORD.EDU
- Subject: Re: draft of built-in method combination types
- From: Patrick H Dussud <DUSSUD%Jenner%ti-csl.csnet@RELAY.CS.NET>
- Date: Mon, 28 Sep 87 11:14:24 CDT
- In-reply-to: Msg of Wed, 23 Sep 87 07:27 EDT from "Sonya E. Keene" <skeene@SCRC-STONY-BROOK.ARPA>
Date: Wed, 23 Sep 87 07:27 EDT
From: "Sonya E. Keene" <skeene@SCRC-STONY-BROOK.ARPA>
Subject: draft of built-in method combination types
A primary method has the name of the method combination type as its
sole qualifier. For example, the method combination type AND
recognizes methods whose sole qualifier is AND; these are primary
methods.
I thougt about it some more and found two disadvantages in qualifying
primary methods:
When one wants to change the method-combination type (from NCONC to
APPEND), one has to change the qualifiers of all the primary methods in
the source files.
Automatic method generators will have to know about the method
combination type.