From: Robert Dober <robert.dober@...>
Date: 2009-02-04T16:39:30+09:00
Subject: Re: Object#singleton_class in Ruby 1.9?

On Tue, Feb 3, 2009 at 10:25 PM, David A. Black <dblack@rubypal.com> wrote:

> Nor is this kind of problem specific to singleton methods and
> singleton classes, of course. This is why I think it's very tricky to
> come up with rules in this area. In the end, it's always going to be
> about particular code and particular programming goals.
Ah very nicely put, indeed that shows me what I *should* have said:

It is IMHO preferable that, in case of a name conflict, the framework
wins over the application using it. But maybe I am wrong and this is
not much better a scenario? (All boiling down as usual to testing and
testing and well... testing)
Robert

-- 
It is change, continuing change, inevitable change, that is the
dominant factor in society today. No sensible decision can be made any
longer without taking into account not only the world as it is, but
the world as it will be ... ~ Isaac Asimov