Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:104683 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 15187 invoked from network); 12 Mar 2019 20:07:54 -0000 Received: from unknown (HELO mail.experimentalworks.net) (84.19.169.162) by pb1.pair.com with SMTP; 12 Mar 2019 20:07:54 -0000 Received: from kuechenschabe.fritz.box (ppp-188-174-121-6.dynamic.mnet-online.de [188.174.121.6]) by mail.experimentalworks.net (Postfix) with ESMTPSA id 65E6240E41; Tue, 12 Mar 2019 17:57:49 +0100 (CET) Message-ID: <1552409865.26232.12.camel@schlueters.de> To: Rowan Collins , PHP internals Date: Tue, 12 Mar 2019 17:57:45 +0100 In-Reply-To: References: 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 Di, 2019-03-12 at 15:53 +0000, Rowan Collins wrote: > On Tue, 12 Mar 2019 at 13:28, G. P. B. > wrote: > > > > > I was more going along the lines of removing short tags altogether > > with the > > ini setting as they are not available out of the box except if you > > use a > > special compile flag. > > > > I don't really follow this reasoning: if we removed every feature > which wasn't enabled out of the box, we wouldn't need an INI file at > all. Which would be good - as all those things make writing portable code harder.    $ echo '' | php Is a valid program, which will behave vastly different based on the ini setting. Of course for some things having a config is good (error levels arguably, extension loading, ...) but for the raw language syntax and behavior not so. johannes