Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:104935 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 41504 invoked from network); 25 Mar 2019 18:23:21 -0000 Received: from unknown (HELO mail.experimentalworks.net) (84.19.169.162) by pb1.pair.com with SMTP; 25 Mar 2019 18:23:21 -0000 Received: from kuechenschabe.fritz.box (ppp-188-174-51-14.dynamic.mnet-online.de [188.174.51.14]) by mail.experimentalworks.net (Postfix) with ESMTPSA id 2E8B445E2B; Mon, 25 Mar 2019 16:16:30 +0100 (CET) Message-ID: <1553526929.28717.6.camel@schlueters.de> To: Sara Golemon , Stanislav Malyshev Cc: "G. P. B." , PHP internals Date: Mon, 25 Mar 2019 16:15:29 +0100 In-Reply-To: References: <37adf4e9-58f5-bfd8-fac2-94523e192d00@gmail.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.18.5.2-0ubuntu3.2 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] Deprecate short_open_tag ini directive? From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=) On Mo, 2019-03-25 at 09:38 -0500, Sara Golemon wrote: > > As we stand now, code using short open tags works when those tags are > enabled.  As we'd stand in the future, that code would not work.  > That > level of BC break requires a strong justification. The code would not simply "not work" but even potentially leak to the client (as PHP would not treat it as code) which could leak credentials or other sensitive information. I still think that long-term goal should be that language behavior doesn't depend on ini configuration.  Also creating a tool which does the conversion is relatively simple. johannes