Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106259
Message-ID: <63FBCF41-8F7B-491D-B593-3F767433E2BA@gmail.com>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_5354CA42-3AE2-40B3-B1FC-E2107BA13D44"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Tue, 23 Jul 2019 22:24:32 +0200
In-Reply-To: <CAFPFaMLpZ=okschrpeH77AhZTHcvFBuPf1S1bXH6psxmvABK7g@mail.gmail.com>
Cc: PHP internals <internals@lists.php.net>,
 Derick Rethans <derick@php.net>,
 Peter Kokot <petk@php.net>
To: "G. P. B." <george.banyard@gmail.com>
References: <CAFPFaMLpZ=okschrpeH77AhZTHcvFBuPf1S1bXH6psxmvABK7g@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] [DISCUSSION] Deprecate PHP's short open tags V2
From: claude.pache@gmail.com (Claude Pache)

--Apple-Mail=_5354CA42-3AE2-40B3-B1FC-E2107BA13D44
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> Le 23 juil. 2019 =C3=A0 19:54, G. P. B. <george.banyard@gmail.com> a =
=C3=A9crit :
>=20
> The only point of contention of this RFC that I potentially see is the
> removal in PHP 8.1 after short open tags being a Parse Error in PHP =
8.0
> instead of it being removed in PHP 9 after it having had a whole major
> version release cycle.

Realistically, a non-negligible proportion of users will jump from PHP =
7.x to 8.1 or 8.2; so that having the parse error behaviour in 8.0 only =
is in no way safer for them. It is more reasonable to keep the parse =
error behaviour for all 8.x versions.

=E2=80=94Claude=

--Apple-Mail=_5354CA42-3AE2-40B3-B1FC-E2107BA13D44--