Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75390
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.207 as permitted sender)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
In-Reply-To: <2f218b4d8cffb1a55e464e715c319b1f@mail.gmail.com>
Date: Sun, 13 Jul 2014 12:48:09 +0100
Cc: Alain Williams <addw@phcomp.co.uk>,
 Lester Caine <lester@lsces.co.uk>,
 internals@lists.php.net
Content-Transfer-Encoding: quoted-printable
Message-ID: <B6D27AF4-9F2A-41A8-B6A5-A6551C313F15@ajf.me>
References: <08503591-EFC8-48E6-984E-FFC292C5EA5F@ajf.me> <53C2178E.7070705@sugarcrm.com> <53C24061.6050503@lsces.co.uk> <20140713101840.GR6540@phcomp.co.uk> <2f218b4d8cffb1a55e464e715c319b1f@mail.gmail.com>
To: Zeev Suraski <zeev@zend.com>
Subject: Re: [PHP-DEV] [RFC] Scalar Type Hinting With Casts (re-opening)
From: ajf@ajf.me (Andrea Faulds)


On 13 Jul 2014, at 12:35, Zeev Suraski <zeev@zend.com> wrote:

> I haven't yet reviewed the conversion table in detail, but unless I'm
> missing something, this RFC is in fact much more in the spirit of PHP =
-
> and implements type juggling - unlike the previous incarnation of =
strict
> typing that almost made it into PHP.  It's a bit too strict to my =
liking
> (especially around conversion of floating point to int, which should =
pass
> and perhaps generate a notice IMHO), but this is a big step towards =
the
> spirit of what I proposed together with Lukas back in 2010
> (https://wiki.php.net/rfc/typecheckingstrictandweak) - which was an
> alternative to the strong typing suggested by several others.
>=20
>=20
> Type juggling is an *inherent* feature of PHP.  Paraphrasing what =
Rasmus
> said several years ago(*), 'if you implement this [strong typing], =
please
> don't call it PHP'.
>=20
> Again, luckily, what Andrea proposes isn't strong typing.  It still
> maintains the most important properties of type juggling - e.g. the
> ability to work with strings coming in as input (GET/POST/etc.) =
without
> having to worry about typing.

Right. I think this RFC would strengthen PHP=92s weak typing guarantees, =
because while internal functions will convert to the right type and =
hence avoid issues with strings and such not acting quite like integers =
in some situations, userland functions usually don=92t. This RFC would =
mean that, at least for =93hinted=94 functions, =
user_land_function($_GET[=91id=92]) should work just as well as =
internal_function($_GET[=91id=92]).

Also, it=92s not really =93what Andrea proposes=94, it=92s Anthony=92s =
proposal, even if he is sadly absent from the list these days. I=92m =
just trying to fix up the patch, iron out remaining wrinkles, and get =
this into PHP.

--
Andrea Faulds
http://ajf.me/