Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104667
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>
In-Reply-To: <CAAfnsFWv1Ac=-AUBs2K7a2zyVogeE5a=5r5uV=8KndW1G_satQ@mail.gmail.com>
Date: Tue, 12 Mar 2019 10:39:31 +0000
Message-ID: <CALKiJKqGk9sTuAgTurwy7BH6zUG6WQgPE_cvTNiJSMW5+BhjEA@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000009637430583e34e66"
Subject: Re: [PHP-DEV] Deprecate short_open_tag ini directive?
From: rowan.collins@gmail.com (Rowan Collins)

--0000000000009637430583e34e66
Content-Type: text/plain; charset="UTF-8"

On Tue, 12 Mar 2019 at 10:12, Peter Kokot <peterkokot@gmail.com> wrote:

>
> PHP based template engines today most likely use only <?php and <?=
> because of this topic today exactly. Possibility of being deprecated
> :) I think the short opening tags are good to go so things are more
> simple.
>


A quick search of the list archives showed the opposite: reassurances that
short open tags are *not* deprecated, and vocal support for keeping them.



> A side question is there any plan to move the idea of removing opening
> <?php tag for PHP only files or is this off topic here? PHP has long
> moved out of the template engines world and left that task to more
> dedicated so called compiled or parsed template engines (such as Twig
> or Blade), so maybe something to think about as well.
>


I think that's a different discussion - and also one that's happened a few
times in the past. I think the general conclusion was that the gain isn't
big enough to bother changing every tool that works with PHP.

Regards,
-- 
Rowan Collins
[IMSoP]

--0000000000009637430583e34e66--