Gary Wright wrote:
> I admit to not thinking about this too much but shouldn't there be a 
> global lock on things like require and load?  If it isn't enforced by 
> Ruby itself, I would think that a properly designed multi-threaded 
> application shouldn't have multiple threads contending for access to 
> global state without proper locking.

It certainly could, but that is a behavioral change; there's no way to 
require files in separate threads at the same time. Of course, maybe 
it's a bad idea to allow that in the first place.

- Charlie