Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:105759
To: Theodore Brown <theodorejb@outlook.com>, PHP internals <internals@lists.php.net>
Date: Mon, 20 May 2019 20:00:59 +0200
Message-ID: <16ad66607a0.27c1.08be835b7d1a2c2edb4c4286afe1a236@gmail.com>
In-Reply-To: <DM5PR06MB285728875FF1272F25FD35E7DE060@DM5PR06MB2857.namprd06.prod.outlook.com>
References: <DM5PR06MB285728875FF1272F25FD35E7DE060@DM5PR06MB2857.namprd06.prod.outlook.com>
User-Agent: AquaMail/1.20.0-1451 (build: 102000001)
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="us-ascii"
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] High performance function autoloading
From: gadelat@gmail.com (Gabriel O)


On 20 May 2019 7:17:58 PM Theodore Brown <theodorejb@outlook.com> wrote:

> Every time function autoloading been brought up in the past, there
> have been concerns about performance issues when calling a global
> function from inside a namespace. E.g. calling `strlen` in a loop
> would become far slower if every call has to trigger the autoloader.

This trick for perf improvement is overblown. It's misconception that it 
does provide speed advantage for most functions and reasons behind it. It 
does so only for those implemented as opcodes. People started to abuse it 
by importing ALL functions. Such overzealous approach completely prevents 
useful things like function mocking.