From: Ezra Zygmuntowicz <ezmobius@...>
Date: 2006-01-06T09:00:32+09:00
Subject: Re: require 101


On Jan 5, 2006, at 3:18 PM, Brian Buckley wrote:

>> Because Builder has that stupid autorequire attribute set in its gem
>> spec.
>>
>
> Thank you for the explanation.  I stumbled across this with builder  
> while
> walking through an article about builder
> (http://www.xml.com/pub/a/2006/01/04/creating-xml-with-ruby-and- 
> builder.html
> ) but I seem to often enough encounter what seem to be invalid 'false'
> returns when requiring other libraries.  Is this autocomplete  
> problem a
> problem with quite a few other gems?  And does it spread easily  
> because any
> require which includes a require with that bug will also be returning
> false?  If so it sounds like the long and the short of it for us  
> users of
> gems is we can often (and maybe even generally should) ignor the  
> return
> value of require because it gives so many false positives.  Fair  
> statement
> or overstating the bug?
>
> Brian

Yes for the short answer. I have found that usually if it returns  
fals then things are ok. If it errors out with an exception then its  
not ok.

Cheers-
-Ezra