Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:37799
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: softfail (pb1.pair.com: domain zend.com does not designate 64.97.136.190 as permitted sender)
Message-ID: <009c01c8bc00$1ed8dd90$4401a8c0@foxbox>
Reply-To: "Steph Fox" <steph@zend.com>
To: "Stan Vassilev | FM" <sv_forums@fmethod.com>,
	<internals@lists.php.net>
References: <012701c8bb44$68f8b880$4401a8c0@foxbox> <48342DB7.2020108@isdg.net> <353f2c6f0805211141m9719d58xe0a128adbc14b656@mail.gmail.com> <353f2c6f0805211146p43d6aa96u9e6e03e82490b1c@mail.gmail.com> <cd5680a20805220105u36085eb4t95a4e1a384982845@mail.gmail.com> <325D72617BCF43A39670646B85FDB5FD@pc>
Date: Thu, 22 May 2008 12:36:46 +0100
Organization: Zend Technologies
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="UTF-8";
	reply-type=response
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RFC: allow_call_pass_by_reference
From: steph@zend.com ("Steph Fox")

Hi Stan,

> There is a use case for the function allowing *explicitly* call-time pass 
> by reference, because the function works both ways in subtly different 
> ways.

This RFC isn't about whether or not this behaviour should be deprecated. It 
simply recommends that a warning be thrown by default in PHP 5.3 so that 
people will know to fix their code. The rationale for this is that there is 
ALWAYS a warning thrown in PHP 6, with no possibility to avoid that warning. 
It is also still marked deprecated in PHP 6, i.e. there is presumably a firm 
intention to remove the possibility for call-time pass-by-ref altogether.

call_time_pass_by_reference behaviour has been deprecated for 8 years plus - 
since before the PHP 4.0 release. If you're writing code that relies on that 
behaviour, either you don't care about the warning or you've never seen it. 
I suspect rather a lot of PHP users have never seen it, because by default 
that warning isn't thrown at all.

If you want to argue that there should be no warning by default, fine. But 
please try to stay on-topic.

Thanks,

- Steph