> On 17 Mar 2021, at 03:11, Jordi Boggiano <j.boggiano@seld.be> wrote:
>
>
> On 16/03/2021 15:02, Stephen Reay wrote:
>>> On 16 Mar 2021, at 20:07, Jordi Boggiano <j.boggiano@seld.be> wrote:
>>>
>>>
>>> P.S: While I am here looking at spl_* docs, it seems to me like spl_autoload_call
>>> should be deprecated in favor of class_exists, and spl_autoload_extensions + spl_autoload also
>>> probably should be deprecated or at least marked as antiquated in the docs, and not migrated to
>>> autoload_* like you suggested doing for spl_autoload_register/unregister in another RFC.
>>>
>>>
>>
>> Edit: wrong sending address, again. Sending for list, apologies for the dupe.
>>
>> I don’t have a huge amount of interest in this, except to say: If someone wants to add a
>> core function to make Composer’s autoloader work faster, that’s fine and dandy, it doesn’t
>> hurt to provide the building blocks for common patterns. But pushing your own biases about
>> non-Composer class autoloading being “antiquated” or “deprecated” is a step too far.
>
> I assume that refers to my P.S. note.
>
> I did not mean to offend anyone, I merely have never seen anyone use these before. It seems
> like this relies on include_path being set and then having big dirs full of class files that now
> become autoloadable, but that doesn't play well with namespaces and doesn't let you
> organize stuff very much unless you set every dir in the include_path. Call me biased but that does
> not seem very user friendly.
>
> Anyway this is completely unrelated to the RFC at hand, it was a side note, so let's leave
> it at that I guess.
>
> --
>
> Jordi Boggiano
> @seldaek - https://seld.be
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php
>
It’s not about “offending” anyone. It’s about the inappropriateness of the author of a
userland library that includes an autoload component, calling for the removal/docu-shunning of a
built-in autoload function, with apparently zero actual knowledge of how it works, to boot.
spl_autoload works just fine with namespaces, and files organised into subdirectories
(under an include_path entry) mapped to the namespace names. It has worked that way since 5.3.3 -
over a decade ago.
Your comments about this are both factually wrong, and inappropriate, given your “role”.