Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:105252
Return-Path: <r@roze.lv>
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 7862 invoked from network); 11 Apr 2019 22:51:00 -0000
Received: from unknown (HELO zeona.lv) (213.175.74.1)
  by pb1.pair.com with SMTP; 11 Apr 2019 22:51:00 -0000
Received: from MezhRoze (unknown [10.8.0.69])
	by zeona.lv (Postfix) with ESMTP id 37D98200F47D7
	for <internals@lists.php.net>; Thu, 11 Apr 2019 22:48:27 +0300 (EEST)
To: "'PHP internals'" <internals@lists.php.net>
References: <CAFPFaMJEn=gjk5jAAxR2bF=4Mt3r0FJCm6mbOCReOmyybtAkkg@mail.gmail.com> <CAOv67gsiva80KEhw7D2N2qKCz0gZvza30EDL7SZoJRPFsGoROA@mail.gmail.com> <0ec42fa9-77d1-a203-8425-e72fdd5071f3@korulczyk.pl> <06473788-a34b-f041-36e6-31d19d8dda4c@cubiclesoft.com> <59cafbfb-2bb0-468c-458f-74bcac780e0f@korulczyk.pl>
In-Reply-To: <59cafbfb-2bb0-468c-458f-74bcac780e0f@korulczyk.pl>
Date: Thu, 11 Apr 2019 22:48:27 +0300
Message-ID: <004c01d4f09f$880ac320$98204960$@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: AQKWYMbL3wXLTWQ3PVae8RfPqaXsqgJlPMGNAWrs/XwBfwzR+AIrnLXmpHiZZsA=
Subject: RE: [PHP-DEV] [RFC] [VOTE] Deprecate PHP's short open tags
From: r@roze.lv ("Reinis Rozitis")

> From: Robert Korulczyk [mailto:robert@korulczyk.pl]
>
> Personally, I'm surprised by the controversy around this change. So =
far it was an
> obvious anti-pattern for me, and never seen anybody who was aware of =
the
> consequences of using <? and still use <? instead <?php on purpose.

It's not really a problem for programmers/coders writing new code rather =
for server providers/administrators (maybe also a reason why such issues =
are not (or rarely) voiced in a language development internal list) =
hosting legacy applications where no one wants or there is nobody to fix =
anything (even more with an automatic third party tool) and then there =
won't even be a switch (ini option) anymore for backwards compability.=20
So you are (will be) forced to stay on EOL php version or implement a =
patch for reverting particular thing in your distro/custom package.


p.s. somewhat similar is the situation with 'mysql' extension which by =
default prints a lot of deprecated warnings even being in pecl and =
basically the same wrapper around mysqlnd as mysqli/pdo, but at least =
there is still an option if your code really requires mysql_*=20
(and many thanks to the people like Dmitry, Matteo who still make it =
compatible with the actual php versions).

rr