Hi! > +1 on doing this. I can understand having case-insensitive constants, but > having both case-sensitive and case-insensitive at the same time is weird > and rather useless. I imagine the only reason why this "feature" exists in > the first place is to support arbitrary casing for true/false/null, which > is better handled by special-casing these particular constants (something > we already do for various other reasons). This will simplify the language
If we support all case-insensitive constants that are predefined (not sure if any exts do that but we have to support those too if they do) then I don't see a big problem in phasing-out user-defined ones. After a quick gihub scan, I see there's some usage of case-insensitive constants but most of it doesn't seem to be actually using that thing (i.e. usages are in the same case as definition). -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
