Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:37563
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.132 as permitted sender)
Message-ID: <00f801c8b1c5$942cd960$4001a8c0@foxbox>
Reply-To: "Steph Fox" <steph@zend.com>
To: "Hannes Magnusson" <hannes.magnusson@gmail.com>
Cc: "internals" <internals@lists.php.net>
References: <021601c8b141$bbf64a50$4001a8c0@foxbox> <7f3ed2c30805081429q239a5d14k1d80e29cbd46acf6@mail.gmail.com>
Date: Fri, 9 May 2008 12:12:31 +0100
Organization: Zend Technologies
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] allow_call_time_pass_reference
From: steph@zend.com ("Steph Fox")

Hannes,

> I'd say throw the warning if the switch is on and someone does
> call-time-pass-by-reference and turn that switch off by default.

That's exactly the situation we have now - a warning when the INI setting is 
changed, for code that by default runs silently.

And we offer a recommendation to throw that warning in production. That's 
the real WTF!

If call-time pass-by-ref is something that needs to be warned about, warn by 
default so everyone will get to see it during development. If it isn't 
something that needs to be warned about, why throw a warning at all?

- Steph

>
> -Hannes
>
> -- 
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>