Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:94980
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.41 as permitted sender)
References: <CADqTB_gBFM_2yNDQemPs68Fab4Hbd8pGj38a3-HSQ+CRcnDyvA@mail.gmail.com>
 <CAF+90c9td1bt2zCbGfXdbGtFO-4qhJuJnkAEdsQDaH+wATDOmA@mail.gmail.com>
 <CAFMT4NpFBCJW1x3Yxz3FDx+6JGcdaGXZuBseEOaxXG0fnFHV0g@mail.gmail.com>
 <de01a2d6-f03a-834d-b211-213a6f4cca1e@gmail.com>
 <CAFMT4NppJ2+rO7Y9=kqSrYhwHGDQ_faSSPGmaSY6sZPRrOKCtQ@mail.gmail.com>
 <33781781-2a63-78c1-68a1-9e19ad720d8d@gmail.com>
 <CAFMT4NrHmn71UzqMNPTJe18M-9OjgsG2YDsdhhNJ-vfrsYu5yw@mail.gmail.com>
 <1d89ec68-de5e-2670-aed1-f12872c073c3@gmail.com>
 <CADqTB_gZJgtV2rVhzMd_ExpfXxW-w0wR8GVfNXJc6wFO6DOQmA@mail.gmail.com>
 <aaa65a04-d349-62ae-fd47-3901a6afeefe@gmail.com>
 <CADqTB_hdq+kyM_cJ_e7ent3OK1ZPOco+YZe0TB-yugPLx1argw@mail.gmail.com>
 <615f02b9-0621-2e7a-bec9-af4e342529b2@gmail.com>
 <CADqTB_jdv36JBTuh6YL4J0_VJ_kDosmVLnj8FdCjzLHGn1W12w@mail.gmail.com>
To: internals <internals@lists.php.net>
Message-ID: <0d55f224-201e-2273-8faa-296122320e19@gmail.com>
Date: Tue, 9 Aug 2016 22:26:32 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <CADqTB_jdv36JBTuh6YL4J0_VJ_kDosmVLnj8FdCjzLHGn1W12w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Function auto-loading
From: rowan.collins@gmail.com (Rowan Collins)

On 09/08/2016 18:44, Rasmus Schultz wrote:
> On Tue, Aug 9, 2016 at 6:17 PM, Rowan Collins<rowan.collins@gmail.com>  wrote:
>
>>> >>In other words, calls to substr() does not trigger the resolve - a
>>> >>statement like "use function substr" on the other hand, does.
>> >
>> >Ah, I see. The problem with that is, you still have to explicitly list every
>> >function you're going to use, so you might as well just use require_once, or
>> >call "load_function('substr')" directly.
> Well, no - there is still the issue of file names and paths becoming a
> dependency, besides issue of having to locate the file in the first
> place.

Sure, there is a small advantage over raw require statements, because 
you're wrapping the file-location logic in a function, which can be a 
bit more flexible. But that doesn't actually need the engine to do 
anything special:


Proposed:

function autoload_function($name) {
     require_once FUNCTION_ROOT . str_replace('\', PATH_SEPARATOR, 
$name) . '.php';
}
register_function_autoloader('autoload_function');

use function Acme\Util\foo; // calls autoload_function('Acme\Util\foo');
use function Acme\Util\bar; // calls autoload_function('Acme\Util\bar');


Current PHP:

function load_function($name) {
     if function_exists($name) return;
     require_once FUNCTION_ROOT . str_replace('\', PATH_SEPARATOR, 
$name) . '.php';
}

load_function('Acme\Util\foo');
load_function('Acme\Util\bar');


All we'd really gain is a standard "name" for load_function (i.e. the 
"use" keyword), and I guess a built-in registry for chaining multiple 
callbacks together when you run it.

Regards,

-- 
Rowan Collins
[IMSoP]