Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:94575
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.52 as permitted sender)
MIME-Version: 1.0
Sender: jesseschalken@gmail.com
In-Reply-To: <CAF+90c_UBnZkkWfPGR37A0rcUNZQfSReU6=4nd0TVKTXY5Txig@mail.gmail.com>
References: <c69873f9-091f-f863-5f94-68d870285919@gmail.com>
 <CAF+90c8E_eO1xWLHexNxTFEvFu6DhNyvanTjsGxZ5Ge8aCK0KA@mail.gmail.com>
 <CAFMT4NqGykfZXFM=BO-xhbP0pO_+SDqmnFwLztd6cpbWqU5t3A@mail.gmail.com> <CAF+90c_UBnZkkWfPGR37A0rcUNZQfSReU6=4nd0TVKTXY5Txig@mail.gmail.com>
Date: Tue, 19 Jul 2016 11:58:32 +1000
Message-ID: <CAF1yvATv40P5ysE530xKVf9vBhi60wyaf473Q5UE+oK=+_3t3Q@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: Levi Morrison <levim@php.net>, Rowan Collins <rowan.collins@gmail.com>, 
	PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11474b8c0e610f0537f36c29
Subject: Re: [PHP-DEV] Idea: Function autoloading using dummy namespaces
From: me@jesseschalken.com (Jesse Schalken)

--001a11474b8c0e610f0537f36c29
Content-Type: text/plain; charset=UTF-8

On Mon, Jul 18, 2016 at 9:55 AM, Nikita Popov <nikita.ppv@gmail.com> wrote:

>
> A relaxed variant would only invoke the autoloader once for each
> call, assuming that a function that is not loadable at one time will never
> become loadable (which is of course a significant restriction). The former
> variant would be prohibitively slow. The latter is more realistic, but I
> expect it to have non-trivial performance impact nonetheless.
>
>
Is that really a significant restriction? The only difference it would make
is for code that expects "namespace Bar { foo(); }" to refer to global
function "foo()" at one point in the program, and later to refer to
"Bar\foo()" at another point in the program, after "Bar\foo" has become
loadable. That kind of temporal coupling with the symbols that happen to be
loaded/loadable at a given point in time sounds just awful, and I can't
imagine what the use case would be.

Considering Option B can cause the introduction of global functions to
break code (my previous email), the caching of negative results from the
autoloader sounds like the only feasible option.

--001a11474b8c0e610f0537f36c29--