Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:19529
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 9 Oct 2005 12:14:38 +0200
Message-ID: <00A2E2156BEE8446A81C8881AE117F192C15D5@companyweb>
Thread-Topic: [PHP-DEV] return /* by reference */ new Foo() in PHP4
Thread-Index: AcXMVm3QaH7Yu3J/SgKHnV+PJK5eoQAYlg6w
Cc: <internals@lists.php.net>
Subject: AW: [PHP-DEV] return /* by reference */ new Foo() in PHP4
From: mp@webfactory.de ("Matthias Pigulla")


> > So, in case of "return new", wouldn't it make sense to remove the=20
> > warning as the code is 'legal'? And please, don't start a new "it's=20
> > just a friendly notice" flame war.
>=20
>      It's just a notice, tune your error_reporting level accordingly.

Sorry, but that is just a stupid killer argument. I thought I had
written something like "please, don't start a new *it's just a friendly
notice* flame war".=20

May I conclude that what you really want to say is:

"Yes, return /*byref*/ new Foo() _is_ bad code _unless_ inside Foo's
constructor, $this is passed around and somebody somewhere stores yet
another reference to it. Accept that you wrote broken code: return new
Foo() is wrong, it needs to be return $tmp =3D& new Foo()."

Shaking his head,
Matthias