Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:125120
Feedback-ID: id5114917:Fastmail
Precedence: bulk
MIME-Version: 1.0
Date: Fri, 23 Aug 2024 11:29:32 +0100
To: internals@lists.php.net
Message-ID: <f32382b4-3bee-47ab-88ed-ad2ab154c319@app.fastmail.com>
In-Reply-To: <53BD062A-4D7F-4E5D-852E-6D27641213A8@koalephant.com>
References: <21D6F160-5EAE-44FA-907B-E1DAAC1B8D75@rwec.co.uk>
 <53BD062A-4D7F-4E5D-852E-6D27641213A8@koalephant.com>
Subject: Re: [PHP-DEV] [Concept] Flip relative function lookup order (global, then
 local)
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
From: imsop.php@rwec.co.uk ("Rowan Tommins [IMSoP]")

On Fri, 23 Aug 2024, at 10:58, Stephen Reay wrote:
> Making relative function names do the opposite of relative class names 
> sounds like a great way to permanently kill any prospects of 
> encouraging developers to use regular namespaced functions in place of 
> static classes as "bag of functions", which is what we keep hearing we 
> should use - most notably on a recent RFC to embody the concept of a 
> static class.

That's why I brought up the point about making it easy to explicitly say "relative to current", just as you can explicitly say "relative to global" with a single "\".

It's also worth remembering that this whole discussion has no effect on using functions that are defined in a *different* namespace. The below code might benefit from function autoloading, but would not be helped, hurt, or changed in any way by any of the proposals in this thread:

namespace Acme\Foo\Controller;

use function Acme\StringUtils\better_strlen;
use Acme\StandardUtils as Std;

$foo = Std\generate_something();
$len = better_strlen($foo);
\Acme\Debug\out($len);



Regards,
-- 
Rowan Tommins
[IMSoP]