Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101984
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.48 as permitted sender)
To: "Christoph M. Becker" <cmbecker69@gmx.de>, Sara Golemon
 <pollita@php.net>, PHP internals <internals@lists.php.net>
References: <CAESVnVqAukZUar4xMk5Pr52u83m2RFq3iN=DRjJM18-izdqX=A@mail.gmail.com>
 <1e29d1b7-dbf4-35d5-61cc-8348c195984a@gmx.de>
Message-ID: <1a373841-649b-aef0-1eea-637980463bbd@gmail.com>
Date: Sun, 18 Mar 2018 14:49:20 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:59.0)
 Gecko/20100101 Thunderbird/59.0
MIME-Version: 1.0
In-Reply-To: <1e29d1b7-dbf4-35d5-61cc-8348c195984a@gmx.de>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: [RFC] Base Conversion Clowniness
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

>> https://wiki.php.net/rfc/base-convert
> 
> Is there any chance to revive this RFC?  There are at least three
> tickets in the bug tracker regarding the sloppy behavior of base_convert():

I think if we want to take this RFC forward it should be reduced to
either proposing one action, instead of four, or at the worst case,
choice of two for vote.

It also needs BC impact section added - AFAIK it may break some tests
and _php_math_basetozval is PHPAPI, which means besides 4 uses in core,
any extension could be using it and that extension may not be prepared
for it working differently. Which means if we change it, the failure
behavior that happens should be such that application ignoring it would
not have trouble - at least not worse than today.

-- 
Stas Malyshev
smalyshev@gmail.com