From: Paul Brannan <pbrannan@...>
Date: 2008-12-03T23:20:58+09:00
Subject: [ruby-core:20257] Re: Behavior: autoload calls rb_require()  directly

On Wed, Dec 03, 2008 at 01:50:42PM +0900, Charles Oliver Nutter wrote:
> Rather than having autoload actually invoke the global require, whatever  
> it may be defined as, I think the better change would be the  
> long-postponed "require plugin" logic that's been discussed previously.  
> Rather than anyone ever needing to redefine require, there should be a  
> simple way to add to the require lookup chain with normal Ruby code.  
> require overrides have a nasty tendency to break each other, and  

How would a require plugin avoid this?  It seems to me they would still
be order-dependant.

> obviously won't fit well into e.g. autoload that wants to make sure it's  
> always calling into the "require" that eventually requires files. So  
> don't override require, don't make autoload call overridden versions,  
> and build in a way to add require plugins without redefining require  
> yourself.
>
> It's the right way!
>
> - Charlie