Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79129
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.216 as permitted sender)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
In-Reply-To: <CACwt+JfWULbrJrorM96v35S5=ef8aFrVZTn+4W-7pi_nJUuxkg@mail.gmail.com>
Date: Mon, 24 Nov 2014 16:11:48 +0000
Cc: Levi Morrison <levim@php.net>,
 PHP Internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <ABCD5D3B-E7E2-4A4B-8A51-BD429CB0DA45@ajf.me>
References: <D7C8CEF6-625E-4489-8EFC-8FCAA16302D2@ajf.me> <CAFMT4NodhUcS3f-nnCpxGuR=AA6-g9wTchzeS7faTeu9SSL5xw@mail.gmail.com> <CACwt+JfWULbrJrorM96v35S5=ef8aFrVZTn+4W-7pi_nJUuxkg@mail.gmail.com>
To: Patrick ALLAERT <patrickallaert@php.net>
Subject: Re: [PHP-DEV] [VOTE][RFC] Safe Casting Functions
From: ajf@ajf.me (Andrea Faulds)


> On 24 Nov 2014, at 16:08, Patrick ALLAERT <patrickallaert@php.net> =
wrote:
>=20
>=20
> Le Wed Nov 19 2014 at 10:57:39 PM, Levi Morrison <levim@php.net> a =
=C3=A9crit :
>   - PHP suffers a lot from function bloat and this RFC provides
> multiple functions that do the same thing but differ only in how they
> handle errors. A simple validation of "can this be safely cast to an
> integer without dataloss?" avoid the issue entirely and would be fewer
> functions.
>=20
> My "no" is mostly for the reason above, mentioned by Levi and also =
because of the use of Exception (previously mentioned by Derick as =
well).
>=20
> To improve this RFC, I would:
> - use errors/warnings instead of exceptions (unless there is a more =
global approach on this aspect for PHP 7).

Errors in PHP are horrible to handle. There=E2=80=99s absolutely no =
question of this RFC being revived using errors, at all. If I must, =
I=E2=80=99ll wait until exceptions are inevitably approved for core in =
PHP 7. Assuming they actually are. If they aren=E2=80=99t, I might =
actually quit PHP...

> I would personally appreciate a syntax closer to the current casting =
mechanism, e.g.:
>=20
>     $int =3D (=3Dint) "42"; // result: (int) 42
>     $string =3D (=3Dstring) 42; // result: (string) "42"
>     $int =3D (=3Dint) "foobar"; // result: E_ERROR: Can not cast =
(string) "foobar" strictly to an int
>=20
>     $int =3D (~int) "42"; // result: (int) 42
>     $int =3D (~int) "foobar"; // result: E_WARNING: Can not cast =
(string) "foobar" strictly to an int

PHP already already has enough bizarre syntaxes, I don=E2=80=99t think =
it needs even more.

--
Andrea Faulds
http://ajf.me/