E
Eugen Ciur
Hi all,
I discovered recently a strange behavior. If I require 'i18n' gem then
'active_support' then everything is ok, if I change order - irb raises
an exception:
$ irb
ruby-1.9.2-p0 > require 'i18n'
=> true
ruby-1.9.2-p0 > require 'active_support'
=> true
ruby-1.9.2-p0 > exit
eugen@eugen-hp:~$ $ irb
ruby-1.9.2-p0 > require 'active_support'
=> true
ruby-1.9.2-p0 > require 'i18n'
NameError: uninitialized constant Object::I18n
from
/home/eugen/.rvm/gems/ruby-1.9.2-p0/gems/activesupport-3.0.1/lib/active_support/i18n.rb:8:in
`<top (required)>'
from
/home/eugen/.rvm/gems/ruby-1.9.2-p0/gems/i18n-0.5.0/lib/i18n/version.rb:1:in
`<top (required)>'
from <internal:lib/rubygems/custom_require>:29:in `require'
from <internal:lib/rubygems/custom_require>:29:in `require'
from
/home/eugen/.rvm/gems/ruby-1.9.2-p0/gems/i18n-0.5.0/lib/i18n.rb:1:in
`<top (required)>'
from <internal:lib/rubygems/custom_require>:33:in `require'
from <internal:lib/rubygems/custom_require>:33:in `rescue in require'
from <internal:lib/rubygems/custom_require>:29:in `require'
from (irb):2
from /home/eugen/.rvm/rubies/ruby-1.9.2-p0/bin/irb:17:in `<main>'
It is a bug? Any idea ?
I discovered recently a strange behavior. If I require 'i18n' gem then
'active_support' then everything is ok, if I change order - irb raises
an exception:
$ irb
ruby-1.9.2-p0 > require 'i18n'
=> true
ruby-1.9.2-p0 > require 'active_support'
=> true
ruby-1.9.2-p0 > exit
eugen@eugen-hp:~$ $ irb
ruby-1.9.2-p0 > require 'active_support'
=> true
ruby-1.9.2-p0 > require 'i18n'
NameError: uninitialized constant Object::I18n
from
/home/eugen/.rvm/gems/ruby-1.9.2-p0/gems/activesupport-3.0.1/lib/active_support/i18n.rb:8:in
`<top (required)>'
from
/home/eugen/.rvm/gems/ruby-1.9.2-p0/gems/i18n-0.5.0/lib/i18n/version.rb:1:in
`<top (required)>'
from <internal:lib/rubygems/custom_require>:29:in `require'
from <internal:lib/rubygems/custom_require>:29:in `require'
from
/home/eugen/.rvm/gems/ruby-1.9.2-p0/gems/i18n-0.5.0/lib/i18n.rb:1:in
`<top (required)>'
from <internal:lib/rubygems/custom_require>:33:in `require'
from <internal:lib/rubygems/custom_require>:33:in `rescue in require'
from <internal:lib/rubygems/custom_require>:29:in `require'
from (irb):2
from /home/eugen/.rvm/rubies/ruby-1.9.2-p0/bin/irb:17:in `<main>'
It is a bug? Any idea ?