TRUE is true, no matter what

NogDog

Just in case anyone wondered, I tried this today based on something I saw in someone else's code:

php -r "define('TRUE', false);var_dump(TRUE);"
bool(true)

🆒

sneakyimp

Finally, the truth! Boole would be proud.

Bonesnap

This code is not false.

dalecosp

So thankful for absolutes.

This Bruce Jenner crap was about to get to me...

Weedpacket

php -r "define('TRUE', false); echo defined('TRUE') ? 'defined' : 'undefined';"
php -r "echo defined('TRUE') ? 'defined' : 'undefined';"
php -r "define('true', false); echo var_dump(true);"

sneakyimp

dalecosp;11045187 wrote:
This Bruce Jenner crap was about to get to me...

Bruce Gender

NogDog

So I guess the built-in constants cohabit with the user-defined constants, and PHP uses the built-ins when it's ambiguous.

$ php -r "define('TRUE', false);var_dump(constant('TRUE'));var_dump(TRUE);"
bool(false)
bool(true)

(Just in case it ever matters 🙂 )

Derokorian

However, if you use case-sensitive argument to define, var_dump still uses the bool not the constant. constant() is the only way to get the value set in define.

NogDog

FYI, this all started for me when I saw something like this in a piece of code someone else was looking at:

abstract class Foo
{
    const TRUE = true;
    const FALSE = false;
    // rest of class...
}

...in which case I suppose self::TRUE would be explicitly separate from TRUE, though I have no idea why the originator thought s/he needed them as class constants -- but it did pique my curiosity. 🙂