Re: Consistent case-insensitive module registry lookups

From: Date: Tue, 18 Aug 2026 14:51:39 +0000
Subject: Re: Consistent case-insensitive module registry lookups
References: 1 2 3 4 5 6  Groups: php.internals 
Request: Send a blank email to internals+get-132261@lists.php.net to get a copy of this message
Hi, Il 18/08/2026 15:04, Aleksander Machniak ha scritto:
I don't agree that case-sensitive here would be better. There's multiple variations of extension names, e.g. PDO, SimpleXML, Xdebug, swoole. And for example --disable-simplexml exists (btw, is this one case- insensitive? why not --disable-SimleXML?). The point is that in some places you don't have to know the exact casing. So, why would I have to know when checking for an extension existence? More importantly, is it possible currently to have both Myext and myext enabled? I'd say there might be more arguments for case-insensitive solution here.
Wearing my RM hat, I've already mentioned that I'd be perfectly fine with 8.6 having a case‑insensitive ini_get_all(). Wearing any other hat I might have, I agree that keeping extension names case‑insensitive makes far more sense. Another example is composer.json and its ext-* dependencies, which are also generally written in their lowercase variants. To me, this would be one of those useless BC breaks that make the user experience worse instead of improving it. Cheers -- Matteo Beccati

« previous php.internals (#132261) next »