Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80564
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain devilix.net designates 209.85.214.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAB6YZuwYNGk5L49om9O4UWNWxOM2r3=QJ_oKG3nRLv7BfK7qrg@mail.gmail.com>
References: <8DCD1B72-C81D-499E-B455-E4A042CD76E6@ajf.me>
	<CAPwsocGyv7dp8n=_E1QfrXRSbYZXcHZAPk5F=hDLB070i=SCGA@mail.gmail.com>
	<4E2073DE-0951-498C-97BB-DDAC094F11FA@ajf.me>
	<9a033dd1f223f854e760924d118ab812@mail.gmail.com>
	<CAKUjMCU-57cDpG5ZbDGv10dSqx=Ey40D-WbKxKSnC6oSYOfLWw@mail.gmail.com>
	<2ae0164cb9b9bf1c974d7a3c60af0466@mail.gmail.com>
	<F3BC55CD-38CD-42B7-AE0B-A6D34E3D3875@ajf.me>
	<6105ea99002e634373c09685310e26a6@mail.gmail.com>
	<D39D18B9-A9E5-430E-B00A-E0DE03DAFE8C@ajf.me>
	<e131f1aaf3ae0491f958171df36211f5@mail.gmail.com>
	<85F6139E-6332-4645-91B8-C852B07EA62A@ajf.me>
	<a939cd800e7472c135b4b0e5cc99e683@mail.gmail.com>
	<54B7DA71.1050905@seld.be>
	<CAB6YZuwYNGk5L49om9O4UWNWxOM2r3=QJ_oKG3nRLv7BfK7qrg@mail.gmail.com>
Date: Thu, 15 Jan 2015 18:11:00 +0200
Message-ID: <CAPhkiZy9Sn=L-vWaWhqSUP+b+D15rRkLVyQsw=etCtPkpqyEdg@mail.gmail.com>
To: =?UTF-8?Q?Pavel_Kou=C5=99il?= <pajousek@gmail.com>
Cc: Jordi Boggiano <j.boggiano@seld.be>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] Scalar Type Hints v0.2
From: narf@devilix.net (Andrey Andreev)

Hi,

On Thu, Jan 15, 2015 at 5:31 PM, Pavel Kou=C5=99il <pajousek@gmail.com> wro=
te:
> On Thu, Jan 15, 2015 at 4:19 PM, Jordi Boggiano <j.boggiano@seld.be> wrot=
e:
>>
>> Right now, or with only weak hints, if a library decides to implement st=
rict
>> typing, they'll skip the scalar hints and check types with something lik=
e
>> the assert lib [1]. A user calling it with random data would *always* ge=
t
>> exceptions. There is no way for the library to use scalar hints to play =
nice
>> with weak-typed callers as it would not be able to type check anymore in
>> that case.
>>
>
> Why would the libraries writers use the checks inside the method
> instead of the typing, even in the case of the weak typing? I don't
> see a single reason to do so, because if they ask for an "int" in the
> method signature, they will get an int or the method won't get called
> at all. See the example in the RFC with the "if (!is_int($i))".

You're basically asking what's the difference between weak and strong
typing ... it's rather philosophical. It's the intent that's
important, not the end result, which is why I see the
caller-controlled switch as pointless.

Cheers,
Andrey.