Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:96110
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain cschneid.com from 195.226.6.51 cause and error)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.0 \(3226\))
In-Reply-To: <CAJMCqJnyx+MAGF0O674dMxXk3FH6hsnz4qUF1FNG_MUAFdKu_Q@mail.gmail.com>
Date: Fri, 23 Sep 2016 15:51:38 +0200
Cc: internals@lists.php.net
Content-Transfer-Encoding: quoted-printable
Message-ID: <9F330826-CF44-4584-961B-727EEDD9482A@cschneid.com>
References: <CAJMCqJnyx+MAGF0O674dMxXk3FH6hsnz4qUF1FNG_MUAFdKu_Q@mail.gmail.com>
To: Vesa Kaihlavirta <vpkaihla@gmail.com>
Subject: Re: [PHP-DEV] RFC: Strict comparisons
From: cschneid@cschneid.com (Christian Schneider)

Am 19.09.2016 um 15:04 schrieb Vesa Kaihlavirta <vpkaihla@gmail.com>:
> <?php declare(strict_comparisons=3D1);
>=20
> $two =3D "2";
> if ($two > 1) {
>        echo "This sorta works without strict_comparisons=3D1" . =
PHP_EOL;
> }
>=20
> ...would throw a TypeError exception after this change.

This sounds like a bad idea to me: Changing the language semantics of =
something so basic as the comparison operators seems like asking for =
trouble. One programmer will try to incorporate code from non-strict =
parts into strict parts and possibly gets exceptions even though the =
code works. Another programmer is puzzled about all the type casts (or =
even try/catch constructs) when moving code the other way around.

On top of that: Making it a runtime-setting or file-wide declaration =
seems like the most troublesome option.
Reminds me way too much of magic quotes :-)

Let's take a step back: If you want type-safety and your program is more =
or less well-structured then type declarations on function parameters =
should IMHO be more than sufficient.

Regards,
- Chris