Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:120679
MIME-Version: 1.0
References: <CAFPFaM+2eUsN9YUdUBEyr6XTe7QagyDBS8_F_LZH00ujJM8shw@mail.gmail.com>
 <72F136AA-768F-4577-80EF-22212DB50EF3@gmail.com>
In-Reply-To: <72F136AA-768F-4577-80EF-22212DB50EF3@gmail.com>
Date: Mon, 26 Jun 2023 16:05:35 +0100
Message-ID: <CAFPFaMJEByW8Wt-ppgYHxAud4GAXTvtgC4OyrK6DfNsmO=hvLQ@mail.gmail.com>
To: Claude Pache <claude.pache@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000006b3e4805ff09afa9"
Subject: Re: [PHP-DEV] [RFC] Deprecate remains of string evaluated code assertions
From: george.banyard@gmail.com ("G. P. B.")

--0000000000006b3e4805ff09afa9
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, 31 May 2023 at 23:20, Claude Pache <claude.pache@gmail.com> wrote:

> Although your RFC says that the `zend.assertions` ini setting has
> superseded `assert.active` for a while, the =E2=80=9Cofficial=E2=80=9D ph=
p.ini file still
> advises to modify the value of `assert.active` rather than the one of
> `zend.assertion` in order to switch behaviour at runtime:
>
>
> https://github.com/php/php-src/blob/91fd5641cde138b8894a48c921929b6e4abd5=
c97/php.ini-development#L1604
>
> I bet that many people (myself included) follows the advice given in
> `php.ini`.
>

This talks about run-time modification, which is something that I don't
think should be done in practice, nor is often done.


> Another point: Your RFC is missing `assert.quiet_eval`...
>

I have clarified that this was indeed removed in PHP 8.0.
https://wiki.php.net/rfc/assert-string-eval-cleanup

Best regards,

--0000000000006b3e4805ff09afa9--