Forum: Ruby return value of require

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
Detlef R. (Guest)
on 2009-06-02 01:51
(Received via mailing list)
Hi,

I had a problem with require and ruby 1.8.7-p72 on debian (original
debian packages).

For some of the ruby-gnome2 libraries (all, which are based on gtk),
require returned false. Beside of the return value all works like
expected.

With an upgrade to 1.8.7-p160 and compiling ruby from source, all
libraries return true on require, as expected.

Can someone tell me, in which version this change was made?

Cheers, detlef
Brian C. (Guest)
on 2009-06-02 12:10
Detlef R. wrote:
> I had a problem with require and ruby 1.8.7-p72 on debian (original
> debian packages).
>
> For some of the ruby-gnome2 libraries (all, which are based on gtk),
> require returned false. Beside of the return value all works like
> expected.
>
> With an upgrade to 1.8.7-p160 and compiling ruby from source, all
> libraries return true on require, as expected.
>
> Can someone tell me, in which version this change was made?

I'm don't see what the problem is. require returns false if the library
has already been loaded, and true if it is loaded for the first time at
that point.

$ irb --simple-prompt
>> require 'openssl'
=> true
>> require 'openssl'
=> false
>>

If some of the ruby-gnome2 libraries returned false, it's probably just
because some previous library that you required in turn required those
other libraries.

If you want to investigate further,

    puts $LOADED_FEATURES

will probably be of help.

Regards,

Brian.
This topic is locked and can not be replied to.