Re: [PHP-DEV] Consistent case-insensitive module registry lookups

Hi,


I don't think making them all case-sensitive is better. Now, I understand that,
most people in 2026 like stricter parsing. I indeed do either.
However, PHP is in a stage in it's lifecycle that it should take the BC break into serious
consideration. In this proposal, we "trade" consistency with BC breaks, and therefore I
want to keep the break effectively small. Changing three independent functions'
behavior is surely worse than one, and since we've already keep the "bad" habit of
processing case-insensitive extension names for decades, in my honest opinion it is
more reasonable to only fix the one case-sensitive case.  


You've made a good point about the documentation. That's a documentation error in
the get_extension_funcs function and should be fixed.


Considering branching: I don't want to get 8.6 RMs in trouble of these small changes,
they surely doesn't qualifies as a urgent feature that can be merged after the soft
feature freeze. Since I forget to make it clear: this should target 8.7 :)


(Or, if 8.6 RMs want this to go into 8.6, please feel free to provide feedbacks)


Cheers to all!


Weilin