Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60078
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 209.85.213.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <op.wcwq1eafidpuyk@slws007.slhq.int>
References: <CAF+90c_ia=YbYGT+rGUhuhi+Aj-VD7ccO5wNc32w_iEFSwNj+g@mail.gmail.com>
	<CAJWj5+HzZQkYsBcHkUOrfrzqb8PBLRsKJ3uX2oLB9pRa6382uA@mail.gmail.com>
	<op.wcwq1eafidpuyk@slws007.slhq.int>
Date: Tue, 17 Apr 2012 13:57:49 +0200
Message-ID: <CAJWj5+HB-TaW=P5mcG8oD8yVJ=E+ayhfj-vLCQWiUZo6hOcrRw@mail.gmail.com>
To: Gustavo Lopes <glopes@nebm.ist.utl.pt>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] is_numeric_string an hexadecimal numbers ("123" == "0x7B")
From: simonsimcity@googlemail.com (Simon Schick)

2012/4/17 Gustavo Lopes <glopes@nebm.ist.utl.pt>:
>
> I think that would be an error. As was mentioned a few months ago when 0b
> was introduced, no other number format has this behavior. You can't do "123"
> == "0b10" or "123" == "0876". Extending this hexadecimal oddity instead of
> eliminating it is inconsistent with the treatment given to those other
> formats.
>
> --
> Gustavo Lopes
>

Hi, Gustavo

That's something I didn't know of ... if we're doing that, it should,
of course, be also be done for the dual system.
The only thing I wonder about is the code examples you're giving ...

I would expect this to work if we start to change something here:

var_dump((int) '0x7b'); // int(123)
var_dump((int) '0b1111011'); // int(123)
var_dump((int) '0123'); // int(123)

The last example was not mentioned here before but as you set in an
example, I did it here as well ...

Bye
Simon