Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110850
MIME-Version: 1.0
References: <c-17aa9-kcanr61p-tnd07y=1e5p5oh@2.gethop.com>
In-Reply-To: <c-17aa9-kcanr61p-tnd07y=1e5p5oh@2.gethop.com>
Date: Mon, 6 Jul 2020 18:33:33 +0200
Message-ID: <CAEPJduk5tZ+aViYM4BiEUSTcL3m3_=0Fs1Nc8R2LOAx3D0uh6A@mail.gmail.com>
To: Arnold Daniels <arnold.adaniels.nl@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000345ee205a9c870e2"
Subject: Re: [PHP-DEV] [RFC][DISCUSSION] Strict operators directive
From: kontakt@beberlei.de (Benjamin Eberlei)

--000000000000345ee205a9c870e2
Content-Type: text/plain; charset="UTF-8"

On Mon, Jul 6, 2020 at 5:27 PM Arnold Daniels <arnold.adaniels.nl@gmail.com>
wrote:

> Hi all,
>
> I'd like to start the discussion of the "Strict operators directive" RFC
> version 1.5. This RFC proposes a new directive strict_operators, which
> limits the type juggling done by operators to avoid unexpected results.
>
> https://wiki.php.net/rfc/strict_operators
>
> There are some significant changes from the previous version.
> strict_operators no longer has cases where it changes the outcome of an
> operation. To achieve this the following changes are made to the RFC
>
> * All comparison operators, besides `===` and `!==`, only accept `int` and
> `float` operands. For any other type a `TypeError` is thrown. This includes
> `==` and `!=`.
>

what about DateTime and other objects overwriting comparison operators?
(GMP, ...) How would this proposal affect future proposals that expose
comparisons to userland (see for example the operator overloading RFC).

* The `switch` statement is not affected.
>

> For frequently asked questions please see
> https://wiki.php.net/rfc/strict_operators/faq.
>

Honestly PHP comparisons are already complex enough, introducing a second
set of rules that are just as complex seems like a risky proposal to me.

>
> [Arnold Daniels - Chat @ Spike](
> https://spikenow.com/r/a/?ref=spike-organic-signature&_ts=l1bam)
> [l1bam]

--000000000000345ee205a9c870e2--