On Tue, 11 Oct 2005, TRANS wrote:
> Ah, I see. So it's the same @x in either method --I thinking super would
> behave the same as calling Q::H.x. Is this why super is "hard bound" at
> compile time.

What do you mean by hard-bound at compile time? In a super-call, the self 
of the callee is always the self of the caller. However the 
classes/modules involved are not necessarily predetermined:

  module A; def foo; "A calls #{super}" end end
  class B; def foo; "B" end end
  class C; def foo; "C" end end
  class D<B; include A; def foo; "D calls #{super}" end end
  class E<C; include A; def foo; "E calls #{super}" end end
  puts D.new.foo
  puts E.new.foo

displays:

  D calls A calls B
  E calls A calls C

But I don't know what that feature has to do with your problem though...

____________________________________________________________________
Mathieu Bouchard - t?l:+1.514.383.3801 - http://artengine.ca/matju
Freelance Digital Arts Engineer, Montr?al QC Canada