Re: [PHP-DEV] [RFC] Deprecate remains of string evaluated code assertions

2023-06-27 Thread G. P. B.
I am going to group the response from the 3 emails. On Tue, 27 Jun 2023 at 09:17, Claude Pache wrote: > Although the specific comment in the php.ini file talks about runtime > switching, it is in fact irrelevant whether it is set at runtime or not. > More concretely; I use currently the settings

Re: [PHP-DEV] [RFC] Deprecate remains of string evaluated code assertions

2023-06-27 Thread Claude Pache
> Le 27 juin 2023 à 10:36, Claude Pache a écrit : > > > >> Le 26 juin 2023 à 17:06, G. P. B. a écrit : >> >> On Wed, 31 May 2023 at 13:08, G. P. B. wrote: >> >>> Hello internals, >>> >>> I would like to start the discussion about deprecating various remains >>> from the now removed strin

Re: [PHP-DEV] [RFC] Deprecate remains of string evaluated code assertions

2023-06-27 Thread Claude Pache
> Le 26 juin 2023 à 17:06, G. P. B. a écrit : > > On Wed, 31 May 2023 at 13:08, G. P. B. wrote: > >> 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

Re: [PHP-DEV] [RFC] Deprecate remains of string evaluated code assertions

2023-06-27 Thread Claude Pache
> Le 26 juin 2023 à 17:05, G. P. B. a écrit : > > On Wed, 31 May 2023 at 23:20, Claude Pache > wrote: >> 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 >>

Re: [PHP-DEV] [RFC] Deprecate remains of string evaluated code assertions

2023-06-26 Thread G. P. B.
On Wed, 31 May 2023 at 13:08, G. P. B. wrote: > 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://w

Re: [PHP-DEV] [RFC] Deprecate remains of string evaluated code assertions

2023-06-26 Thread G. P. B.
On Wed, 31 May 2023 at 23:20, Claude Pache wrote: > 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

Re: [PHP-DEV] [RFC] Deprecate remains of string evaluated code assertions

2023-05-31 Thread Claude Pache
> Le 1 juin 2023 à 00:20, Claude Pache a écrit : > > Another point: Your RFC is missing `assert.quiet_eval`... > (In fact, it is probable that the `assert.quiet_eval` ini setting and the ASSERT_QUIET_EVAL constant have been removed in PHP 8, but that the documentation has not been updated.)

Re: [PHP-DEV] [RFC] Deprecate remains of string evaluated code assertions

2023-05-31 Thread Claude Pache
> Le 31 mai 2023 à 14:08, G. P. B. 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:

[PHP-DEV] [RFC] Deprecate remains of string evaluated code assertions

2023-05-31 Thread G. P. B.
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 wa