Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81637
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.220.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <2AABD912-C2A3-4877-8B40-8E391B2BE45F@ajf.me>
References: <8DCD1B72-C81D-499E-B455-E4A042CD76E6@ajf.me>
	<B0C5801F-7D46-4CB0-9B2E-AF18C44DAF14@ajf.me>
	<CA+9eiLtPVoDYT71fYrZfxPk6a_m7ErFd2w8UBvu9ZeTEbnm4kA@mail.gmail.com>
	<1E54E93F-8CE1-469F-BE1F-DD2F1DF76E39@ajf.me>
	<CA+9eiLv3YUdvvo7NbkMOoJEb4eVUyoHEYzoAPweJp3FXVfFNMQ@mail.gmail.com>
	<5175DE01-ADC9-4A0B-8343-820C53B30054@ajf.me>
	<CA+9eiLv+FCqiEmaM-NjGtMnpxyYb+x7zgrR5pneJmZowauDYBA@mail.gmail.com>
	<2AABD912-C2A3-4877-8B40-8E391B2BE45F@ajf.me>
Date: Mon, 2 Feb 2015 23:26:08 +0400
Message-ID: <CA+9eiLvQ9e7jr=FkMzTNX-Wo778ihJSXMHo=j_gA5c_NywLjPA@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e0115fd02273451050e1fed2c
Subject: Re: [PHP-DEV] [RFC] Scalar Type Hints v0.2
From: dmitry@zend.com (Dmitry Stogov)

--089e0115fd02273451050e1fed2c
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Mon, Feb 2, 2015 at 10:12 PM, Andrea Faulds <ajf@ajf.me> wrote:

> Hi Dmitry,
>
> > On 2 Feb 2015, at 18:22, Dmitry Stogov <dmitry@zend.com> wrote:
> >
> > So, one of the advantages of strict type hinting is the ability to catc=
h
> potential errors.
> > For example when we pass 67 to setBody(string $message).
>
> Yes, that sort of thing is easily caught by strict type checks. They=E2=
=80=99re
> also able to catch things that are sometimes okay for weak hints, sometim=
es
> not. For example, some *but not all* strings are accepted for integer and
> float parameters, and some *but not all* floats are accepted for integer
> parameters. Strict checks make this much simpler and not dependant on the
> value: either some type is accepted, or it isn=E2=80=99t.
>

Agree. Strict type checks are simple and may be implemented more efficient.
But in case we have to support both - weak and strict, this won't make any
advantage.


>
> Because of that, strict types can actually be effectively analysed
> ahead-of-time by static analysers, IDEs and so on, and so you can catch
> some types of errors while editing your code, without even needing to run
> it. This is quite a powerful feature. Nikita might have more to say on th=
at.
>

Static analyzers can work with weak conversion rules as well.
Anyway, this is not directly related to run-time semantic we discuss now.

Thanks. Dmitry.


>
> Thanks.
> --
> Andrea Faulds
> http://ajf.me/
>
>
>
>
>

--089e0115fd02273451050e1fed2c--