Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:106421 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 68396 invoked from network); 7 Aug 2019 21:38:01 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 7 Aug 2019 21:38:01 -0000 To: internals@lists.php.net References: Date: Wed, 7 Aug 2019 20:05:01 +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: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Posted-By: 94.4.34.143 Subject: Re: [PHP-DEV] [RFC] [VOTE] Deprecate PHP's short open tags, again From: markyr@gmail.com (Mark Randall) Message-ID: On 07/08/2019 18:44, Peter Kokot wrote: > I think the worst > situation for language is that there is an option to write non > portable code with this unfortunate short tag. It won't work > everywhere. So, this is already a reason for thinking forward (at > least from the progress and consistency point of view) I feel it necessary to point out that non-portability due to INI settings applies to almost everything PHP does, and in and of itself should not be considered a major argument. PHP is, after all, built almost entirely on extensions. Those extensions can either be there, or not, enabled in the INI, or not. Do we consider code written containing functions from mysqli, gd or zip (just to name a few) to be non-portable because we can omit them from the INI (or just not install them). There are arguments for and against removal. IMO non-portability is not one of them. IMHO short tag removal has one major thing going for it, consistency, and by extension, predictability. That's it. Is that enough? I'm on the fence. Mark Randall