Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:94118
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain mindplay.dk from 209.85.213.44 cause and error)
MIME-Version: 1.0
In-Reply-To: <CADyq6sLzjq2DDGrAhwY7byGFLRKObzYQeFiGHgmCbHEpd8_Cwg@mail.gmail.com>
References: <CAEDdnaX_KbaZB=3WzFAp73E0dCxx5zuoqMbPbakMUGpHyRPJFg@mail.gmail.com>
 <b9318b90-f850-12a2-459d-8995220922df@gmail.com> <20160617202344.2868F1A80C02@dd1730.kasserver.com>
 <CAObuZdvZoACWE1bxz2PUMW+yXHxyEtXuYpPXL=6dEqrsakSNBQ@mail.gmail.com>
 <CADqTB_ijxN_ZVcAdLrpnejtYNO2x6Z1Q4PcnARCRE+etDuhF3w@mail.gmail.com>
 <CANUQDCjgSohsYWmkWOLfdL+9Jzio_uY-vnYVc4fzd6kmGaL46g@mail.gmail.com>
 <CADqTB_ih=WnH699EtKJJMbaL=5FnFsOwmgsutWxKC9ApX00TjQ@mail.gmail.com> <CADyq6sLzjq2DDGrAhwY7byGFLRKObzYQeFiGHgmCbHEpd8_Cwg@mail.gmail.com>
Date: Sun, 19 Jun 2016 11:57:25 +0200
Message-ID: <CADqTB_ix6VMBpq4BVkqLp6Ec7175En09sTbM2ROW63_6DHKaCg@mail.gmail.com>
To: Marco Pivetta <ocramius@gmail.com>
Cc: Niklas Keller <me@kelunik.com>, Ryan Pallas <derokorian@gmail.com>, 
	Stanislav Malyshev <smalyshev@gmail.com>, Thomas Bley <mails@thomasbley.de>, 
	"internals@lists.php.net" <internals@lists.php.net>, michael.vostrikov@gmail.com
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] New escaped output operator
From: rasmus@mindplay.dk (Rasmus Schultz)

I am well familiar with this approach, and it does not scale - not
only would you be aggressively loading every installed view-helper
anytime you render a view, you would even be loading them when you're
*not* rendering a view.

I'm afraid the best we could do at this point, without changing the
language, is a establish a convention for autoloading functions
(and/or namespaces of functions) from files, based on static analysis
of template files.

But that is pretty complex - on the organizational side, it requires
developers to agree on and adopt a convention, and on the technical
side, you need static analysis and thereby most likely a cache layer
as well.

It's all possible, but most people aren't going to put up with this
much complexity for something this simple.

Hmm. What if we could import static methods into file scope and use
them as functions?

use My\Namespace::my_function;

my_function(); // <-- effectively My\Namespace::my_function()

This would leverage auto-loading at least... I mean, it's still
effectively just abusing classes as pseudo-namespaces, so there is
that - but it would work with e.g. Composer right away, and probably
with many existing static classes?

Yeah, it's still ugly...


On Sun, Jun 19, 2016 at 11:37 AM, Marco Pivetta <ocramius@gmail.com> wrote:
> On 19 June 2016 at 11:34, Rasmus Schultz <rasmus@mindplay.dk> wrote:
>>
>> > You can always add more functions to a namespace even spread accross
>> > multiple files
>>
>> Same problem: no autoloading.
>>
>> You would have to add require_one statements - which, as said, is not
>> really possible with Composer packages...
>>
>
> You should look at packages that already do this:
> https://github.com/nikic/iter/blob/5527ca489bf151ceef17622f1c89114640f522d2/composer.json#L16
>
> Ref: https://getcomposer.org/doc/04-schema.md#files
>
> Marco Pivetta
>
> http://twitter.com/Ocramius
>
> http://ocramius.github.com/