Re: Multiple classifications of an object

[Bart Lateur]

On Wed, 27 Jun 2001 13:48:38 -0400, Dan Sugalski wrote:

>And the current @ISA stuff is MI, 
>albeit on a per-class basis rather than on a per-object one.
>
>Anyway, as Damian mentioned, setting the .ISA property is a perfectly 
>reasonable sort of thing to do if the language supports this. 

Just one question. If an object would have both per-object inheritance
(.ISA), and per class inheritance (@ISA), which one would have
precedence? If there's a conflict, a method exists both for a superclass
and for an object superclass (i.e. through .ISA), which list would be
checked first? Which method would be picked, and executed?

FWIW, I think I'd vote for .ISA, as it is more individually tied to this
particular object. The other one is generic.

-- 
        Bart.