Re: PHP6 OOP compiler feature question / request
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
Sean Coates wrote:
>> 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).
This application was developed in 2001, at which point 'try' was not a
keyword and the original developers of the app had no idea it was to
become one.
I'm sure there are many others out there in the same boat.
Jasper
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32)
iD8DBQFEY5fqFfAeHhDzT4gRA++8AKCSDqC+dORY7YD+G8ouxboGwXtigwCdGIrF
H6Yz6oBt9QqeKd5Z7d33DKg=
=zcoJ
-----END PGP SIGNATURE-----
Thread (11 messages)