Hi,

In message "[ruby-talk:21368] Re: nested require files need path internally"
    on 01/09/19, "Julian Fitzell" <julian-ml / beta4.com> writes:

|>You don't have this kind of problem, if you don't try to load from the
|>current directory.
|
|But, I think what he is looking for is the ability to require a file from the same directory as the file that does the require, not from the current directory.  I have experienced this problem too...

Your statement is understandable.  I think it's trade off between
library search path complexity and saving few strokes of grep and
edit.  I prefer behavior simplicity this case.

							matz.