Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80455
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.1 \(1993\))
In-Reply-To: <CAMUwpuR2QbvSoiKM=r_gc3hexvvTn0mxJ52hvkueRoGm3f8XXQ@mail.gmail.com>
Date: Wed, 14 Jan 2015 10:22:27 +0000
Cc: PHP Internals List <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <76F9DAD3-5A22-4A53-8262-CF6B33D80FC3@ajf.me>
References: <8DCD1B72-C81D-499E-B455-E4A042CD76E6@ajf.me> <CAMUwpuR2QbvSoiKM=r_gc3hexvvTn0mxJ52hvkueRoGm3f8XXQ@mail.gmail.com>
To: Julien Pauli <jpauli@php.net>
Subject: Re: [PHP-DEV] [RFC] Scalar Type Hints v0.2
From: ajf@ajf.me (Andrea Faulds)


Hi Julien,

> On 14 Jan 2015, at 10:14, Julien Pauli <jpauli@php.net> wrote:
>=20
> Using declare() IMO, is a PITA.
> Everything that can be done without the use of declare(), must be done =
without declare().
>=20
> I would have prefered different syntax, like the ones we disccussed =
many years ago , having strict checks with the foo(string $a) syntax, =
and non-strict check with the foo((string) $a) syntax.

Actually, this approach came about mostly to avoid that. I don=E2=80=99t =
really like the idea of mixing and matching weak and strict type checks. =
Having some functions using (int) and (string), others use int and =
string, and others still use both, would be confusing. Plus, it would =
mean that you=E2=80=99d be forced to follow the personal preference of =
the API authors.

With this RFC, yes, you have to put an extra line at the top of the =
file. But it has the advantage that everything follows the same =
behaviour, even extension/built-in functions. That=E2=80=99s what I like =
about it.

--
Andrea Faulds
http://ajf.me/