Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106198
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
In-Reply-To: <88b65a46-f080-ae08-d89e-ee6c4299a19c@heigl.org>
Date: Tue, 9 Jul 2019 12:21:56 +0200
Cc: internals@lists.php.net
Content-Transfer-Encoding: quoted-printable
Message-ID: <6BE96F43-19D5-465E-B93F-0B3CC2E11F25@gmail.com>
References: <CANZOY=Dn-fJGG2FRjBjFB1joMgLKtvxpPetEb64RMN5NHfku_w@mail.gmail.com>
 <CADyq6s+kTjoSPLSraoRUG5-dH2mCMsratgPx_rGiGJEQHEsDEA@mail.gmail.com>
 <C193AABB-C7C0-4D7F-B437-E83C4E463E04@cschneid.com>
 <88b65a46-f080-ae08-d89e-ee6c4299a19c@heigl.org>
To: Andreas Heigl <andreas@heigl.org>
Subject: Re: [PHP-DEV] [VOTE] Strict operators directive
From: claude.pache@gmail.com (Claude Pache)



> Le 9 juil. 2019 =C3=A0 12:09, Andreas Heigl <andreas@heigl.org> a =
=C3=A9crit :
>=20
>=20
>=20
> Am 09.07.19 um 12:06 schrieb Christian Schneider:
>> Am 09.07.2019 um 11:30 schrieb Marco Pivetta <ocramius@gmail.com>:
>>> I wasn't sure about the full implications of this, but after some =
thought,
>>> the worst that can happen is excessive strictness, requiring to drop =
a
>>> single declaration on top of a file =F0=9F=91=8D
>>=20
>> When you drop the declaration on top of the file the semantics of =
your operators suddenly change, e.g.
>> 	"42" < "7"
>> changes from true to false and you get subtle bugs.
>>=20
>> And if you try to read other people's code (or even try to copy/paste =
it) then make sure you keep in mind which mode they are programming in.
>=20
> But that's the same for `declare(strict_types=3D1);`
>=20
> Cheers
>=20
> Andreas

No, it=E2=80=99s not the same thing as declare(strict_types=3D1).

With declare(strict_types=3D1), you just get additional TypeErrors. It =
will not actually change the semantics of code that works in both =
non-strict-types mode and strict-types mode. This is a useful feature =
when refactoring legacy code.

The worst thing that can happen with declare(strict_types=3D1), is that =
code won=E2=80=99t work any more.

The worst thing that can happen with declare(strict_operators=3D1), is =
that code will change semantics.

=E2=80=94Claude=