Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:94554
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <bf40e2bb-deef-0c1c-421b-5e4a578270a6@gmail.com>
References: <c69873f9-091f-f863-5f94-68d870285919@gmail.com>
	<3567286a-e942-1551-c300-663a50b0f484@gmail.com>
	<bf40e2bb-deef-0c1c-421b-5e4a578270a6@gmail.com>
Date: Mon, 18 Jul 2016 17:04:44 +0200
Message-ID: <CABdc3WqSdm+Vw5Z1MfrLuC=HdRgH=T7WqWaBGyzpEcAFgUeekA@mail.gmail.com>
To: Rowan Collins <rowan.collins@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=94eb2c06d756df65d30537ea4997
Subject: Re: [PHP-DEV] Idea: Function autoloading using dummy namespaces
From: michal.brzuchalski@gmail.com (=?UTF-8?Q?Micha=C5=82_Brzuchalski?=)

--94eb2c06d756df65d30537ea4997
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

18 lip 2016 15:58 "Rowan Collins" <rowan.collins@gmail.com> napisa=C5=82(a)=
:
>
> On 18/07/2016 01:50, Stanislav Malyshev wrote:
>>
>> Hi!
>>
>>> How about an alternative approach where a function inside a namespace
>>> can be autoloaded using the existing callback, by using a reserved
>>> namespace segment? So to autoload function "foo\bar()", the engine woul=
d
>>> construct a string like "__function\foo\bar" or "foo\__function\bar",
>>> and pass that to the registered autoloader stack.
>>

I was thinking on passing some context information into autoload about
context, eg.: class | funtion. Wouldn't it be satisfiable information for
autoloader?
IMHO it would be the easiest way to satisfy autoloader to find proprietary
implementation.
Such problem as naming convention of functions file could be resolved in
userland! Without complex implementation in core.

>>
>> Magic out-of-domain values usually are bad design, and lead to a lot of
>> trouble since now the system needs to deal with two sets of assumptions
>> instead of one. I wouldn't recommend doing it.
>>
>
> Hi Stas,
>
> My original idea was actually to have the autoloader look up
"foo\bar\__functions" for *any* function in namespace "foo\bar", with the
idea that some existing autoloaders would actually be able to work without
any modification (just call your file "__functions.php").
>
> If you include the function name (to give users more flexibility), that
doesn't really work (unless you have one function per file), so you're
right that it requires some muddling assumptions.
>
> I agree that it's all a bit magic either way, but I thought it might get
the feature moving quicker than a complete rewrite of the existing autoload
system.
>
> Like I say, it was just an idea. :)
>
>
> Regards,
> --
> Rowan Collins
> [IMSoP]
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>

--94eb2c06d756df65d30537ea4997--