Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106065
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
In-Reply-To: <6D1026FF-ECF1-4604-91A8-D290D37CC238@cschneid.com>
Date: Wed, 26 Jun 2019 09:56:39 +0200
Cc: Arnold Daniels <arnold.adaniels.nl@gmail.com>,
 internals@lists.php.net
Content-Transfer-Encoding: quoted-printable
Message-ID: <F6D115B8-0808-4EA6-B031-4CE61F3C5704@gmail.com>
References: <c-17aa9-jxbttytv-fj6p6s=1xtnjis@2.gethop.com>
 <6D1026FF-ECF1-4604-91A8-D290D37CC238@cschneid.com>
To: Christian Schneider <cschneid@cschneid.com>
Subject: Re: [PHP-DEV] [RFC] Strict operators directive
From: claude.pache@gmail.com (Claude Pache)



> Le 26 juin 2019 =C3=A0 08:50, Christian Schneider =
<cschneid@cschneid.com> a =C3=A9crit :
>=20
> Am 25.06.2019 um 15:09 schrieb Arnold Daniels =
<arnold.adaniels.nl@gmail.com>:
>> This RFC proposes a new directive 'strict_operators'. When enabled, =
operators may cast operands to the expected type, but must comply to;
>>=20
>> * Typecasting is not based on the type of the other operand
>>=20
>> * Typecasting is not based on the value of any of the operands
>> * Operators will throw a TypeError for unsupported types
>=20
> While I understand that some people don't like the way PHP does type =
conversions I think this proposal creates a much bigger element of =
surprise when copying PHP code from one place to another than all the =
.ini-settings ever did.
>=20
> It basically creates two languages in one and I won't be able to =
determine what
> 	$a =3D=3D 42
> exactly does without having to look at the header of the file.
>=20
> I'm inclined to say that if you want to make PHP a new language with a =
new core type concept then you should fork it and call it something else =
to avoid confusion.
>=20
> - Chris
>=20


Indeed. The directive may make operators more strict in what they =
accept, but it should avoid changing the semantics. Concretely, we must =
have either:

    "120" > "99.9"; // true

or:

    "120" > "99.9"; // TypeError

Anything else will bring confusion.

=E2=80=94Claude