Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:89933
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain basereality.com from 209.85.160.177 cause and error)
MIME-Version: 1.0
In-Reply-To: <CANaX5ndsVxurJcN9=z91q8P6=j3jh53xcwz1+=pw11rtEzDt=Q@mail.gmail.com>
References: <DUB129-W10F0D9A42A48CED194AE98F9FD0@phx.gbl>
	<CANaX5ndsVxurJcN9=z91q8P6=j3jh53xcwz1+=pw11rtEzDt=Q@mail.gmail.com>
Date: Wed, 30 Dec 2015 23:43:25 +0000
Message-ID: <CA+kxMuS=4z8Rpax+JYxpAEgMJKt0qmtxViz_Xp-LD57yOJNv1Q@mail.gmail.com>
To: Davey Shafik <davey@php.net>
Cc: Thomas Punt <tpunt@hotmail.co.uk>, 
	"internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC] Number Format Separator
From: danack@basereality.com (Dan Ackroyd)

On 30 December 2015 at 23:00, Davey Shafik <davey@php.net> wrote:

> how will settype($string, int|float), intval(), floatval(), is_numeric()
> and ctype_digit() work with this change?

My understanding is that those functions will continue to work as they
do currently. The numeric literals are resolved by the compiler into
numbers when the code is compiled, so there will be no difference.
i.e. this RFC does not affect PHP at runtime at all, only the compile
step.

> What will var_dump()  etc. show?

var_dump(1_000_000) will have the same output as var_dump(1000000)

> there should be an explicit way to support "1_000_000" => (int) 1_000_000. This
> should be part of the RFC.

I don't think it should be part of this RFC. That sounds like a
completely different RFC, or is covered by NumberFormatter::parse().

cheers
Dan