Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84567
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <76c47c6fbd961958c10bc1a069377a34@mail.gmail.com>
References: <BAY178-W5945DBF18D50C0F91C760DE190@phx.gbl>
	<76c47c6fbd961958c10bc1a069377a34@mail.gmail.com>
Date: Wed, 11 Mar 2015 14:28:01 -0400
Message-ID: <CAAyV7nG1FAVHxtmi=C1Lakm_AfrhSuqSH9+-hS5Xz5zOYTdegw@mail.gmail.com>
To: Zeev Suraski <zeev@zend.com>
Cc: Theodore Brown <theodorejb@outlook.com>, 
	"internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] RE: [VOTE][RFC] Coercive Scalar Type Hints
From: ircmaxell@gmail.com (Anthony Ferrara)

Zeev,

>> You also stated above that false->bool is not supported (I'm guessing
> you
>> meant float->bool). So users would be able to pass "4.3" to a bool
> typehint,
>> but not 4.3? This behavior seems very arbitrary and confusing.
>
> It may be confusing, but only academically so.  Again, this approach tries
> to work well with real world usage - and reject conversions which are
> likely to be erroneous.  "4.3" may look like a floating point number but
> in the context of conversion to boolean, that doesn't matter much.  It's a
> string.

Doesn't that contradict what you've been saying the whole time about
how "13" and 13 and 13.0 are really "the same thing", and as such
should be coerced?

> function bar(float $x)
> $foo = 1;
> bar($foo);  // will definitely fail in strict mode

No, actually it won't fail in strict mode:
https://wiki.php.net/rfc/scalar_type_hints_v5#integers_should_be_accepted_for_strict_float_arguments

Anthony