id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
10533	Php 5.3 deprecated errors	mrmist	westi	"There was a ticket #8701 that was meant to look at this, and it was marked as fixed 3 months ago.  Yet today if I load up trunk in PHP5.3 with wp_debug on I get 

PHP Deprecated: Assigning the return value of new by reference is deprecated in E:\webpage\svn\trunk\wp-includes\cache.php on line 103 PHP Deprecated: Assigning the return value of new by reference is deprecated in E:\webpage\svn\trunk\wp-includes\pomo\mo.php on line 171 PHP Deprecated: Assigning the return value of new by reference is deprecated in E:\webpage\svn\trunk\wp-includes\l10n.php on line 407 PHP Deprecated: Assigning the return value of new by reference is deprecated in E:\webpage\svn\trunk\wp-includes\query.php on line 61 PHP Deprecated: Assigning the return value of new by reference is deprecated in E:\webpage\svn\trunk\wp-includes\theme.php on line 1133 PHP Deprecated: Assigning the return value of new by reference is deprecated in E:\webpage\svn\trunk\wp-includes\taxonomy.php on line 617 PHP Deprecated: Assigning the return value of new by reference is deprecated in E:\webpage\svn\trunk\wp-includes\widgets.php on line 320 

Many of which I guess relate to the use of $foo = & new bah.

But anyway, I look back through that ticket and I see that  & ~ E_DEPRECATED was played with a few times, but the final commit never bothered with it.  Should we not have an  & ~ E_DEPRECATED in there somewhere?  Otherwise I can't see a way around the error reports. 

(I didn't re-open the last ticket as it is old and long.)

Hoping this is one of the first things to change once PHP4 support goes."	defect (bug)	closed	normal	2.9	Warnings/Notices	2.9	normal	fixed	has-patch commit tested