Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106075
MIME-Version: 1.0
References: <c-17aa9-jxbttytv-fj6p6s=1xtnjis@2.gethop.com> <6D1026FF-ECF1-4604-91A8-D290D37CC238@cschneid.com>
 <F6D115B8-0808-4EA6-B031-4CE61F3C5704@gmail.com> <CAG9XoMTJKFFF2hrxgjBy3_A+8MA6mbEg1_1o957fY6bP29G4Cw@mail.gmail.com>
 <F5FDFABD-2508-4D26-AE73-8829A068CA8F@cschneid.com> <CAG9XoMTb+g6g5gSFbvASeEcVj5N4crxgE1Exo120hJZLXRtwKQ@mail.gmail.com>
 <E86347D1-E6BA-4B5E-AB00-DD3C17F05B25@gmail.com> <CAG9XoMRBBB34gHqvnYTpzUgLvW=+V649AadPEhbDgAbLw+_c1Q@mail.gmail.com>
 <CALKiJKoA8YN0O4B==6+cmRnkmvOsB8rZBn_HMxYjGdB7Nq4H3w@mail.gmail.com>
In-Reply-To: <CALKiJKoA8YN0O4B==6+cmRnkmvOsB8rZBn_HMxYjGdB7Nq4H3w@mail.gmail.com>
Date: Wed, 26 Jun 2019 14:15:51 +0200
Message-ID: <CAG9XoMTAgPuP=7JbiEPMRXLz33msi3wHmmCFrJ8QFSRrsP4GAQ@mail.gmail.com>
To: Rowan Collins <rowan.collins@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000551898058c3902bb"
Subject: Re: [PHP-DEV] [RFC] Strict operators directive
From: benjamin.morel@gmail.com (Benjamin Morel)

--000000000000551898058c3902bb
Content-Type: text/plain; charset="UTF-8"

>
> Given that we already have === and !==, could the strict mode simply throw
> an error for *any* use of the non-strict == and != versions?
> declare(strict_operators=1);
> var_dump(  "11" == "11.0" ); # TypeError: "Cannot use non-strict equality
> operator in strict operator mode."
> var_dump( "11" === "11.0"); # bool(false)
> I'm not sure whether I like the idea or not, but I thought I'd throw it out
> there as a possibility.


That's definitely a possibility, that I'm sure a lot of people will dislike.

I personally don't have a strong opinion about it.

Ben

--000000000000551898058c3902bb--