Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:34303 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 60087 invoked by uid 1010); 31 Dec 2007 17:59:02 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 60072 invoked from network); 31 Dec 2007 17:59:02 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 31 Dec 2007 17:59:02 -0000 Authentication-Results: pb1.pair.com smtp.mail=helly@php.net; spf=unknown; sender-id=unknown Authentication-Results: pb1.pair.com header.from=helly@php.net; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 85.214.94.56 as permitted sender) X-PHP-List-Original-Sender: helly@php.net X-Host-Fingerprint: 85.214.94.56 aixcept.net Linux 2.6 Received: from [85.214.94.56] ([85.214.94.56:50292] helo=h1149922.serverkompetenz.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D7/96-02434-3ED29774 for ; Mon, 31 Dec 2007 12:59:00 -0500 Received: from MBOERGER-ZRH.corp.google.com (183-169.78-83.cust.bluewin.ch [83.78.169.183]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by h1149922.serverkompetenz.net (Postfix) with ESMTP id 905381B365A; Mon, 31 Dec 2007 18:58:58 +0100 (CET) Date: Sun, 30 Dec 2007 18:58:30 +0100 Reply-To: Marcus Boerger X-Priority: 3 (Normal) Message-ID: <1944505528.20071230185830@marcus-boerger.de> To: "Andrew Mason" CC: Pierre , david.coallier@nyphp.com, In-Reply-To: <99cd336d0712281728g6659d7e6pa3ed92db5574e63b@mail.gmail.com> References: <99cd336d0712280356v680cc82fh3b1396c9c608bb96@mail.gmail.com> <99cd336d0712281728g6659d7e6pa3ed92db5574e63b@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] spl_autoload vs __autoload From: helly@php.net (Marcus Boerger) 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 wrote: >> On Dec 28, 2007 3:30 PM, wrote: >> > On Dec 28, 2007 6:56 AM, Andrew Mason 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