Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:94119
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.178 as permitted sender)
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (1.0)
In-Reply-To: <CADqTB_ix6VMBpq4BVkqLp6Ec7175En09sTbM2ROW63_6DHKaCg@mail.gmail.com>
Date: Sun, 19 Jun 2016 22:59:58 +1000
Cc: Marco Pivetta <ocramius@gmail.com>, 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-Transfer-Encoding: 7bit
Message-ID: <2FE6EEAB-FAA4-4449-A443-08C2C0D28AB4@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> <CADqTB_ix6VMBpq4BVkqLp6Ec7175En09sTbM2ROW63_6DHKaCg@mail.gmail.com>
To: Rasmus Schultz <rasmus@mindplay.dk>
Subject: Re: [PHP-DEV] New escaped output operator
From: davidkmuir@gmail.com (David Muir)



> On 19 Jun 2016, at 7:57 PM, Rasmus Schultz <rasmus@mindplay.dk> wrote:
> 
> 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...
> 
> 

Ugly, but brilliant! +1

David