Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81309
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.48 as permitted sender)
Message-ID: <54C90500.1010109@gmail.com>
Date: Wed, 28 Jan 2015 15:49:20 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: PHP Internals <internals@lists.php.net>
References: <54C80F4F.7020905@gmail.com>	<011d01d03ab7$dd725c30$98571490$@tekwire.net>	<CAH-PCH7UstXaV67S141fNxpTMyEwChZs5u9NaY3x53JBgqk3WQ@mail.gmail.com>	<54C8BE99.8070109@gmail.com> <CAH-PCH7fDygM17XVPTeiEfccsQX0oH0Ui5C_mYN=_9osvzQGVw@mail.gmail.com>
In-Reply-To: <CAH-PCH7fDygM17XVPTeiEfccsQX0oH0Ui5C_mYN=_9osvzQGVw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Proposal: Raise severity of undefined constants
From: rowan.collins@gmail.com (Rowan Collins)

Ferenc Kovacs wrote on 28/01/2015 12:13:
>
> ok, I was assuming that by turning it into E_RECOVERABLE_ERROR you 
> would still keep the assuming string behavior if there is a custom 
> error handler which returns true for this error.

I'm undecided on whether the string value or null would make more sense, 
and listed both possibilities in my original post:

 > Proposed behaviour: an E_RECOVERABLE_ERROR is issued; if the error is 
caught, either the existing string behaviour could be retained, or the 
value could be treated as NULL. (I'm open to other alternatives.)

Returning null would probably allow the engine code to be simplified, 
but returning the string would allow people to write compatibility 
layers using a custom error handler.

Regards,
-- 
Rowan Collins
[IMSoP]