Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82651
Return-Path: <yohgaki@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 29857 invoked from network); 14 Feb 2015 00:10:38 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 14 Feb 2015 00:10:38 -0000
Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.43 as permitted sender)
X-PHP-List-Original-Sender: yohgaki@gmail.com
X-Host-Fingerprint: 209.85.216.43 mail-qa0-f43.google.com  
Received: from [209.85.216.43] ([209.85.216.43:35429] helo=mail-qa0-f43.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id B3/52-15073-D729ED45 for <internals@lists.php.net>; Fri, 13 Feb 2015 19:10:38 -0500
Received: by mail-qa0-f43.google.com with SMTP id bm13so14895260qab.2
        for <internals@lists.php.net>; Fri, 13 Feb 2015 16:10:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:in-reply-to:references:from:date:message-id
         :subject:to:cc:content-type;
        bh=TpLpPOjDNGsRWKIJfh9CT5eo6LYUKxmn6Rlll2yH38o=;
        b=UzoXE9+etQxFsdGGzIcmsJMQoTsIYwVsN62/fR6FD1C09DIZIMyC4VjLUVR3VJ+fAd
         VfA3Z8Ed6PsaDMll7bRBdbnJIgVVzvTS+jogSJmJNP1gcIMSXDE3xlm8pWTj37iCm2vt
         LfI6x+hvyWR20PHOWS3nh4ihEfpP0C1XoubyAZLlJFAmzulZz307kDsG4c9i4MbTCM1c
         edND8qi8xo98v10TprXgttpzsdPvCepEQaOjAI3SMZtLZsDc5Kx1DZ9TbeQYWuqDmI7G
         aNTd4PDfOPK95BJn7+AUrIordqpZr46RP7uS9R2MhOn2JH6d4YmdiYv5R0MaQKDPq8tR
         c4/g==
X-Received: by 10.229.190.6 with SMTP id dg6mr30686754qcb.16.1423872635377;
 Fri, 13 Feb 2015 16:10:35 -0800 (PST)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
Received: by 10.229.198.8 with HTTP; Fri, 13 Feb 2015 16:09:55 -0800 (PST)
In-Reply-To: <CAF+90c-7w1fLqmffYvPRhmtt8rzESEpSmW8vfMD-YfLt1mG_8w@mail.gmail.com>
References: <CAF+90c-7w1fLqmffYvPRhmtt8rzESEpSmW8vfMD-YfLt1mG_8w@mail.gmail.com>
Date: Sat, 14 Feb 2015 09:09:55 +0900
X-Google-Sender-Auth: qrjLGFQ_Y4kcZnnXXyYbDMpL3rU
Message-ID: <CAGa2bXaxs760ZVGharG2zZizh-+f4S+kiLv5uH4+UeDFZ4rpkA@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11336798a31f97050f012ec7
Subject: Re: [PHP-DEV] [RFC] Exceptions in the engine
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

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

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.

Anyway, +1

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--001a11336798a31f97050f012ec7--