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? Regards, Eric
