Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81759
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.220.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <5E952833-7651-40A5-B88C-1701B100F150@ajf.me>
References: <CA+9eiLuueVvYgT-fhCvzBSxzoDioinpc5Eok5OQtGDBG1FZM=w@mail.gmail.com>
	<CAL0xaBEV-vhXQ06QGSJ4pTZSCK=hpampo44uVd9C99FgYb_W+Q@mail.gmail.com>
	<CA+9eiLv3VrpGf-eRmOZiGw=bhfP6xMgHUSZV8WboPHYrYyenrA@mail.gmail.com>
	<5E952833-7651-40A5-B88C-1701B100F150@ajf.me>
Date: Wed, 4 Feb 2015 09:24:59 +0400
Message-ID: <CA+9eiLtdNE+r2_m0AzBRSVzh-Uvn3MqMcWWOKu-rwt08uWCN4w@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: Arvids Godjuks <arvids.godjuks@gmail.com>, PHP Internals <internals@lists.php.net>, 
	Nikita Popov <nikita.ppv@gmail.com>
Content-Type: multipart/alternative; boundary=001a113399e69e7b9c050e3c688b
Subject: Re: [PHP-DEV] What do we need strict scalar type hints for?
From: dmitry@zend.com (Dmitry Stogov)

--001a113399e69e7b9c050e3c688b
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Feb 3, 2015 at 7:14 PM, Andrea Faulds <ajf@ajf.me> wrote:

> Hi Dmitry,
>
> > On 3 Feb 2015, at 04:07, Dmitry Stogov <dmitry@zend.com> wrote:
> >
> > I have similar opinion. Strict typing looks foreign for PHP.
>
> It is in a way, yes. PHP has traditionally been =E2=80=9Cweakly-typed=E2=
=80=9D everywhere.
>
> That being said, we=E2=80=99re not always weakly-typed (there are strict =
type
> checks in some places), and userland code has sometimes done strict type
> checks anyway.
>
> > I see, strict type hints may be useful.
> > Aspecially for testing and error detection, but anyaway, I'm not sure i=
f
> and how it should be enabled. Declare() is a working solution, but it's n=
ot
> excelent.
>
> It=E2=80=99s not a perfect solution, but I haven=E2=80=99t seen anything =
that seems to be
> much better. The best bit about declare() is that it would make strict
> types completely optional, so people who don=E2=80=99t like them wouldn=
=E2=80=99t have to
> use them, even if they call code which does.
>

I agree. It's probably the best solution that we saw. But it's still not
good enough,
It would be great to make the obvious part of the proposal accepted first.
I would suggest to make two separate voting questions.

1) Enable scalar type hinting with standard rules.

2) In addition enable strict type hinting triggered by declare().

Thanks. Dmitry.


>
> --
> Andrea Faulds
> http://ajf.me/
>
>
>
>
>

--001a113399e69e7b9c050e3c688b--