Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106260
Return-Path: <r@roze.lv>
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 7835 invoked from network); 23 Jul 2019 23:17:40 -0000
Received: from unknown (HELO zeona.lv) (213.175.74.1)
  by pb1.pair.com with SMTP; 23 Jul 2019 23:17:40 -0000
Received: from MezhRoze (unknown [10.8.0.69])
	by zeona.lv (Postfix) with ESMTP id 478112009DAB7
	for <internals@lists.php.net>; Tue, 23 Jul 2019 23:40:53 +0300 (EEST)
To: "'PHP internals'" <internals@lists.php.net>
References: <CAFPFaMLpZ=okschrpeH77AhZTHcvFBuPf1S1bXH6psxmvABK7g@mail.gmail.com>
In-Reply-To: <CAFPFaMLpZ=okschrpeH77AhZTHcvFBuPf1S1bXH6psxmvABK7g@mail.gmail.com>
Date: Tue, 23 Jul 2019 23:40:53 +0300
Message-ID: <000301d54196$ec050730$c40f1590$@roze.lv>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 15.0
Content-Language: lv
Thread-Index: AQDvdyqZOGEcm0cGOt6xidNxRz1kCqikNo/Q
Subject: RE: [PHP-DEV] [RFC] [DISCUSSION] Deprecate PHP's short open tags V2
From: r@roze.lv ("Reinis Rozitis")

> First, short_open_tag is an ini setting that control core language =
syntax. This means that their use is not possible in portable code, =
because the code author does not necessarily have the necessary control =
over the configuration of the deployment environment.


While this RFC  is a much better way of deprecating the feature (looking =
at the previous votes it most likely will happen), the reasoning/text =
(main point) is still odd:

- if the code author wants a portable code he HAS the necessary control =
over it and can always follow the coding guidelines and write it using =
'<?php'

- contrary the control/option is taken away from the server =
administrator (the deployment environment provider) that if there is a =
project/code that uses short tags there is no way to support that =
anymore besides altering the code (for what he might not have the =
necessary control).

rr