Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112577
MIME-Version: 1.0
References: <CAFPFaMKbo+o5k7NcbPEUORrisLCEvhiyw_VZD_JRYnPA9W=+Xw@mail.gmail.com>
In-Reply-To: <CAFPFaMKbo+o5k7NcbPEUORrisLCEvhiyw_VZD_JRYnPA9W=+Xw@mail.gmail.com>
Date: Mon, 21 Dec 2020 22:31:02 +0100
Message-ID: <CAFPFaM+tmcia72soDX0UR0fW9JX3pnMXucroKZSaZ8_JPGPPHw@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000006be8cb05b7002da7"
Subject: Re: [PHP-DEV] Follow up on Octal literal RFC
From: george.banyard@gmail.com ("G. P. B.")

--0000000000006be8cb05b7002da7
Content-Type: text/plain; charset="UTF-8"

On Mon, 21 Dec 2020 at 19:36, G. P. B. <george.banyard@gmail.com> wrote:

> Now, onto the weird special case, which looks like a bug in the
> implementation of base_convert() as
> var_dump(base_convert('O', 8, 10));
> Will emit the following deprecation warning (but only if the starting base
> is 8):
> Deprecated: Invalid characters passed for attempted conversion, these have
> been ignored in %s on line %d
> string(1) "0"
> But when using octdec() it doesn't.
>

Correction, this is not the case. I was mistakenly using 'O' (capital o
instead of zero) in the test case.
This does not emit a deprecation notice.

Best regards,

George P. Banyard

--0000000000006be8cb05b7002da7--