From: Matthias Veit <matthias_veit@...>
Date: 2002-07-16T09:00:02+09:00
Subject: Re: cut & paste for code


>>>> HEF == "Hal E. Fulton" <hal9000@hypermetrics.com> wrote:

HEF> [snip]
HEF> 
HEF> What I meant was more like this:
HEF> 
HEF> class Other 
HEF>   # whatever
HEF> end
HEF> 
HEF> module T
HEF>   def meth1
HEF>   end
HEF>   def meth2
HEF>   end
HEF>   def meth3
HEF>   end
HEF> end
HEF> 
HEF> class A
HEF>   include T
HEF>   # more stuff?
HEF> end
HEF> 
HEF> class B < Other
HEF>   include T
HEF>   # more stuff?
HEF> end
HEF> 
HEF> What's wrong with this?

Absolutely nothing. It's nice.

I just mentioned, that the behaviour of the including code
depends on the surrounding context. If there is no context, 
(the module T above is toplevel), no problem arises. 
The problem, I see, are nested classes - there is a difference
between including a module (bound to a specific namespace) or 
copyinheritance, where the binding is not done.

Best regards,
Matthias
__________________________________________________
Do You Yahoo!?
Yahoo! Autos - Get free new car price quotes
http://autos.yahoo.comm