Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:16723 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 30761 invoked by uid 1010); 16 Jun 2005 09:27:09 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 30746 invoked from network); 16 Jun 2005 09:27:09 -0000 Received: from unknown (HELO pb1.pair.com) (127.0.0.1) by localhost with SMTP; 16 Jun 2005 09:27:09 -0000 X-Host-Fingerprint: 82.165.35.142 thinkforge.org Linux 2.4/2.6 Received: from ([82.165.35.142:3699] helo=mail.mayflowersystem.com) by pb1.pair.com (ecelerity 1.2 r(5656M)) with SMTP id B7/78-20931-CE541B24 for ; Thu, 16 Jun 2005 05:27:09 -0400 Received: (qmail 12185 invoked by uid 60010); 16 Jun 2005 09:27:06 -0000 Received: from 84.154.70.6 by mail (envelope-from , uid 89) with qmail-scanner-1.24 (uvscan: v4.3.20/v4362. spamassassin: 2.63. Clear:RC:1(84.154.70.6):. Processed in 0.507414 secs); 16 Jun 2005 09:27:06 -0000 Received: from unknown (HELO ?192.168.0.19?) (schlueter@mayflower.de@84.154.70.6) by 0 with (RC4-MD5 encrypted) SMTP; 16 Jun 2005 09:27:05 -0000 To: internals@lists.php.net Date: Thu, 16 Jun 2005 11:26:43 +0200 User-Agent: KMail/1.8 Cc: Sebastian Mendel References: <42B13E9A.7080706@php-tools.net> <95.E7.20931.05441B24@pb1.pair.com> In-Reply-To: <95.E7.20931.05441B24@pb1.pair.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-ID: <200506161126.44054.johannes@php.net> Subject: Re: [PHP-DEV] forward compatibility "public" in 4.4 From: johannes@php.net (Johannes Schlueter) On Thursday 16 June 2005 11:27, Sebastian Mendel wrote: > > I guess, this will more likely produce an error message like this: > > > > Parse error: syntax error, unexpected T_PUBLIC, expecting T_STRING in > > public.php on line 2 right > > So I'm strongly against this change. If you want to run PHP4 code in > > PHP5, disable E_STRICT. +1 > id dont know, but isnt there a difference between where the keywords are > placed? No, it's a parser keyword and a keyword can't be used as a function name. > and if it is so, then this would also be a candidate for > > "NOTICE: 'public' is a keyword in PHP 5" in php 4.4 No. No "errors" for "forward compatibility". johannes