Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:22985
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Wed, 26 Apr 2006 21:00:40 -0400
Reply-To: Jason Garber <jason@ionzoft.com>
Organization: IonZoft, Inc.
Message-ID: <1724175614.20060426210040@ionzoft.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
CC: Brian Moon <brianm@dealnews.com>, internals@lists.php.net
In-Reply-To: <444FF716.6070201@lerdorf.com>
References: <444FF5CD.2010805@dealnews.com> <444FF716.6070201@lerdorf.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Passing functions to function by reference
From: jason@ionzoft.com (Jason Garber)

Hello Rasmus,

RL> In 5.1 this now throws an E_STRICT instead of a warning.  It is still a
RL> bad idea to pass a tempvar by reference, so yes, you should strive to 
RL> write E_STRICT clean code.

At the possible expense of being blamed and flamed, I'll say it...

ifsetor($var, 'default') would go a long way to accommodate E_STRICT
code.

-- 
Best regards,
 Jason                            mailto:jason@ionzoft.com

Wednesday, April 26, 2006, 6:41:26 PM, you wrote:

RL> Brian Moon wrote:
>> In PHP4, you could do:
>> 
>> function test()
>> {
>>        return array(1,2,3);
>> }
>> 
>> $var = array_shift(test());
>> 
>> PHP 5.0 broke this.  There was a fatal error on the array_shift that 
>> only variables could be passed by reference.  There was a good argument 
>> for it.  So, we started migrating our code.
>> 
>> Well, seems this works in 5.1.  So, my question is, was it an 
>> intentional "fix" or will this break again and we need to continue to 
>> watch for this?

RL> In 5.1 this now throws an E_STRICT instead of a warning.  It is still a
RL> bad idea to pass a tempvar by reference, so yes, you should strive to 
RL> write E_STRICT clean code.

RL> -Rasmus