while i think the other posts effectivly answered your question. i have
a require related question myself. hope you don't mind.

given a directory tree:

  pdir
    programP.rb
    adir
      a1.rb
      a2.rb
      programA.rb

and the files as such:

programP.rb:
  require 'adir/a1'

a1.rb:
  require 'adir/a2'

a2.rb:
  # dosn't matter

programA.rb:
  require 'a1'

%cd pdir
%ruby programP.rb
%cd adir
%ruby programA.rb
./a1.rb:1:in 'require':No such file to load -- adir/a2 (Load Error)
...

to get programA.rb to work you have to remove adir/ from the require in
a1.rb, but then programP.rb stops working. this is annoying as i would
think the local directory hiearchy to the required file should be
checked first for a match, and only after that, if at all, should the
main file's hiearchy be checked. as it now stands, regardless of
programA, if i decided i just wanted to move programP somewhere else,
say into adir for example, i not only need to modify its require paths,
but i am forced to modify each of those required file's require paths.
and that's just not natural.

~transami



On Thu, 2002-07-18 at 14:30, Bob X wrote:
> Why does Ruby do single quotes around package names?
> 
> Why not just:
> 
> require somepackage
> 
> Just a little question...
> 
> Bob
> 
> / do not send to my e-mail address /
> 
> 
-- 
~transami

  _(")_  dobee dobee do...
   \v/  
   ^ ^