From: Brian Buckley <briankbuckley@...>
Date: 2006-01-06T08:18:03+09:00
Subject: Re: require 101

------=_Part_6955_3117969.1136503068865
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

> 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.htm=
l
) 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

------=_Part_6955_3117969.1136503068865--