From: Trevor Squires <trevor@...>
Date: 2005-11-07T10:37:06+09:00
Subject: Re: Namespace pollution in Rails

Hi Leslie,

I encountered a Glue conflict as well a while back.  I believe it's 
something to do with the html_scanner library that is included in rails 
(action_controller/vendor).

This rails patch may not be specific to your own issue but it does 
(IMHO) give an indication of why the glue gem's files are getting 
loaded by rails:

http://dev.rubyonrails.org/ticket/2255

Regards,
Trevor

On 6-Nov-05, at 1:28 PM, Leslie Viljoen wrote:

> Trans wrote:
>
>> This shoud be a lesson.
>>
>> Unless you are specifically creating a general purpose class or module
>> which can be required INDEPENDENTLY, for all the world to use in their
>> projects (for example a OrderHash), you should NOT load your classes
>> and modules into that space.
>>
>> T.
>>
>>
> Yes, they are using Gems.
>
> I agree with what you are saying, in fact I think libraries that
> do this should be removed - and that is what they have done
> in response to my requests at Textdrive. Strangely, I installed
> the latest version of Nitro and Glue and both irb and the
> Rails console environments were inaffected. It must have been
> an older version of Glue, but it still beats me how this came about.
> Irb showed no pollution, only when running a Rails app did there
> suddenly appear a loaded Glue module.
>
> This is why I am so curious about it - how did Glue get itself loaded?
>
> I'd like to be able to circumvent such things in future, it is
> impossible to code around every possible class people dream up
> and Glue even modified the default String class!
>
>
>
>
--
Trevor Squires
http://somethinglearned.com