Detailed explanation of php define constants

How define in php is implemented:

Note that a loop starting with repeat also uses the goto statement T_T

The function of this code is: For int, float, string, bool, resource, null, use these values ​​directly when actually defining the constants. For object, you need to convert the object into one of the above 6 types (if it is still an object after the conversion, continue the conversion) How to convert object into one of 6 types? From the code point of view, there are two methods:

1, Z_OBJ_HT_P(val)->get, after macro expansion, it is (*val).value.obj.handlers->get

2, Z_OBJ_HT_P(val)->cast_object, after macro expansion, it is (*val).value.obj.handlers->cast_object

Handlers is a structure containing many function pointers. For detailed definition, see _zend_object_handlers. The function pointers in this structure are used to operate objects, such as reading/modifying object attributes, obtaining/calling object methods, etc... get and cast_object are also among them.

For general objects, PHP provides the standard cast_object function zend_std_cast_object_tostring. The code is located in php-src/zend/zend-object-handlers.c:

From the above specific implementation, the default cast_object is to find the __tostring method in the class and then call...

Back to the initial example, define('foo', $a), since $a is an instance of A, and __toString is defined in class A, the foo constant is actually equal to the return value bar of toString.

ps: Keep digging for little details.

1, define has a return value Usually we define constants directly as: define('foo', 123); However, judging from the implementation of define, it has a return value. According to the description in the manual:

Return TRUE on success, or FALSE on failure.

Under what circumstances will define fail? for example:

The above code contains two situations. One is that we try to redefine the predefined constants of the PHP kernel, such as PHP_INT_MAX, which It will obviously fail. The second case is that we have defined a constant FOO somewhere in the code, and then define it again in the next program, which will also cause failure. Therefore, it is best to write all the constants that need to be defined together when coding to avoid name duplication.

2, there is no limit on constant names Let's review the implementation of define again, which only determines whether the name is in the form of XXX::YYY.

In other words, define has almost no requirements for its name, and of course it does not require that the name be a legal PHP variable name. Therefore, we can let define's constants have some weird names. For example:

But if such a constant is defined, it is If it cannot be used directly, a syntax error will be reported. The correct usage is as follows: