Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:16719
Return-Path: <schst@php-tools.net>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 16915 invoked by uid 1010); 16 Jun 2005 08:56:06 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 16896 invoked from network); 16 Jun 2005 08:56:06 -0000
Received: from unknown (HELO pb1.pair.com) (127.0.0.1)
  by localhost with SMTP; 16 Jun 2005 08:56:06 -0000
X-Host-Fingerprint: 217.160.167.162 a15162455.alturo-server.de Linux 2.6
Received: from ([217.160.167.162:43254] helo=mail.rot3.de)
	by pb1.pair.com (ecelerity 1.2 r(5656M)) with SMTP
	id 6F/27-20931-E9E31B24 for <internals@lists.php.net>; Thu, 16 Jun 2005 04:55:58 -0400
Received: from [172.17.6.127] (p4d23e3d4.np.schlund.de [212.227.35.77])
	by mail.rot3.de (Postfix) with ESMTP id BE75F854625;
	Thu, 16 Jun 2005 10:56:49 +0200 (CEST)
Message-ID: <42B13E9A.7080706@php-tools.net>
Date: Thu, 16 Jun 2005 10:55:54 +0200
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Lukas Smith <lsmith@php.net>
Cc: internals@lists.php.net
References: <FE.11.20931.54730B24@pb1.pair.com>
In-Reply-To: <FE.11.20931.54730B24@pb1.pair.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] forward compatibility "public" in 4.4
From: schst@php-tools.net (Stephan Schmidt)

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.

Just my 2 cts,

Stephan