Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106670
To: Internals <internals@lists.php.net>
References: <CAFPFaML19B_RehrUQLEy_oFae-H5r3+BpUGg=GF1js83cJpJqQ@mail.gmail.com>
 <CAJHtznzie34C92y2nTRXxhD99FEW-5hmruVatsrLDHcAKvTccQ@mail.gmail.com>
 <CAEYWF=7S2SxzxU+TzRV0Rc7FNMvyZBkAENVTNbZKqrs71Uyijw@mail.gmail.com>
 <000001d54e5a$02ac09f0$08041dd0$@roze.lv>
 <2b5588d6-d667-321f-22f1-46a22bb797c5@korulczyk.pl>
 <000001d54ea3$eb3480a0$c19d81e0$@roze.lv>
 <ad6b9615-372d-69ba-9ca5-e8fa554c5aea@korulczyk.pl>
 <000301d54ead$b43e7b00$1cbb7100$@roze.lv>
 <59378662-77ca-0779-10cb-c25acf1b45ef@korulczyk.pl>
 <CAKOpQSySEqE4VR+b0Twp4NxZMa+ruEYTbV7qr38Tcw8wqobH2A@mail.gmail.com>
 <CAFPFaMKBWEo-MXCP75vFt2JEvNXzLVhW=f2gGaGHSazb1oXK8Q@mail.gmail.com>
 <CAAfnsFUQ1mKGdqkekCxU7+C6Rr48WBAajoD-ut4bk8UD=GU4Zw@mail.gmail.com>
 <CAPKYkKzpEN8Q-2_CfnJkTNJTmDCDLX2h7UfRfetP+2JJaeuOWA@mail.gmail.com>
 <CAAfnsFUv13iAMVZ-MqNP25NBmvADMKon7KWhTCBpPY-BG2VwFQ@mail.gmail.com>
 <0c52dfe9-0192-c643-12b8-8038ccf98910@gmail.com>
 <CAAfnsFUqmmJFv8X1MDSKL8kCjHvcH8KA8JsTgy53jKhodOVMPw@mail.gmail.com>
Message-ID: <b70e94f6-5cbb-56e5-f97e-cb29941962b8@gmail.com>
Date: Tue, 20 Aug 2019 18:39:20 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <CAAfnsFUqmmJFv8X1MDSKL8kCjHvcH8KA8JsTgy53jKhodOVMPw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
Subject: Re: [PHP-DEV] [RFC] [VOTE] Deprecate PHP's short open tags, again
From: rowan.collins@gmail.com (Rowan Tommins)

On 20/08/2019 17:56, Peter Kokot wrote:
> Probably. But fact is that PHP opening short tags can be used. We can
> enable them in controlled environments and use the short tags knowing
> they will never be removed now. No deprecation warning is standing in
> our way to do that now. And such code (or better put app) is honestly
> now also not so bad. Because it will still work in at least let's say,
> PHP 9 at least or considering the feedback and discussions for ever...
> Also users who are already using short tags can now postpone the
> upgrades for another ~5+ years at least :)


I don't think anything has changed in that regard. If there's text in 
the manual that short open tags are deprecated then it was wrong before 
this pair of RFCs; if there's text in the manual stating other reasons 
not to use them (portability, possibility of mixing in XML, etc) then it 
is still just as valid as it ever was.

If your impression was that the feature was already deprecated before 
the v1 RFC, and has somehow become *less* deprecated as a result of this 
vote, that may be explain some of the disconnect over the issue. As far 
as I'm aware, it had no such status, it was simply a feature that used 
to be more commonly used than it is today.

Regards,

-- 
Rowan Tommins (né Collins)
[IMSoP]