Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110286
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
In-Reply-To: <CAGgaK7L_CyUDzV_0dpOXQ0FCDWDnCTK3zQwhk=+iC2XDipoHiQ@mail.gmail.com>
Date: Wed, 27 May 2020 11:59:27 +0200
Cc: Internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <C4981530-FF04-41E4-8A0C-783A5B78ACFB@cschneid.com>
References: <CANZOY=AHs40Dzo_G44Q9byDbJ7emu5yDpmBMTSQ2uCXSARG_Dw@mail.gmail.com>
 <5ebff6c5.1c69fb81.1cf6b.cea7SMTPIN_ADDED_MISSING@mx.google.com>
 <CAGgaK7L_CyUDzV_0dpOXQ0FCDWDnCTK3zQwhk=+iC2XDipoHiQ@mail.gmail.com>
To: Max Semenik <maxsem.wiki@gmail.com>
Subject: Re: [PHP-DEV] [RFC] Strict operators directive
From: cschneid@cschneid.com (Christian Schneider)

Am 16.05.2020 um 16:56 schrieb Max Semenik <maxsem.wiki@gmail.com>:
> On Sat, May 16, 2020 at 5:20 PM Mark Randall <marandall@php.net> =
wrote:
>=20
>> IMHO we need to know what is happening with editions, as I think this
>> would be an ideal candidate for that rather than another declare
>=20
>=20
> On the other hand, a declare would allow a gradual upgrade path where
> people can use strict mode for new code and convert file after file at
> their own pace, taking their time to fix all the problems - while =
already
> taking advantage of new features where possible.


The problem originally discussed (and among other things leading to the =
P++ proposal) remains:
We would have two semantically very different languages in one with just =
a little line at the top of the file to distinguish between them.

I cannot look at code like
	function same($a, $b)
	{
		return $a =3D=3D $b;
	}
and know how if it works with my usage of types.

In a way having this on a per-file-basis makes things even worse.

- Chris