Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:35033
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain horde.org designates 75.144.171.129 as permitted sender)
Message-ID: <20080130121732.69455fae04q2urk0@technest.org>
Date: Wed, 30 Jan 2008 12:17:32 -0500
To: internals@lists.php.net
References: <47A05612.4020505@php.net>
	<1462818236.20080130160605@marcus-boerger.de>
In-Reply-To: <1462818236.20080130160605@marcus-boerger.de>
MIME-Version: 1.0
Content-Type: text/plain;
	charset=ISO-8859-1;
	DelSp="Yes";
	format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (5.0-cvs)
Subject: Re: [PHP-DEV] BC break with callbacks in 5.3
From: chuck@horde.org (Chuck Hagenbuch)

Quoting Marcus Boerger <helly@php.net>:

>   actually it was a bug. We, sorry I, did not spot this in earlier versions.
> Now saying you rely on a bug in PHP 5 to be able to execute PHP 4 code
> simply does not work.

The bug is that with callbacks in PHP 5.3+, E_STRICT is enforced even  
when E_STRICT is turned off. See bug #43231 (I've been unable to use  
PHP 5.3 since November because of this):

http://bugs.php.net/bug.php?id=43231

This works fine:

class foo {
   function bar() {
     echo 'hi';
   }
}

foo::bar();

This throws a warning:

call_user_func(array('foo', 'bar'));


Both should certainly be E_STRICT errors. The 2nd one should not throw  
a warning if E_STRICT is off, though.

-chuck