Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82599
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.200 as permitted sender)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
In-Reply-To: <CACwt+JdHCYYVMbuuAZ73N_sfOkQHJ7_EkOtPWtqJcNW7Xgjn3w@mail.gmail.com>
Date: Fri, 13 Feb 2015 11:13:10 +0000
Cc: PHP Internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <EE83CD8A-BAFA-43AC-8CD0-5F123BF96299@ajf.me>
References: <CACwt+JdHCYYVMbuuAZ73N_sfOkQHJ7_EkOtPWtqJcNW7Xgjn3w@mail.gmail.com>
To: Patrick ALLAERT <patrickallaert@php.net>
Subject: Re: [PHP-DEV] [VOTE] Scalar Type Hints
From: ajf@ajf.me (Andrea Faulds)

Hi,

> On 13 Feb 2015, at 09:37, Patrick ALLAERT <patrickallaert@php.net> =
wrote:
>=20
> Voted "no" because of the reasons already mentioned by a bunch of =
others here.
>=20
> Weak type hint as presented earlier: +1 (and very good job Andrea =
about that!).
> declare(strict_types=3D1): -1, not only about the syntax, but also =
about the mixed mode it introduces.
>=20
> I'm pretty confident that this RFC will "pass" with just above 2/3 of =
majority while it could reach much more.
>=20
>  I am pretty sure that if this RFC doesn't include a strict type mode =
_the way it is proposed_ (or even, not at all, as part of another =
related RFC), it would have some "no" converted to "yes" and would have =
a wider adoption, which is for sure a better option than relying on a =
voting mechanism which still is a supporting tool, we're not politicians =
after all :)

It wouldn=E2=80=99t have wider adoption. Excluding a large portion of =
the PHP community (which favours strict types) and giving them something =
which doesn=E2=80=99t work for their use cases (weak types) is not going =
to win any fans.

> Andi's suggestion about an E_STRICT_TYPES sounds very reasonable and =
much more in line with how PHP deals with "errors=E2=80=9D.

I don=E2=80=99t think E_STRICT_TYPES is a good idea. Global error =
handlers are, well, global. They not only affect your own code, but =
everything within the request, including libraries you use. So you can =
use them (and break every library you use), or not use them (and now =
it=E2=80=99s useless).

What this RFC does is let individual files choose one mode or the other. =
This is far better for interoperability.

Thanks.

--
Andrea Faulds
http://ajf.me/