Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:106485 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 12101 invoked from network); 9 Aug 2019 14:59:19 -0000 Received: from unknown (HELO zeona.lv) (213.175.74.1) by pb1.pair.com with SMTP; 9 Aug 2019 14:59:19 -0000 Received: from MezhRoze (unknown [10.8.0.69]) by zeona.lv (Postfix) with ESMTP id AC79B2009DAB7; Fri, 9 Aug 2019 15:26:42 +0300 (EEST) To: "'Robert Korulczyk'" , References: <000001d54e5a$02ac09f0$08041dd0$@roze.lv> <2b5588d6-d667-321f-22f1-46a22bb797c5@korulczyk.pl> <000001d54ea3$eb3480a0$c19d81e0$@roze.lv> In-Reply-To: Date: Fri, 9 Aug 2019 15:26:43 +0300 Message-ID: <000301d54ead$b43e7b00$1cbb7100$@roze.lv> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQHjzwR+XvJt6M7mF5GjTobLDXnEoQIpyUV8Alb9DGYB+yJwYQEzzSE9Ajo4a1YBXPZcgAHiiC/CpmxiO2A= Content-Language: lv Subject: RE: [PHP-DEV] [RFC] [VOTE] Deprecate PHP's short open tags, again From: r@roze.lv ("Reinis Rozitis") > This does not explain how someone could use that feature *by = accident*. I gave > an example where you can use short open tags by accident, and it is = really easy > (the most popular IDE sometimes generates code with short open tags) = and hard > to notice (it is not easy to spot a difference between ` you compare this to situation when you create a separate file with an = explicit > directive to disable PHP engine, and then be surprised that code is = not executed? Disabling short tags now is done with "an explicit directive" (there has = to be a specific ini file with a specific setting 'short_open_tag =3D = 0').=20 Isn't this the same "situation when you create a separate file with an = explicit directive"? If a coder (or IDE) has written '