From: Aredridel <aredridel@...>
Date: 2005-02-03T01:29:54+09:00
Subject: Re: top-level object? top-level methods?

> I'm not sure what the problem is. Top level def methods are private,
> so they don't affect #respond_to?. Methods of the same name defined in
> Object's subclasses will mask those messages. When you talk about
> polluting, it makes it sound like they get in the way, and cause all
> manner of problems; I don't see how this could be possible. Is there a
> reason for changing it, other than to make Ruby more pure?
> 
> I'm not trying to give the idea the smackdown, but since I only see a
> semantic difference between the two ways of doing it, I feel that
> pollution is perhaps a bit too strong a word.

+1.

Don't break it -- not all problems are OO-shaped, no need to make ruby
less suitable for programs that aren't OO.

Besides, all the one-liners and such (which I write every day) rely on
this: it's a feature, not a bug.