Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82936
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain lerdorf.com designates 209.85.192.178 as permitted sender)
Message-ID: <54E30991.80108@lerdorf.com>
Date: Tue, 17 Feb 2015 01:27:45 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Benjamin Eberlei <kontakt@beberlei.de>
CC: PHP internals <internals@lists.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>	<54E290E5.3020508@lerdorf.com>	<CAESVnVpXmmfDh6iqT=n27iHQ21_QxPWkez_=bEc1Dpn+MNrjMg@mail.gmail.com>	<54E2AD88.6040206@lerdorf.com>	<CAESVnVoFD7-A2_a1ZPR9av2tiVbbs7D0NUt0TihH-dQFvhkH6Q@mail.gmail.com>	<54E2FA57.6050009@lerdorf.com> <CAEPJdumj2aT9_zchhBBqbetB+L9s-QwRRMukrRpdbB_fH3iLOw@mail.gmail.com>
In-Reply-To: <CAEPJdumj2aT9_zchhBBqbetB+L9s-QwRRMukrRpdbB_fH3iLOw@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="anPLOqkqBORkVh3AlTqC7HInQSCuVkI4J"
Subject: Re: [PHP-DEV] Reviving scalar type hints
From: rasmus@lerdorf.com (Rasmus Lerdorf)

--anPLOqkqBORkVh3AlTqC7HInQSCuVkI4J
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 02/17/2015 01:11 AM, Benjamin Eberlei wrote:
> I think curl_setopt is a misleading example in the typehinting
> discussion, because
> this kind of API does not benefit from it. The third argument depends
> on the second argument and requires a "generic" type in code:
>=20
> curl_setopt(resource $ch, int $option, mixed $data);
>=20
> It won't be possible to change this (or any similar API) with strict
> type hints.=20
>=20
> The code to convert a boolean $data to integer in the VERIFYPEER case i=
s
> manually
> implemented and therefore subject to the implementors design decisions.=


Sure, I realize this, but it is the bool->int coercion example that is
always brought up. A static analysis type checker would have trouble
catching this, but both PHP and Hack apply that coercion at runtime:

       case CURLOPT_SSL_VERIFYHOST:
           if(Z_BVAL_PP(zvalue) =3D=3D 1) {

The runtime could say, hey, I am in strict mode here and you are passing
me an array of strings which I am coercing to a boolean. Not cool.

-Rasmus


--anPLOqkqBORkVh3AlTqC7HInQSCuVkI4J
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlTjCZEACgkQlxayKTuqOuAWfwCfYFair7VGiwV9aYCWrak+4rwv
cW4An0zCnFb3dpaKZ+tRAwQFBcfKcCWs
=uaiv
-----END PGP SIGNATURE-----

--anPLOqkqBORkVh3AlTqC7HInQSCuVkI4J--