Hello Andrew, SPL simply allows two things: a) a stack that hooks into __autoload b) a default implementation that may be used (with ot without the former)
We try to group functionality into extensions where we seem fit. And by the time I implemented spl_autoload stuff it made sense to put it into the SPL extension. Just because that extension was meant to be the home for more advanced OOP stuff. marcus Saturday, December 29, 2007, 2:28:53 AM, you wrote: > Thanks for your replies guys. > Part of the reason why I asked here is because of a previous posting a > while back where Stas seemed to suggest that the spl_autoloader was > superior but from reading the api i didn't know if this was purely > from a flexibility point of view or if there was more too it. I > probably should have been more specific in my question. > kind regards > Andrew > On 12/29/07, Pierre <[EMAIL PROTECTED]> wrote: >> On Dec 28, 2007 3:30 PM, <[EMAIL PROTECTED]> wrote: >> > On Dec 28, 2007 6:56 AM, Andrew Mason <[EMAIL PROTECTED]> wrote: >> > > Hi guys, >> > > Can anyone shed some light on the advantages of the spl_autoload over >> > > the standard __autoload ? is there any ? >> > > >> > >> > Please use php-general for that kind of question. >> >> This question makes sense here and brings yet again the question why >> such things are not available by default. >> >> -- >> Pierre >> http://blog.thepimp.net | http://www.libgd.org >> Best regards, Marcus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
