Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:83393
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <059701d04d73$bf9a4280$3ecec780$@php.net>
References: <011801d04a07$83ab1c00$8b015400$@php.net>
	<CABDNdAFQsbo-A-gijPCwYDOf3ts-yKpP0tAL--WUaLU26GB-AQ@mail.gmail.com>
	<016f01d04a3a$e9183220$bb489660$@php.net>
	<CAESVnVoM7YbmXA8hTG1O66j+6YX3Xx2Q3uj_F=TPjHA4ws=8JA@mail.gmail.com>
	<d8031ce52e9965c789887e8f7b687a4e@mail.gmail.com>
	<CAESVnVpA+M6iv_zbDmKTEF8Q1zKjwnbi1ucc=UyuUyRr+X+U3w@mail.gmail.com>
	<022801d04ab1$4a0c47d0$de24d770$@php.net>
	<1913e09d7f52541901d8574d2080a63f@mail.gmail.com>
	<CAAyV7nFD=BQ5dBYiKzhbOKTomKmWvruTnb=R_n9mYB-Lz1P9pg@mail.gmail.com>
	<7a5d96b34b98ec1f3ee17be7fa6a1e81@mail.gmail.com>
	<CAPhkiZxpYbaPN1370_HFTVnBA=Jg-rU8DrB2P+2dmRcJfGWPtw@mail.gmail.com>
	<2CBDEB67-3DE3-437D-9AF3-0E6A92027244@zend.com>
	<CAPhkiZwcD3h42=9eak4uP9n2GBE=v0LVP6Ncq9Oz7L91dJ5y5w@mail.gmail.com>
	<4cc0c81c7199a452534bb8edcdb19914@mail.gmail.com>
	<54E589F6.9030002@garfieldtech.com>
	<d62afd01c97a2d00466ac88579fa861c@mail.gmail.com>
	<54E66569.8000709@garfieldtech.com>
	<CAAyV7nG79GbQt_hcAsV15Ad-7k7KjDW43HTGyegHPoswDMNzJA@mail.gmail.com>
	<059701d04d73$bf9a4280$3ecec780$@php.net>
Date: Sat, 21 Feb 2015 10:18:05 -0500
Message-ID: <CAAyV7nGSO_JamVybDjSDyVEbav4Jzb_kBFyxDWxgcnf2e0DQZQ@mail.gmail.com>
To: francois@php.net
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Reviving scalar type hints
From: ircmaxell@gmail.com (Anthony Ferrara)

Francois,

On Fri, Feb 20, 2015 at 8:14 PM, Fran=C3=A7ois Laupretre <francois@php.net>=
 wrote:
> Hi Anthony,
>
> I guess you would keep supporting __toString() ? So, you should probably =
consider 'string' as 'string|object'.
> Adding this case to 'float' meaning 'int|float' and 'callable' resolving =
to 'string|array|object', are you sure it's worth the pain implementing and=
 supporting a dual-mode mechanism, compared to the ruleset I am intending t=
o propose (currently in draft): https://wiki.php.net/rfc/zpp-conversion-rul=
es ?

No. The rules are quite clearly explained in the RFC. The only thing
that can resolve a string hint is a string. __toString is a form of
cast, and hence disallowed in strict mode (because 1: it's not
explicit, 2: it loses significant information).

Callable is an existing rule, which is not subject to the "strict" discussi=
on.

> Actually, using such ruleset, I guess you could infer less, but the diffe=
rence wouldn't be so important.
>
> Only 3 conversions still use value, from which one can be made type-depen=
dent-only if requested during discussion (float to int proposed as lossless=
-only). Every type except int, float, and string are also proposed as 100% =
strict.

None of the conversions use "value". Int, Float, String and Bool all
behave precisely about type. No runtime value information is used
(only runtime type info).

Please read the proposal and see what it says. Don't judge it by what
you assume, but by what it says.

Anthony