Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106199
MIME-Version: 1.0
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>
 <6BE96F43-19D5-465E-B93F-0B3CC2E11F25@gmail.com>
In-Reply-To: <6BE96F43-19D5-465E-B93F-0B3CC2E11F25@gmail.com>
Date: Tue, 9 Jul 2019 13:30:00 +0200
Message-ID: <CANZOY=AAbH+j-fop8VBgH5rZjp0B2CL3Y8p-aWkcF_oydgaHpw@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000003a1b73058d3de235"
Subject: Re: [PHP-DEV] [VOTE] Strict operators directive
From: arnold.adaniels.nl@gmail.com (Arnold Daniels)

--0000000000003a1b73058d3de235
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Jul 9, 2019 at 12:22 PM Claude Pache <claude.pache@gmail.com> wrote=
:

>
>
> > Le 9 juil. 2019 =C3=A0 12:09, Andreas Heigl <andreas@heigl.org> a =C3=
=A9crit :
> >
> >
> >
> > 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
> >>
> >> 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.
> >>
> >> 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.
> >
> > But that's the same for `declare(strict_types=3D1);`
> >
> > Cheers
> >
> > 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 wi=
ll
> not actually change the semantics of code that works in both
> non-strict-types mode and strict-types mode. This is a useful feature whe=
n
> refactoring legacy code.
>
> The worst thing that can happen with declare(strict_types=3D1), is that c=
ode
> won=E2=80=99t work any more.
>
> The worst thing that can happen with declare(strict_operators=3D1), is th=
at
> code will change semantics.
>
> =E2=80=94Claude
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
After discussing it with Nikita and Derick, I've decided to close the
voting for this RFC for now. The change is too large to merge it this
choose to a feature freeze.

Additionally, it seems that more discussion is required.

I will reopen the RFC at a later moment, targetting it at PHP 8.

Regards,
Arnold

--0000000000003a1b73058d3de235--