Re: when $a = &new class is necessary

From:	Sascha Grossenbacher	Date:	Mon, 24 Sep 2007 19:29:41 +0000
Subject:	Re: when $a = &new class is necessary
References:	1 2 3 4	Groups:	php.pear.dev
Request:	Send a blank email to pear-dev+get-48167@lists.php.net to get a copy of this message

Christian Schmidt schrieb:

Gregory Beaver wrote:
This will replace 1 E_STRICT with another, as we won't be able to use the "static" keyword.
Right - but the "static" warning can be muted using a custom error handler, the "=&" warning can't when using an opcode cache. Christian But your example does not change anything. Somewhere in the code, directly or within PEAR::makeNew, the "=& new" has to be there..

I understand PHP5 friendliness different than you, for me it means that the code should act the same way on php4 and php5, which means, the & needs to be used. E_STRICT is not a warning or even an error, it is a help to writer better and faster php5 code. To solve your op-code cache problem, I would suggest you to disable display_errors/error_reporting, it does not affect your custom error_handler in any way. Sascha