Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112236
Date: Thu, 12 Nov 2020 10:16:11 +0000
User-Agent: K-9 Mail for Android
In-Reply-To: <5facd78e.1c69fb81.81f92.be93SMTPIN_ADDED_MISSING@mx.google.com>
References: <CAEsg9X3UF9i8r2PS_f___RU_PsXuJhLg1NOm1JUAtP8B_Uzasg@mail.gmail.com> <5facd78e.1c69fb81.81f92.be93SMTPIN_ADDED_MISSING@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
To: internals@lists.php.net
Message-ID: <A192352A-6907-4CB9-898B-3F9AD3F84ADE@gmail.com>
Subject: Re: [PHP-DEV] Re: strict_types will be default at some moment?
From: rowan.collins@gmail.com (Rowan Tommins)

On 12 November 2020 06:34:48 GMT+00:00, Mark Randall <marandall@php=2Enet> =
wrote:
>If that ever goes back into discussion, I think that I and many others=20
>would argue that strict_types=3D1 would be a baseline requirement of the=
=20
>first edition=2E


As I tried to explain in my message last night and elsewhere, the directiv=
e as originally designed would not be a good fit for "editions", which impl=
ies progression in some definite direction; it would need something more li=
ke "flavours" of the language, equally valid but supporting different style=
s=2E=20

Adding it to "editions" would just be a means to the end of removing the o=
ption, but it's not clear that the case for doing that is any stronger than=
 it was 5 years ago=2E

Regards,

--=20
Rowan Tommins
[IMSoP]