Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104752
MIME-Version: 1.0
References: <CAFPFaMLC6beM1Tmud-fJQ-2inUhAPXo8WAY1mvEO26jdcNos7g@mail.gmail.com>
 <CALKiJKqNqMJVTmhmgjcBUSkJNG9_F-kuvLicQ7Ghs2FvJM1GiA@mail.gmail.com>
 <CAAfnsFWv1Ac=-AUBs2K7a2zyVogeE5a=5r5uV=8KndW1G_satQ@mail.gmail.com>
 <CALKiJKqGk9sTuAgTurwy7BH6zUG6WQgPE_cvTNiJSMW5+BhjEA@mail.gmail.com>
 <CAAwdEzBSkw8sNbm_mka9EDVKhvXQNqMtxaMPh5e9UUj72OC5eA@mail.gmail.com>
 <CALKiJKrpWo41W31xb3_bjVG0MMUM8Z0sgGGeD0yccxyMfu5Kog@mail.gmail.com>
 <1552409865.26232.12.camel@schlueters.de> <CAAfnsFXMVh38kUKK6wRD=mYxZ3nZNN1mVtz_i_DXESxRg-z3Ww@mail.gmail.com>
 <1552436054.16816.11.camel@schlueters.de>
In-Reply-To: <1552436054.16816.11.camel@schlueters.de>
Date: Fri, 15 Mar 2019 16:56:05 +0100
Message-ID: <CAFPFaML+SdZ8hAfuZU=QfO2dFv8=P9Oh_M9Lwq2P4JsZfDQY-g@mail.gmail.com>
To: =?UTF-8?Q?Johannes_Schl=C3=BCter?= <johannes@schlueters.de>
Cc: Peter Kokot <peterkokot@gmail.com>, Rowan Collins <rowan.collins@gmail.com>, 
	PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000007ea9e3058424148b"
Subject: Re: [PHP-DEV] Deprecate short_open_tag ini directive?
From: george.banyard@gmail.com ("G. P. B.")

--0000000000007ea9e3058424148b
Content-Type: text/plain; charset="UTF-8"

Just gonna do general reply instead of pointing at specific points.

But as it has been pointed out using short tags makes the code less
portable,
which IMO isn't ideal.

I personally don't tinker with INI settings withing PHP with `ini_set` as
IMHO if you
need to change them it should be done in the php.ini file.
However, I'm not sure of the behavior if someone sets this behavior within
a file/class
does this only affect this specific instance or is it globally?
Because if it is globally I can see code that writes/uses XML be affected
as pointed
out by Johannes

As it seems that there are people for and against; I suppose I could write
an RFC
for this, but would need the karma to do so.

Best regards

George P. Banyard

--0000000000007ea9e3058424148b--