Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54602
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CADqTB_jHR0afckXj9b6hOLVGx29h=xjpJZ93ymitL8AuMqYO9g@mail.gmail.com>
References: <CADqTB_jHR0afckXj9b6hOLVGx29h=xjpJZ93ymitL8AuMqYO9g@mail.gmail.com>
Date: Mon, 15 Aug 2011 00:44:25 +0200
Message-ID: <CAH-PCH7bk84X5Rkaka5BxwT=oe2vBWKY+7+kOWoCh1uFAuai=g@mail.gmail.com>
To: Rasmus Schultz <rasmus@mindplay.dk>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] Function autoloading through spl_autoload
From: tyra3l@gmail.com (Ferenc Kovacs)

On Mon, Aug 15, 2011 at 12:11 AM, Rasmus Schultz <rasmus@mindplay.dk> wrote=
:
> Instead of trying to figure out how to autoload functions and cover all y=
our
> bases, how about simply adding a __call() magic method?
>
> That way, each application (or framework) can make their own decisions ab=
out
> 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 i=
n 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 crea=
te
> 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
>

we already have a magic method with the name __call.
I'm not sure where you propose adding this magic method, but judging
from it's name, you would like to propose something similar than
__autoload what we have abadoned for many reasons, the main reasons is
that the spl_autoload_register is more explicit and supports having
multiple callbacks.

please create an RFC for your idea, from first glance, I feel that you
didn't really thought over the details yet.


--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu