Bug #77100 [Opn]: Inconsistent behavior between constants and magic constants

Edit report at https://bugs.php.net/bug.php?id=77100&edit=1 ID: 77100 Updated by: cmb@php.net Reported by: fabien dot villepinte at gmail dot com Summary: Inconsistent behavior between constants and magic constants Status: Open Type: Bug Package: Scripting Engine problem PHP Version: Irrelevant Block user comment: N Private report: N New Comment: FWIW, the docs[1] say: | All these "magical" constants are resolved at compile time, | unlike regular constants, which are resolved at runtime. [1] <http://php.net/manual/en/language.constants.predefined.php> Previous Comments: ------------------------------------------------------------------------ [2018-11-03 16:12:34] fabien dot villepinte at gmail dot com Description: ------------ The functions define(), defined() and constant() don't work the same way whether the name of the constant given as an argument is the name of an already defined constant or the name of a magic constant. For instance : define('PHP_EOL', 0); // returns false and emits a notice define('__DIR__', 0); // returns true __DIR__; // returns the path of the current directory constant('__DIR__'); // returns the value of the user-defined constant, 0 in this case There is nothing in the documentation mentioning this case, so I can't say if the current behavior is correct or not. Test script: --------------- <?php var_dump(defined('__LINE__')); var_dump(define('__LINE__', 'test')); var_dump(constant('__LINE__')); var_dump(__LINE__); Actual result: -------------- bool(false) bool(true) string(4) "test" int(5) ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=77100&edit=1