Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82652
Return-Path: <nikita.ppv@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 31420 invoked from network); 14 Feb 2015 00:15:17 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 14 Feb 2015 00:15:17 -0000
Authentication-Results: pb1.pair.com header.from=nikita.ppv@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=nikita.ppv@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.179 as permitted sender)
X-PHP-List-Original-Sender: nikita.ppv@gmail.com
X-Host-Fingerprint: 209.85.212.179 mail-wi0-f179.google.com  
Received: from [209.85.212.179] ([209.85.212.179:55112] helo=mail-wi0-f179.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 69/A2-15073-4939ED45 for <internals@lists.php.net>; Fri, 13 Feb 2015 19:15:17 -0500
Received: by mail-wi0-f179.google.com with SMTP id hi2so15656978wib.0
        for <internals@lists.php.net>; Fri, 13 Feb 2015 16:15:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        bh=7T0BavvUVSQLDeOqpK13gvRFh+mOcX7avpanex3FfRw=;
        b=veYa7/LTfMiCpkJw+M9Z2KoasgSFZSmlxx7KqKZQlWfU7pza5gA3RtZzjpDD1Ny4da
         AGS/rCEK8R3l95GhAIrXEMpUUnIcpYU7msHFzG+QOiieABlUN1iNK++gaAE87UhLMTkf
         uj/flgCXatkFR4E9sz0YuPcR0onQEsmZgx0HFr9IWT+n+1v0/jm7twv8sdQ73pFfzliG
         zQuxajvl3dSf6BAiaNPRARNCWQcDkcC37OQTUkSqOO32YgVhTsAlywNgjEvbNuU34cDU
         2uN/Mfc4r2gc+bau6wh246iOu/sKmt2LVaI530nC0n/qbpw344H10Z/wf7dcvlOdWlws
         VpdQ==
MIME-Version: 1.0
X-Received: by 10.180.74.206 with SMTP id w14mr11993837wiv.71.1423872913625;
 Fri, 13 Feb 2015 16:15:13 -0800 (PST)
Received: by 10.27.10.168 with HTTP; Fri, 13 Feb 2015 16:15:13 -0800 (PST)
In-Reply-To: <CAGa2bXaxs760ZVGharG2zZizh-+f4S+kiLv5uH4+UeDFZ4rpkA@mail.gmail.com>
References: <CAF+90c-7w1fLqmffYvPRhmtt8rzESEpSmW8vfMD-YfLt1mG_8w@mail.gmail.com>
	<CAGa2bXaxs760ZVGharG2zZizh-+f4S+kiLv5uH4+UeDFZ4rpkA@mail.gmail.com>
Date: Sat, 14 Feb 2015 01:15:13 +0100
Message-ID: <CAF+90c9WLwSNS8YpnkVtBVXw8hdna-5MEehkNcWg4TnV7Xkm_w@mail.gmail.com>
To: Yasuo Ohgaki <yohgaki@ohgaki.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=f46d041824dc38d76d050f013fcd
Subject: Re: [PHP-DEV] [RFC] Exceptions in the engine
From: nikita.ppv@gmail.com (Nikita Popov)

--f46d041824dc38d76d050f013fcd
Content-Type: text/plain; charset=UTF-8

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
>

--f46d041824dc38d76d050f013fcd--