Re: What's wrong the __autoload()?

On Wed, 2008-03-12 at 10:33 -0500, Greg Donald wrote: > On 3/12/08, Richard Heyes <richardh@phpguru.org> wrote: > > > I'm wondering what's wrong with the use of __autoload(), since I see that > > > projects like the Zend Framework don't use it and prefer to require_once > > > each required file. > > > > Things that happen without you explicitly causing them (ie require() et > > al) can lead to confusion. > > It's called "convention over configuration" and that's exactly where > good frameworks should be headed. But then you'd end up with something like Ruby on Rails... and we all know about Ruby on Rails *VOMIT*. Who wants to be stuck on a track when they can soar with the eagles. > http://en.wikipedia.org/wiki/Convention_over_Configuration Interesting how the article promotes the ideas of both convention and configuration co-existing so that one doesn't lose versatility. Thus, one could infer that any good framework would allow both paradigms. Cheers, Rob. -- http://www.interjinn.com Application and Templating Framework for PHP