Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:19531
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 14:04:28 +0200
Message-ID: <00A2E2156BEE8446A81C8881AE117F192C15D6@companyweb>
Thread-Topic: [PHP-DEV] return /* by reference */ new Foo() in PHP4
Thread-Index: AcXMxzIQ5ahVYk6bSi6RpL3jTUkSngAAGARQ
To: <internals@lists.php.net>
Subject: AW: [PHP-DEV] return /* by reference */ new Foo() in PHP4
From: mp@webfactory.de ("Matthias Pigulla")

Sorry, Olli, if that kind of ignores your statements, but I would like
not to distract from the issue. IIRC, what you suggested is called
"boxing" in C# and would lead too far here.

I wanted to focus only on the "return new ..." case and only on PHP4, as
"return new" is a very special case. This particular construct is really
unambiguous and the workaround on the PHP language level is really
nonsense.

As to the notices, I will gladly accept them and take them as a helpful
pointers when "fixing" my "broken" code. The problem is that this
particular case causes a lot of "white noise" notices (at least in
heavily OO apps), as IMHO "return new" is not something that needs to be
fixed by me.

I have been strolling around in a lot of places where the changed
behaviour is being discussed, but I haven't seen a sound rationale for
*this particular* case yet.

Kind regards,
Matthias