On Tue, Sep 12, 2017 at 7:43 PM, Stanislav Malyshev <smalys...@gmail.com> wrote: > I don't think HHVM not supporting something can be an argument. > I agree there, though I will offer that part of the reason HHVM has never bothered to support case-insensitive constants is that it's simply never needed to. The only major project that didn't work out of the box was Wordpress, and when they saw my blogpost about their one case-insensitive constant, they switched it to being case-sensitive, because EVEN WORDPRESS thought they'd maintained that BC long enough. :)
> I'm worried about TRUE vs. True vs. true though - I've see all of those used > around the code (not tRuE though ;) and breaking that would add a ton of > meaningless work to maintainers without any upside. Same with NULL/null etc. > We could always special case these in the lexer, or during compile-time constant folding. I agree they're a concern (and already noted as much in my previous reply), but they're an entirely tractable concern. -Sara -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
