Re: [RFC] Deprecate remains of string evaluated code assertions
| From: | Claude Pache | Date: | Wed, 31 May 2023 22:20:22 +0000 |
| Subject: | Re: [RFC] Deprecate remains of string evaluated code assertions | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-120491@lists.php.net to get a copy of this message | ||
> Le 31 mai 2023 à 14:08, G. P. B. <george.banyard@gmail.com> a écrit :
>
> Hello internals,
>
> I would like to start the discussion about deprecating various remains from
> the now removed string code evaluated assertions functionality of assert().
>
> The RFC is located on the wiki at the following address:
> https://wiki.php.net/rfc/assert-string-eval-cleanup
>
> Initially, this was part of the mass PHP 8.3 deprecation RFC, but only the
> assert_options() function was part of it.
>
> Best regards,
>
> George P. Banyard
Hi,
Although your RFC says that the
zend.assertions ini setting has superseded
assert.active for a while, the “official” php.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/91fd5641cde138b8894a48c921929b6e4abd5c97/php.ini-development#L1604
I bet that many people (myself included) follows the advice given in php.ini.
Another point: Your RFC is missing assert.quiet_eval...
—Claude