B
Brad Hutchins
This an odd one.
require 'rubygems'
works in my scripts . . . but if I go to IRB to test some 'rspec' stuff.
I get:
=> false
Tried including the whole path, but that did not work either any ideas
why scripts being run don't have a problem requiring rubygems but IRB
does?
OSX 10.5.3
Ruby 1.8.6
Model Name: MacBook Pro 15"
Model Identifier: MacBookPro1,1
Processor Name: Intel Core Duo
Processor Speed: 2.16 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 2 MB
Memory: 2 GB
require 'rubygems'
works in my scripts . . . but if I go to IRB to test some 'rspec' stuff.
I get:
=> false
Tried including the whole path, but that did not work either any ideas
why scripts being run don't have a problem requiring rubygems but IRB
does?
OSX 10.5.3
Ruby 1.8.6
Model Name: MacBook Pro 15"
Model Identifier: MacBookPro1,1
Processor Name: Intel Core Duo
Processor Speed: 2.16 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 2 MB
Memory: 2 GB