Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104930
MIME-Version: 1.0
References: <CAFPFaMLC6beM1Tmud-fJQ-2inUhAPXo8WAY1mvEO26jdcNos7g@mail.gmail.com>
 <37adf4e9-58f5-bfd8-fac2-94523e192d00@gmail.com>
In-Reply-To: <37adf4e9-58f5-bfd8-fac2-94523e192d00@gmail.com>
Date: Mon, 25 Mar 2019 09:38:40 -0500
Message-ID: <CAESVnVpCFtR6Rt=rp_zw838+Du1in2k7=q4m_tfVmbSOry7_oA@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: "G. P. B." <george.banyard@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000c3a22e0584ec29b2"
Subject: Re: [PHP-DEV] Deprecate short_open_tag ini directive?
From: pollita@php.net (Sara Golemon)

--000000000000c3a22e0584ec29b2
Content-Type: text/plain; charset="UTF-8"

On Tue, Mar 12, 2019 at 11:57 AM Stanislav Malyshev <smalyshev@gmail.com>
wrote:
> > I'm currently going through the PHP doc to remove mentions of PHP 4
> > and stumbled upon the short_open_tag ini directive [1] which only
affects
> > the availability of `<?` tags as `<?=`is always available as of PHP 5.4.
> > From my understanding, the `<?` tag is not available without the
directive,
> > so maybe we should deprecate PHP's short tag altogether?
>
> Why? What would it improve for people that are using it? For people that
> aren't, it obviously won't change anything. So what would be the
> motivation for this change?
>
I'm with Stas (and some others in disconnected sub-threads because email is
hard).  This RFC needs a better "why this is important" section.  Yeah, I
get that it being an option makes writing portable code harder, I get that
the XML open tag is something that can be tripped on, but why is removing
it a sufficiently better solution to the "problem"?

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.

-Sara

--000000000000c3a22e0584ec29b2--