Re: [RFC] Exceptions in the engine
| From: | Nikita Popov | Date: | Sat, 14 Feb 2015 00:15:13 +0000 |
| Subject: | Re: [RFC] Exceptions in the engine | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-82652@lists.php.net to get a copy of this message | ||
On Sat, Feb 14, 2015 at 1:09 AM, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote:
> Hi Nikita,
>
> On Tue, Oct 7, 2014 at 6:53 AM, Nikita Popov <nikita.ppv@gmail.com> wrote:
>
>> As such I'm re-proposing this RFC for inclusion in PHP 7:
>>
>> https://wiki.php.net/rfc/engine_exceptions_for_php7
>>
>> The RFC text is essentially the same as previously, with the primary
>> difference being that parse errors are now converted to exceptions as
>> well.
>> This was previously not possible due to limitations in the compiler
>> design.
>>
>
> Are E_WARNING, etc future scope?
> I briefly looked the patch. It seems it covers only engine errors.
> I suppose it's the scope of this RFC, though.
> If API is made adoptable to modules for E_WARNING, etc, it would be
> great.
>
This RFC is strictly about fatal and recoverable fatal errors. Changing any
other error types to exceptions would be a significant
backwards-compatibility break.
Nikita
> Anyway, +1
>
> Regards,
>
> --
> Yasuo Ohgaki
> yohgaki@ohgaki.net
>