Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:23272 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 74797 invoked by uid 1010); 11 May 2006 20:00:52 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 74782 invoked from network); 11 May 2006 20:00:52 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 May 2006 20:00:52 -0000 X-PHP-List-Original-Sender: jasper@album.co.nz X-Host-Fingerprint: 210.55.31.88 mail.album.co.nz Linux 2.5 (sometimes 2.4) (4) Received: from ([210.55.31.88:38454] helo=mail.album.co.nz) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 51/20-19568-2F793644 for ; Thu, 11 May 2006 16:00:51 -0400 Received: from mail.album.co.nz (www.album.co.nz [127.0.0.1]) by mail.album.co.nz (Postfix) with ESMTP id B5EADF5894; Fri, 12 May 2006 08:00:45 +1200 (NZST) X-Spam-Checker-Version: SpamAssassin 3.1.1-gr0 (2006-03-10) on www.album.co.nz X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=unavailable version=3.1.1-gr0 Received: from [192.168.0.9] (222-153-191-138.jetstream.xtra.co.nz [222.153.191.138]) by mail.album.co.nz (Postfix) with ESMTP id 2F534F5842; Fri, 12 May 2006 08:00:45 +1200 (NZST) Message-ID: <446397EA.4000503@album.co.nz> Date: Fri, 12 May 2006 08:00:42 +1200 Organization: Album Limited User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: Sean Coates CC: internals References: <446222C8.3090101@smashlabs.com> <44623E75.4070304@zend.com> <446273F7.2090702@iamjochem.com> <446370F9.9060105@smashlabs.com> <446391D4.4010600@album.co.nz> <44639486.4040500@album.co.nz> <446396D4.1060008@caedmon.net> In-Reply-To: <446396D4.1060008@caedmon.net> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] PHP6 OOP compiler feature question / request From: jasper@album.co.nz (Jasper Bryant-Greene) -----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-----