From: "trans.  (T. Onoma)" <transami@...>
Date: 2004-11-24T21:27:51+09:00
Subject: Re: Question about the behavior of reopening a module and including another module.

On Wednesday 24 November 2004 05:24 am, Zev Blut wrote:
| Hello,
|
| On Wed, 24 Nov 2004 06:31:18 +0900, Pit Capitain <pit@capitain.de> wrote:
| > You can find a description here:
| > http://www.ruby-doc.org/docs/ProgrammingRuby/html/classes.html#UC (if
| > you have the paper version see also figure 19.4 on page 247).
|
| Thanks for the link, it certainly helps describe how it is implemented.
|
| > By including a module, anonymous proxy classes pointing to the module
| > and its ancestors are added to the ancestors of the including class. If
| > you alter a module's ancestors AFTER including the module in a class,
| > the proxy classes don't reflect this change.
| >
| > I think it's an implementation issue.
|
| Yeah probably so.
| Are there plans to change this in Ruby 2.0?

It is a rather fundamental problem, so is not likely to get addressed. 
Thankfully, it is extremely rare for it to be a problem.

There has been some talk of this on suby-ruby, with a possible solution or 
two, but they have performace downsides.

T.