Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80128
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.50 as permitted sender)
Message-ID: <54A8788E.30905@gmail.com>
Date: Sat, 03 Jan 2015 15:17:34 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Nikita Popov <nikita.ppv@gmail.com>, 
 PHP internals <internals@lists.php.net>
References: <CAF+90c-x7=N2hujczr7RCbKRHNEwP9BXM1sKvVaaKbqY2WHufw@mail.gmail.com>
In-Reply-To: <CAF+90c-x7=N2hujczr7RCbKRHNEwP9BXM1sKvVaaKbqY2WHufw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Remove hex support in numeric strings
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> I'd like to propose removing support for hexadecimal strings in the
> is_numeric_string() function, in order to achieve consistency with ordinary
> integer and float casts:
> 
>     https://wiki.php.net/rfc/remove_hex_support_in_numeric_strings
> 
> This change drops a WTF in our conversion semantics and should have low BC
> impact.

While I'm usually all for preserving BC in this case I think removing
the inconsistency is better and the use case is weird enough that it
makes little sense to implicitly support it. Given that we have options
with both filter and hexdec _and_ casts do not support it, I think this
RFC would do the right thing.

-- 
Stas Malyshev
smalyshev@gmail.com