Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54601
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain mindplay.dk from 209.85.214.42 cause and error)
MIME-Version: 1.0
Date: Sun, 14 Aug 2011 18:11:07 -0400
Message-ID: <CADqTB_jHR0afckXj9b6hOLVGx29h=xjpJZ93ymitL8AuMqYO9g@mail.gmail.com>
To: internals@lists.php.net
Content-Type: multipart/alternative; boundary=485b3978bfe160198604aa7e6c3c
Subject: Re: [PHP-DEV] [RFC] Function autoloading through spl_autoload
From: rasmus@mindplay.dk (Rasmus Schultz)

--485b3978bfe160198604aa7e6c3c
Content-Type: text/plain; charset=ISO-8859-1

Instead of trying to figure out how to autoload functions and cover all your
bases, how about simply adding a __call() magic method?

That way, each application (or framework) can make their own decisions about
what they're going to autoload and how.

A much simpler solution, and one with more potential uses than just
autoloading.

The __call() method could be invoked first in the current namespace, if
present - then in the parent namespace, if present, etc. up to the global
namespace. Since functions are no longer just global, but can now exist in a
namespace, it is likely you're going to need a different "autoloader" or
other dynamic function resolvers in each namespace, since we tend to create
a namespace for classes/functions designed to perform a specific kind of
task - for example, a template/view-engine probably needs to autoload
display-formatting functions, while a controller/dispatcher might need to
autoload action-filters, etc.

Just a thought :-)

/ Rasmus Schultz

--485b3978bfe160198604aa7e6c3c--