behavior of -rsomegem differs from require 'somegem'

[Jeremy Hinegardner]

I just encountered something today and I'm not sure if this should be
the expected behaviour. Most likely I'm doing something odd here. I
believe this only affects items require'd as gems.

ruby -v

ruby 1.8.6 (2007-03-13 patchlevel 0) [i686-darwin8.9.1]

cat j.rb

require 'rubygems'
require 'fastercsv'

puts $:.sort.join("\n")

 

[Logan Capaldo]

I just encountered something today and I'm not sure if this should be
the expected behaviour. Most likely I'm doing something odd here. I
believe this only affects items require'd as gems. [snip]
Is this the expected behaviour that -rsomegem behaves differently than
'require "somegem"'. Is the handling of -r different than 'require'

loading rubygems alters the Kernel#require method. -r doesn't actually
call Kernel#require, it directly invokes the underlying C function(s)
the method calls. Therefore, rubygems is incapable of changing the
behavior of -r.

 

[Jeremy Hinegardner]

I just encountered something today and I'm not sure if this should be
the expected behaviour. Most likely I'm doing something odd here. I
believe this only affects items require'd as gems. [snip]
Is this the expected behaviour that -rsomegem behaves differently than
'require "somegem"'. Is the handling of -r different than 'require'

loading rubygems alters the Kernel#require method. -r doesn't actually
call Kernel#require, it directly invokes the underlying C function(s)
the method calls. Therefore, rubygems is incapable of changing the
behavior of -r.

Thanks!

-r using the underlying C function(s). That's the clarification I
needed.


enjoy,

-jeremy