Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:16721 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 24979 invoked by uid 1010); 16 Jun 2005 09:20:18 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 24963 invoked from network); 16 Jun 2005 09:20:18 -0000 Received: from unknown (HELO sebastianmendel.de) (127.0.0.1) by localhost with SMTP; 16 Jun 2005 09:20:18 -0000 X-Host-Fingerprint: 84.148.168.194 p5494A8C2.dip0.t-ipconnect.de Received: from ([84.148.168.194:10022] helo=localhost.localdomain) by pb1.pair.com (ecelerity 1.2 r(5656M)) with SMTP id 95/E7-20931-05441B24 for ; Thu, 16 Jun 2005 05:20:17 -0400 Message-ID: <95.E7.20931.05441B24@pb1.pair.com> To: internals@lists.php.net Date: Thu, 16 Jun 2005 11:27:00 +0200 User-Agent: Mozilla Thunderbird 1.0+ (Windows/20050614) MIME-Version: 1.0 References: <42B13E9A.7080706@php-tools.net> In-Reply-To: <42B13E9A.7080706@php-tools.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Posted-By: 84.148.168.194 Subject: Re: [PHP-DEV] forward compatibility "public" in 4.4 From: lists@sebastianmendel.de (Sebastian Mendel) Stephan Schmidt wrote: > Hi, > > Lukas Smith wrote: >> I think its a good idea to have, to make it somewhat possible to >> prepare for the PHP5 E_STRICT world, while still developing PHP4 >> compatible code. I could for example see this help increase the PHP5 >> adoption inside PEAR, since this would allow us to make some packages >> E_STRICT compatible without throwing out PHP4 compatibility (inside >> PEAR we consider increased major PHP versions to be a BC break, but >> not minor versions). > > Will this still work in PHP 4.4 as it did in 4.3 if you apply the patch? > > function public($foo) { > var_dump($foo); > } > public(42); > > 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 > > So I'm strongly against this change. If you want to run PHP4 code in > PHP5, disable E_STRICT. id dont know, but isnt there a difference between where the keywords are placed? 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 -- Sebastian Mendel www.sebastianmendel.de www.sf.net/projects/phpdatetime | www.sf.net/projects/phptimesheet