Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106069
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>
In-Reply-To: <F5FDFABD-2508-4D26-AE73-8829A068CA8F@cschneid.com>
Date: Wed, 26 Jun 2019 11:36:13 +0200
Message-ID: <CAG9XoMTb+g6g5gSFbvASeEcVj5N4crxgE1Exo120hJZLXRtwKQ@mail.gmail.com>
To: Christian Schneider <cschneid@cschneid.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000006f4ceb058c36c768"
Subject: Re: [PHP-DEV] [RFC] Strict operators directive
From: benjamin.morel@gmail.com (Benjamin Morel)

--0000000000006f4ceb058c36c768
Content-Type: text/plain; charset="UTF-8"

>  (...) could be the case depending on a declaration somewhere else in the
source code.
> That's the confusion Claude and I were talking about: You cannot be sure
what a very simple line of code does.

Oh, I see. You mean that only replacing some of the current results with
TypeErrors would be acceptable; returning a different value would not.
This makes a lot of sense, but once again prevents the language from slowly
moving towards something different (and better), leaving it stuck in its
legacy forever.

I'm starting to believe that a joint effort to fork PHP if the only way out
:(

Ben

--0000000000006f4ceb058c36c768--