Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:58206
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain priacta.com designates 64.95.72.244 as permitted sender)
To: John LeSueur <john.lesueur@gmail.com>, Kris Craig <kris.craig@gmail.com>
CC: Anthony Ferrara <ircmaxell@gmail.com>, Ferenc Kovacs <tyra3l@gmail.com>,
	Michael Morris <dmgx.michael@gmail.com>, "internals@lists.php.net"
	<internals@lists.php.net>
Date: Mon, 27 Feb 2012 17:28:03 -0500
Thread-Topic: [PHP-DEV] Scalar type hinting
Thread-Index: Acz1hv4jxN+zFF2cTyis3+L5qq+CsQAECCTA
Message-ID: <A633CF2D7C7BED41B41F1E64F25507B8069DC46C38@MAILR001.mail.lan>
References: <CAG=uTXEfTBqX7n0_zfGjB_txQFKtZXF4MOo6RHHPSRPerGeKZA@mail.gmail.com>
	<CAKOpQSwP_VXazO1WgQgOWiKTmgiwzorg2=ii+Mdz58a=TKs6VA@mail.gmail.com>
	<CAGovj_O5UQx9aAaYg302i-kKp13CtBKNLmQ48OLHNvk61rM1sw@mail.gmail.com>
	<1330357150.2159.30.camel@guybrush>
	<CAGovj_MUt60EJfG8a7r-cqrC2PKsi8mqh6v_iyNoRDq8q-jh2Q@mail.gmail.com>
	<CAH-PCH6Bre5yzc6r3zxEj3=zZY0PHDOCVQ0s=f8JBDSPnK+5Fw@mail.gmail.com>
	<CAAyV7nFmfhb97CGAK1ZAkp9qb3oCPxbUDnS-Z-v3cP2APcYs=g@mail.gmail.com>
	<CAKOpQSwTGMcuGs5fDvA0kF7QJamooU7hnqtDFMaCh80amt7kcQ@mail.gmail.com>
	<CAKOpQSx_tJfrRx4uRDfcP94bN1qYw=WOktCKf3Xt-AizN=Lk0A@mail.gmail.com>
 <CAGsnKxbBcmZcJjCxuLiu5e-un-7QbTFW4YvHzZUSstq-T4J+jw@mail.gmail.com>
In-Reply-To: <CAGsnKxbBcmZcJjCxuLiu5e-un-7QbTFW4YvHzZUSstq-T4J+jw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: RE: [PHP-DEV] Scalar type hinting
From: johncrenshaw@priacta.com (John Crenshaw)

> -----Original Message-----
> From: John LeSueur [mailto:john.lesueur@gmail.com]=20
>=20
> Maybe this discussion should start from the end of the last discussion on=
 non-strict type hints, where really smart people came up with some options=
 to handle the conversion:
>=20
> https://wiki.php.net/rfc/typecheckingstrictandweak#option_1_current_type_=
juggeling_rules_with_e_strict_on_data_loss
>=20
> The RFC talks about throwing E_STRICT or E_FATAL, and has a couple of opt=
ions for a matrix of conversion rules.

I've actually read that proposal. To some level it is good, but I felt like=
 there were too many problems. E_ERROR is overkill. For comparison, (functi=
on (array $bar) {})('a') generates a catchable fatal error (E_RECOVERABLE_E=
RROR) so that's the furthest this should go in any case, but when dealing w=
ith jugglable types and there's just some unexpected data loss even E_RECOV=
ERABLE_ERROR is too much IMO; E_WARNING or E_NOTICE would be more appropria=
te. IIRC it also failed conversions too aggressively.

John Crenshaw
Priacta, Inc.