Call it: allow reserved words in a class or not?
| From: | Stan Vassilev | FM | Date: | Thu, 06 Nov 2008 03:24:15 +0000 |
| Subject: | Call it: allow reserved words in a class or not? | ||
| Groups: | php.internals | ||
| Request: | Send a blank email to internals+get-41703@lists.php.net to get a copy of this message | ||
Hi,
I just wanted a clarification on this. Currently many of us have class names such as:
Zend_Validate_Interface
Foo_Utils_Array
...and so on. This works fine as it's just a single T_STRING.
As you know, with the new convention, the parser will not encounter T_STRING
"Zend\Validate\Interface" but rather:
T_STRING "Zend"
T_NS_SEPARATOR "\"
T_STRING "Validate"
T_NS_SEPARATOR "\"
T_INTERFACE <-- parse error
I understand it's not trivial to fix this, but I wanted a clarification: is there a plan to do
something about it, or it'll remain an invalid syntax by the time of release of 5.3.
Regards,
Stan Vassilev