Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106272
Return-Path: <markyr@gmail.com>
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 68770 invoked from network); 24 Jul 2019 03:05:39 -0000
Received: from unknown (HELO localhost.localdomain) (76.75.200.58)
  by pb1.pair.com with SMTP; 24 Jul 2019 03:05:39 -0000
To: internals@lists.php.net
References: <CAFPFaMLpZ=okschrpeH77AhZTHcvFBuPf1S1bXH6psxmvABK7g@mail.gmail.com>
Date: Wed, 24 Jul 2019 01:28:53 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.7.2
MIME-Version: 1.0
In-Reply-To: <CAFPFaMLpZ=okschrpeH77AhZTHcvFBuPf1S1bXH6psxmvABK7g@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
X-Posted-By: 5.69.56.51
Subject: Re: [RFC] [DISCUSSION] Deprecate PHP's short open tags V2
From: markyr@gmail.com (Mark Randall)
Message-ID: <php.internals-106272@news.php.net>

I continue to find motivations #1 and #3 utterly bizarre, especially 
that "open tags not being compatible with XML" is still being used as a 
justification.

That said, the depreciation and removal process looks solid, with the 
exception of complete removal in PHP 8.1.

I must question if people are really so desperate to use <? in plain 
text (for XML?) that it needs to be removed with such haste, especially 
as its continued existence at that point would be strictly as a security 
feature.

If I may make one suggestion, I see the depreciation message is quite 
plain. One would not be stretching the bounds of reasonableness too far 
to suggest the creation of a dedicated page on php.net that contains a 
description, a link to csfixer etc, and then that link be included in 
the depreciation message itself.

--
Mark Randall


On 23/07/2019 18:54, G. P. B. wrote:
> Hello internals,
> https://wiki.php.net/rfc/deprecate_php_short_tags_v2