[ruby-talk:21433] Re: nested require files need path internally

On Thu, 20 Sep 2001, Yukihiro Matsumoto wrote:

> Every developer who works on multi file program has to decide where to
> store files other than main one.  Candidates are:
>
>   * current directory (this is BAD)
>   * same directory that main file exists (this is bad too)

Why is this bad?  It's extraordinarily useful to keep files in the same
directory as the main file when writing software, so that I don't have to
install the software every time I test it).

>   * ruby library directory (e.g. /usr/lib/ruby/1.6)
>   * application specific directory (e.g. /usr/share/lib/app)

Both of these options work great, so long as no two directories have a
file with the same name.  If they do, then one file will always get
required twice, and one file will always get required zero times.  I doubt
this is any author's intended behavior.

Should I start naming my files with my_special_identifier_foo.rb so that I
don't have filename-space collisions between separate directories?

Paul