Re: [PHP-DEV] Don't silence chr function arguments error

Em seg, 29 de abr de 2019 às 13:01, Sara Golemon escreveu: > On Mon, Apr 29, 2019 at 2:37 AM Nikita Popov wrote: > >> > The idea is to merge in PHP-7.4, but if there's a consensus that this >>> > should go into PHP 8 only, so it is :) >>> > >>> > Technically a BC break, so 8.0 would be the prefe

Re: [PHP-DEV] Don't silence chr function arguments error

On Mon, Apr 29, 2019 at 2:37 AM Nikita Popov wrote: > > The idea is to merge in PHP-7.4, but if there's a consensus that this >> > should go into PHP 8 only, so it is :) >> > >> > Technically a BC break, so 8.0 would be the preferred branch IMO. >> > > As this would be a TypeError on 8.0, I think

Re: [PHP-DEV] Don't silence chr function arguments error

On Mon, Apr 29, 2019 at 3:44 AM Sara Golemon wrote: > On Sun, Apr 28, 2019 at 6:05 PM Gabriel Caruso > wrote: > > > Currently, if you pass an argument that is not an integer, it will simply > > return an empty string: https://3v4l.org/FF2nA. > > > Not entirely accurate. It outputs a one-characte

Re: [PHP-DEV] Don't silence chr function arguments error

On Sun, Apr 28, 2019 at 6:05 PM Gabriel Caruso wrote: > Currently, if you pass an argument that is not an integer, it will simply > return an empty string: https://3v4l.org/FF2nA. Not entirely accurate. It outputs a one-character string (the null byte). > In case you pass more than > 1 argume

[PHP-DEV] Don't silence chr function arguments error

Hello Internals. I'd like to discuss a small change, but that demands a discussion, for a function in PHP's Core: https://php.net/chr . Currently, if you pass an argument that is not an integer, it will simply return an empty string: https://3v4l.org/FF2nA. In case you pass mo