From: Rich Kilmer <rich@...>
Date: 2001-09-19T11:02:13+09:00
Subject: [ruby-talk:21369] Re: nested require files need path  internally



> I understand your point about the security implications of 
> requiring files from the current directory, but it seems that if 
> a file is requiring another file in the same directory as itself, 
> then if a person can get into that directory to change the file 
> being required, they might as well just have changed the file 
> doing the require in the first place.

This seems like a good argument.  In Java, package (namespace) names directly align with directories.  This is not the case with Ruby namespaces (modules/classes).  In Java, a Class does not need to import another Class in the same package (directory).  In Ruby...every additional file you want to use must be loaded/required.  I do understand the extreme difference between the two, but the ability to "require" a ruby file in the same directory as the requesting file seems very good from a library perspective (and I also agree that you need to protect the namespace from the CWD).