Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106400
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
In-Reply-To: <CAF+90c__-duwVG7tOKDmrKAnV3B+7rKWcxh1kGZ+aUgU9MNSxQ@mail.gmail.com>
Date: Tue, 6 Aug 2019 23:55:13 +0200
Cc: "G. P. B." <george.banyard@gmail.com>,
 PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <31F25B65-D8D0-4F33-97A9-C978CBA8A7D6@gmail.com>
References: <CAFPFaML19B_RehrUQLEy_oFae-H5r3+BpUGg=GF1js83cJpJqQ@mail.gmail.com>
 <CAF+90c__-duwVG7tOKDmrKAnV3B+7rKWcxh1kGZ+aUgU9MNSxQ@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Subject: Re: [PHP-DEV] [RFC] [VOTE] Deprecate PHP's short open tags, again
From: claude.pache@gmail.com (Claude Pache)



> Le 6 ao=C3=BBt 2019 =C3=A0 20:46, Nikita Popov <nikita.ppv@gmail.com> =
a =C3=A9crit :
>=20
> On Tue, Aug 6, 2019 at 1:34 PM G. P. B. <george.banyard@gmail.com> =
wrote:
>=20
>> The voting for the "Deprecate short open tags, again" [1] RFC has =
begun.
>> It is expected to last two (2) weeks until 2019-08-20.
>>=20
>> A counter argument to this RFC is available at
>> https://wiki.php.net/rfc/counterargument/deprecate_php_short_tags
>>=20
>> Best regards
>>=20
>> George P. Banyard
>>=20
>> [1] https://wiki.php.net/rfc/deprecate_php_short_tags_v2
>>=20
>=20
> Side-note: Even if this RFC fails, we should probably still make it an
> error to use <? without short_tags being **explicitly** enabled, so =
that we
> may flip the default to off at some later point in time. The current
> default being "on" despite their use being discouraged is half the =
trouble.
>=20
> Nikita


That would mean in particular that XML documents could no longer be =
preprocessed by PHP without boilerplate around its `<?xml ?>` =
declaration. I doubt that this is a more acceptable breaking change than =
deprecating short_tags.

=E2=80=94Claude=