Re: draft of built-in method combination types

[kempf%hplabsz@hplabs.HP.COM]

>      
>       
>         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.
>      

Another disadvantage is forbidding CALL-NEXT-METHOD within primaries, which
was in my earlier message. This introduces an additional level of 
conceptual complexity which destroys the clean semantics of
CALL-NEXT-METHOD. 

			jak