Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110282
MIME-Version: 1.0
References: <CAD2kNXAEjKW-VQC3PJUzBR9QTL=UEz=OGSTHNvee5tibDECN_Q@mail.gmail.com>
 <0819e254-c789-e3d6-b23d-08128f195953@gmail.com> <CAD2kNXBuJ-+EAPVNpm9VQXmD5GnjAKP7iveOyDSb3NXGkZCO6Q@mail.gmail.com>
 <aae7117c-1685-79f0-374d-8b4c5284fc51@gmail.com>
In-Reply-To: <aae7117c-1685-79f0-374d-8b4c5284fc51@gmail.com>
Date: Tue, 26 May 2020 13:12:59 -0400
Message-ID: <CAD2kNXBNeV=FWpKOwLFaFL4RjB1r7MPT_bs9qH6Yj_Kjaeow0Q@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000b97a0905a6903556"
Subject: Re: [PHP-DEV] [RFC][DISCUSSION] Error Exceptions mode
From: iggyvolz@gmail.com (Katie Volz)

--000000000000b97a0905a6903556
Content-Type: text/plain; charset="UTF-8"

 On Sun, May 24, 2020 at 7:29 PM Rowan Tommins <rowan.collins@gmail.com>
wrote:

> In my mind error_reporting should make absolutely no difference. As you
> say, this option would be for people who don't want to interact with the
> current error system in any way, and that includes its global
> configuration state.
>

My main concern for this was that it would make implementation more
difficult - however it turned out to be fairly straightforward.

One note on this - currently declare() statements do not allow constants or
expressions in them.  I had to patch zend_compile.c to allow this, so this
will affect other declare statements as well (for example,
declare(ticks=E_ALL - 37) will be valid).  Unknown constants or incorrect
types (ex: declare(error_exception=[]), declare(error_exception=E_ALL -
FOO_BAR)) will fail here.

--000000000000b97a0905a6903556--