[Python-Dev] perplexed by mro

Greg Ewing greg@cosc.canterbury.ac.nz
2002年10月04日 14:29:27 +1200 (NZST)


Guido:
> No, the whole point here is that the most inherited class's MRO
> (i.e. z) can insert things in a base class's MRO.

It worries me that when I write a super call, I'll
never be sure which method is going to be called,
because someone might inherit me and mess with
my mro.
But I can see that there are cases where this
behaviour is desirable. I guess it's okay as long
as I have the option of explicitly specifying
the base class. (You're not going to take that
away, are you?)
Greg Ewing, Computer Science Dept, +--------------------------------------+
University of Canterbury,	 | A citizen of NewZealandCorp, a	 |
Christchurch, New Zealand	 | wholly-owned subsidiary of USA Inc. |
greg@cosc.canterbury.ac.nz	 +--------------------------------------+

AltStyle によって変換されたページ (->オリジナル) /