-- Eric Coleman <[EMAIL PROTECTED]> wrote (on Friday, 07 November 2008, 05:15 PM -0500): > On Fri, Nov 7, 2008 at 12:15 PM, Matthew Weier O'Phinney > <[EMAIL PROTECTED]> wrote: > > Actually... loadClass() already does that. The issue is in the userland > > code -- if they do a require_once or include_once in userland *after* > > we've already loaded the class in the autoloader using simply include, > > that will trigger the error. That's what I was getting at. That said, > > we may be being to defensive about this. > > So, if your worried about includes -after- the autoloaded... what > exactly are you preventing with include_once? Seems like it'll be an > error regardless, no?
I'm worried about include_once/require_once() after autoloading. include() and require() will be an issue regardless, but if we can play nice with include_once/require_once(), then we should. That said, we can probably have a flag for using include vs include_once that could be passed to registerAutoload(). -- Matthew Weier O'Phinney Software Architect | [EMAIL PROTECTED] Zend Framework | http://framework.zend.com/
