On Friday 29 July 2005 12:54 am, Yukihiro Matsumoto wrote: > I want to mixin behave more like traits. he precedence should be > [D, C, A, B, A, Object] in the future. > > This is a drawback I mentioned in [ruby-talk:149778]: > >I know there's some drawbacks in the current implementation of Ruby's > >mixin inheritance, when a module is included repeatedly. am willing > >to fix it. 'm seeking the best way to fix. > > Since repeated mixin inclusion is pretty rare case, this problem have > been there for long time. In version 2.3, Python changed the way it resolves methods lookups. Its new way of looking up methods preserves something called monotonic lookup, ie. if module A precedes module B in the method lookup of class C, then A always procedes B in lookups of things derived from C. (See http://www.python.org/2.3/mro.html) Is the lack of monotonic lookup the problem you are refering to above? -- -- Jim Weirich jim / weirichhouse.org http://onestepback.org ----------------------------------------------------------------- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas)