Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119874
Message-ID: <7fe2339ed7ba287811e9437d029696a9b9d8a332.camel@sandfox.me>
To: internals@lists.php.net
Date: Mon, 10 Apr 2023 22:12:31 +0300
In-Reply-To: <CAFPFaMLghRYP4ioCkfa7WKhTAz+1gWgcZ5mWYAunkb9f3g=fdA@mail.gmail.com>
References: 
	<CAFPFaMLghRYP4ioCkfa7WKhTAz+1gWgcZ5mWYAunkb9f3g=fdA@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.46.4 (3.46.4-1.fc37) 
MIME-Version: 1.0
Subject: Re: [PHP-DEV] [RFC] New core autoloading mechanism with support for
 function autoloading
From: sandfox@sandfox.me (Anton Smirnov)

Hello George,

I'm not sure I'm 100% correct but I think that this RFC still allows to
call different functions for the same code, just not in the same run.

Consider this pseudocode:

//- funcs.php

namespace My;

function myfunc(...) { ... }
function array_map(...) { ... }

//- code1.php

namespace My;

myfunc(1); // autoload triggered
// bonus points if it's a different file or some obscure method
array_map(strlen(...), []); // My\array_map

//- code2.php

namespace My;

// no prior autoload
array_map(strlen(...), []); // global array_map

And if I understand the current order of execution correctly, here is a
more extreme example:

//- moreextreme.php

namespace My;

if (some_random()) {
  array_map('My\myfunc', []); // global array_map
} else {
  array_map(myfunc(...), []); // My\array_map
}

--=20
Anton