Re: PHP6 OOP compiler feature question / request
| From: | Sean Coates | Date: | Thu, 11 May 2006 19:56:04 +0000 |
| Subject: | Re: PHP6 OOP compiler feature question / request | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-23271@lists.php.net to get a copy of this message | ||
> In any event, I'm just trying to indicate that others may also face
> issues if they have PHP4 apps with these sorts of keywords in them.
"try" has been a reserved word (documented) since Fri Oct 1 08:07:16
2004 UTC:
http://cvs.php.net/viewcvs.cgi/phpdoc/en/appendices/reserved.xml?view=diff&r1=1.48&r2=1.49
See:
http://php.net/manual/en/reserved.php
(which admittedly needs work)
"You cannot use any of the following words as constants, class names,
function or method names."
I do understand the original question, and I supposed it IS technically
possible to determine the context of a T_TRY token, but nonetheless,
it's bad practice to have functions named the same as reserved words
(even where allowed).
S