From: Benoit Daloze <eregontp@...>
Date: 2011-02-23T07:24:59+09:00
Subject: [ruby-core:35341] Re: odd require behavior

On 22 February 2011 20:05, Roger Pack <rogerdpack2@gmail.com> wrote:
> Hello all.
> In trunk "Queue" appears to be a native class.
> In 1.9.2, its require causes an odd result:
>
>
>>> Queue
> NameError: uninitialized constant Object::Queue
> � � � �from (irb):1
> � � � �from D:/Ruby192/bin/irb:12:in `<main>'
>>> require 'queue'
> LoadError: no such file to load -- queue
> � � � �from <internal:lib/rubygems/custom_require>:29:in `require'
> � � � �from <internal:lib/rubygems/custom_require>:29:in `require'
> � � � �from (irb):2
> � � � �from D:/Ruby192/bin/irb:12:in `<main>'
>>> Queue # it appears it was actually successful...
> => Queue
>>> RUBY_DESCRIPTION
> => "ruby 1.9.2p136 (2010-12-25) [i386-mingw32]"
>
> Any hints out there?
> -r

Maybe some gem prelude's magic which require thread by requiring the
whole rubygems ?

And AFAIK, Queue is not a native class, even in trunk (and I wonder
why Feature #3620 was never answered or merged).

However, you don't have to require 'thread' in trunk, as rubygems
already does it (but shouldnt).