Re: [RFC] New core autoloading mechanism with support for function autoloading
| From: | Rowan Tommins | Date: | Wed, 12 Apr 2023 20:26:15 +0000 |
| Subject: | Re: [RFC] New core autoloading mechanism with support for function autoloading | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-120003@lists.php.net to get a copy of this message | ||
On 12/04/2023 17:31, Claude Pache wrote:
* keep the current semantics, that using a namespaced or qualified function name, (including a function name given as string, which is implicitly fully qualified), doesn’t fall back to the global scope, — even when a previous use of the same function name did trigger the fall back, see:https://3v4l.org/mnVWO (Independently of any mechanism introduced to avoid to repeatedly trigger the function autoloader.)I could just about live with that example changing so that the fallback was cached, but I definitely don't think an explicit call like \foo\strlen('x') should become an implicit alias for \strlen('x'), which is apparently the current proposal. I really like the majority of this proposal, but right now would vote against it based on that. Regards, -- Rowan Tommins [IMSoP]