Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85157
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ez.no designates 157.56.112.107 as permitted sender)
To: Leigh <leight@gmail.com>, Lester Caine <lester@lsces.co.uk>
CC: PHP Internals List <internals@lists.php.net>
Thread-Topic: [PHP-DEV] [RFC][Accepted] Scalar Type Declarations V0.5
Thread-Index: AQHQYCy6J3HXOe26D0+UirydXppeFJ0f+goAgABg6YCAAI13gIAAcmGA
Date: Tue, 17 Mar 2015 23:53:35 +0000
Message-ID: <E602B239-95F0-42CE-9978-B92C8F8F92EA@ez.no>
References: <CAAyV7nEtdFSdPMieK0EvdO+moCqDw7KH59=Lr3+pA10rn=isoQ@mail.gmail.com>
 <55079692.6050405@gmail.com> <5507E7DD.3010908@lsces.co.uk>
 <CAPwsocGBHjBtem0UM+-=d8bZ6s44+0f+ACLgKbcNpcuxKwVetw@mail.gmail.com>
In-Reply-To: <CAPwsocGBHjBtem0UM+-=d8bZ6s44+0f+ACLgKbcNpcuxKwVetw@mail.gmail.com>
Accept-Language: nb-NO, de-DE, en-US
Content-Language: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <22B3D984411B0342AC65A518B1BA24C2@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Mar 2015 23:53:35.3274
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: f606c019-4e72-4e2e-8583-51197302e349
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM3PR07MB387
Subject: Re: [PHP-DEV] [RFC][Accepted] Scalar Type Declarations V0.5
From: andre.romcke@ez.no (=?iso-8859-1?Q?Andr=E9_R=F8mcke?=)

> On Mar 17, 2015, at 18:04 , Leigh <leight@gmail.com> wrote:
>=20
> On 17 March 2015 at 08:37, Lester Caine <lester@lsces.co.uk> wrote:
>=20
>> To help towards that end, can someone who understands what is wanted
>> from the weak type hint mode actually produce a summary of that as it is
>> very difficult to extract just what has now been agreed for that area of
>> type hinting. A base that can be used to review some of the other
>> discussions to put that to bed. Others might appreciate a similar
>> summary of the 'type_error' mode as well? As a base for the
>> documentation on the user manual updates?
>=20
>=20
> Not sure what is "difficult to extract"
>=20
> https://wiki.php.net/rfc/scalar_type_hints_v5#behaviour_of_weak_type_chec=
ks
>=20
> It's all right there...


That part answers what has been agreed (or rather accepted), but not who th=
e
weak mode is for, and why.

Tried to sum that up last week when there was still discussions on this:
http://share.ez.no/blogs/core-development-team/php-7-sth-from-user-perspect=
ive

TL;DR;  weak mode is for api consumers, aka normal php users, while strict =
is
 for the actual target users of this features: api (library/framework) crea=
tors.

Post also argues for why Zeev's adjustments to weak sth handling should sti=
ll
be done, as well as arguing for disallowing/fixing closure hint in strict m=
ode.


ar=