Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54669
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain priacta.com designates 64.95.72.241 as permitted sender)
To: Stas Malyshev <smalyshev@sugarcrm.com>, Matthew Weier O'Phinney
	<weierophinney@php.net>
CC: "internals@lists.php.net" <internals@lists.php.net>
Date: Wed, 17 Aug 2011 21:49:43 -0400
Thread-Topic: [PHP-DEV] [RFC] Function autoloading through spl_autoload*
Thread-Index: AcxdNq9j3wslS2YeSNeb0H3N9ORLYAADZeSA
Message-ID: <A633CF2D7C7BED41B41F1E64F25507B8060A508DB9@MAILR001.mail.lan>
References: <CAH-PCH5YvyBWfKomU0RaJw2E-GVqPXOV2TZMN9EURfQvYxu54w@mail.gmail.com>
 <alpine.DEB.2.02.1108141452460.4043@whisky>
 <CAF+90c-g8PLVvP2NYMbQcGCjNmPGN7tHdk5B8FpLp6JGik8tYQ@mail.gmail.com>
 <4E481136.3090508@sugarcrm.com> <4E483284.4010100@googlemail.com>
 <4E4838E1.3000006@sugarcrm.com> <4E48430D.6070409@googlemail.com>
 <4E486A50.4010700@sugarcrm.com> <4E48A22E.1040900@googlemail.com>
 <4E48AD3E.6010801@sugarcrm.com>
 <CA+Y0-p8JijO1Dhsqatp7yR+WR0v=V7rQHboPJmHXNFLWVWWGGw@mail.gmail.com>
 <4E48C126.50707@sugarcrm.com>
 <CA+Y0-p9k=8xytDq4t_20ebgE_wv2Nnn4mUpPaYM-1UFBNkCfkg@mail.gmail.com>
 <CAH-PCH4TiMyQOkVGWRRpnezCBeZfJdL2CfLkKec4hsaQ=s79uQ@mail.gmail.com>
 <4E48D848.1070407@sugarcrm.com>
 <CALKFbxvbOaaPkyqTpGrTaDskmhW2beRWhJa4FzFgR1hBjtiGzA@mail.gmail.com>
 <CAGovj_O+W3DpSFkfV8LU27cuWzdmsFKgp0H=QpUkrd8M3yri8w@mail.gmail.com>
 <81.F0.56760.0263C4E4@pb1.pair.com> <4E4C50A7.4000604@sugarcrm.com>
In-Reply-To: <4E4C50A7.4000604@sugarcrm.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: RE: [PHP-DEV] [RFC] Function autoloading through spl_autoload*
From: johncrenshaw@priacta.com (John Crenshaw)

> -----Original Message-----
> From: Stas Malyshev [mailto:smalyshev@sugarcrm.com]=20
> Sent: Wednesday, August 17, 2011 7:37 PM
> To: Matthew Weier O'Phinney
> Cc: internals@lists.php.net
> Subject: Re: [PHP-DEV] [RFC] Function autoloading through spl_autoload*
>
> Hi!
>
> On 8/17/11 2:44 PM, Matthew Weier O'Phinney wrote:
> > There's nothing saying you can't have the exact same situation right no=
w
> > with classes and autoloading, too.
>
> Well, there is something - the "file per class" custom which is followed=
=20
> quite widely.
>
> And also classes don't have fallbacks, while the functions do.
>
> > While I understand your objections, I think that after the functionalit=
y
> > exists, there can be discussions about best practices -- e.g., putting
> > one function per file when autoloading, or documenting when all
>
> I'm not sure anybody would really do function-per-file - it's too tedious=
.
>
> --=20
> Stanislav Malyshev, Software Architect
> SugarCRM: http://www.sugarcrm.com/
> (408)454-6900 ext. 227

Tedious, and slow because the overhead for each file loaded can easily be i=
n the 2-5ms range. Nobody is going to have a function per file, but they ar=
e still likely to use function autoloading in other ways. A likely case for=
 this would be to autoload a group of functions that all share the same pre=
fix. Another case might be to autoload a set of functions that are related =
to something else (for example, usability of singleton classes would benefi=
t greatly from having a function of the same name as the class, or classes =
may want to provide a factory function of the same name.)

John Crenshaw
Priacta, Inc.

P.S. Before someone flames me about the evilness of singletons, yes, I know=
; but, occasionally they still have a place. There is usually only one sess=
ion, there is only one app, there is usually only one database, logging is =
usually configured globally, etc.