[PHP-DEV] Deprecated partially supported callables: should is_callable() throw a deprecation notice ?

2022-03-15 Thread Juliette Reinders Folmer
L.s., I've just been looking in detail at the Partially Supported Callables deprecation RFC: https://wiki.php.net/rfc/deprecate_partially_supported_callables The RFC explicitly excludes the `is_callable()` function and the `callable` type from throwing deprecation notices. The

Re: [PHP-DEV] [VOTE] Undefined Variable Error Promotion

2022-03-15 Thread Patrick ALLAERT
Hello Mark and the list, Le mar. 15 mars 2022 à 21:36, Mark Randall a écrit : > Who knows, maybe PHP 9 can be the version that removes remove *all* > warnings from the zend engine. > This is not far from the reason why I voted "no". I am not against the fact this warning becomes an error per

Re: [PHP-DEV] [VOTE] Undefined Variable Error Promotion

2022-03-15 Thread Mark Randall
On 15/03/2022 19:32, Sara Golemon wrote: What I'm hearing is that we also need an RFC for promoting 'Undefined index...' warnings to Errors as well. We do. If it would pass or not is another matter, it would need someone braver than I to take it up. I think there's some other engine

Re: [PHP-DEV] [VOTE] Undefined Variable Error Promotion

2022-03-15 Thread Sara Golemon
On Tue, Mar 15, 2022 at 2:08 PM Miguel Rosales wrote: > > The RFC states: > > > > | If the code does not currently emit a “Warning: Undefined variable > > | $varname” then it is out of scope for this RFC. This RFC does NOT > > | apply to array indexes. > > > > That explicitly excludes undefined

Re: [PHP-DEV] [VOTE] Undefined Variable Error Promotion

2022-03-15 Thread Miguel Rosales
Christoph M. Becker wrote on 15/3/22 19:17: On 15.03.2022 at 17:54, Côme Chilliet wrote: Le lundi 14 mars 2022, 18:18:55 CET Mark Randall a écrit : I have started the vote for promoting undefined variable access to throw an Error exception. The vote will run for 2 weeks until March 28th

Re: [PHP-DEV] [VOTE] Undefined Variable Error Promotion

2022-03-15 Thread Christoph M. Becker
On 15.03.2022 at 17:54, Côme Chilliet wrote: > Le lundi 14 mars 2022, 18:18:55 CET Mark Randall a écrit : > >> I have started the vote for promoting undefined variable access to throw >> an Error exception. >> >> The vote will run for 2 weeks until March 28th 2022. >> >>

Re: [PHP-DEV] [VOTE] Undefined Variable Error Promotion

2022-03-15 Thread Côme Chilliet
Le lundi 14 mars 2022, 18:18:55 CET Mark Randall a écrit : > I have started the vote for promoting undefined variable access to throw > an Error exception. > > The vote will run for 2 weeks until March 28th 2022. > > https://wiki.php.net/rfc/undefined_variable_error_promotion This does not

Re: [PHP-DEV] [RFC] [VOTE] Allow null and false as stand-alone types

2022-03-15 Thread Derick Rethans
On 15 March 2022 15:41:45 GMT, "Côme Chilliet" wrote: >Le samedi 12 mars 2022, 19:30:00 CET G. P. B. a écrit : >> true is not a type in PHP compared to false, therefore it is not included. >> I'm working on a proposal to add true as a type to PHP, but that's a >> seperate RFC and discussion. >

Re: [PHP-DEV] [RFC] [VOTE] Allow null and false as stand-alone types

2022-03-15 Thread Côme Chilliet
Le samedi 12 mars 2022, 19:30:00 CET G. P. B. a écrit : > true is not a type in PHP compared to false, therefore it is not included. > I'm working on a proposal to add true as a type to PHP, but that's a > seperate RFC and discussion. Was there ever an RFC for adding literal values to the type

Re: [PHP-DEV] [RFC][Under discussion] Deprecate ${} string interpolation

2022-03-15 Thread Guilliam Xavier
Hi Mike, Lynn, and Kamil; I feel like this sub-thread has derailed from the initial topic... As already said, this RFC is *not* about the general "variable variables" feature, but about *the `"${...}"` syntax inside interpolated strings* (i.e. double-quoted or heredoc), which can be rewritten to