From: Robert Klemme <bob.news@...>
Date: 2004-03-10T01:54:40+09:00
Subject: Re: when a required module redefine another module => problem


"shasckaw" <shasckaw@skynet.be> schrieb im Newsbeitrag
news:404ddab0$0$13860$ba620e4c@news.skynet.be...

<snip/>

> The fact is that it would be more adequate to have Enumerable modified
> in SomeModule only. This case is simple, but we can imagine more vicious
> sample codes, with some method redefined => it will affect the whole
> program! This is a problem, isn't it?
>
> What do you think about this?

I think this is not limited to modules but to *all* situations in Ruby
where you can redefine existing things (classes, methods, instance methods
etc.) and where this is done in different places that don't know anything
about each other.  But since this feature is mentioned as one of the
strengths of Ruby ("flexibility") most of the time, I'd say apparently
it's not a problem.  After all, most of us around here are aware of this
and it doesn't stop us from using Ruby, does it? :-)

My 0.02 EUR...

Kind regards

    robert