Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:105387
MIME-Version: 1.0
References: <CAFPFaMJEn=gjk5jAAxR2bF=4Mt3r0FJCm6mbOCReOmyybtAkkg@mail.gmail.com>
 <CAOv67gsiva80KEhw7D2N2qKCz0gZvza30EDL7SZoJRPFsGoROA@mail.gmail.com>
 <0ec42fa9-77d1-a203-8425-e72fdd5071f3@korulczyk.pl> <06473788-a34b-f041-36e6-31d19d8dda4c@cubiclesoft.com>
 <59cafbfb-2bb0-468c-458f-74bcac780e0f@korulczyk.pl> <004c01d4f09f$880ac320$98204960$@roze.lv>
 <CAFPFaM+QwXpm-mfwRtbT2sPB_C-9wvPELVTV5dHvizgmfUjMnw@mail.gmail.com>
 <004401d4faa3$60f83700$22e8a500$@gmail.com> <2f922f17-bc7c-313a-8f77-122e861995be@lsces.co.uk>
 <CAPKYkKyS4A_zQO3OEqqv+LOrG5cPLjGqUEXonsQeA_jcE=69Gg@mail.gmail.com> <5cc08999.1c69fb81.9fdc4.30ccSMTPIN_ADDED_MISSING@mx.google.com>
In-Reply-To: <5cc08999.1c69fb81.9fdc4.30ccSMTPIN_ADDED_MISSING@mx.google.com>
Date: Wed, 24 Apr 2019 12:14:18 -0400
Message-ID: <CAPKYkKzYBfnfY6PKtvk5rfL9GBChCoq0MXOpt4tr9rtDcDUqVQ@mail.gmail.com>
To: Mark Randall <markyr@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000117fc5058748ffd1"
Subject: Re: [PHP-DEV] [RFC] [VOTE] Deprecate PHP's short open tags
From: chasepeeler@gmail.com (Chase Peeler)

--000000000000117fc5058748ffd1
Content-Type: text/plain; charset="UTF-8"

On Wed, Apr 24, 2019 at 12:06 PM Mark Randall <markyr@gmail.com> wrote:

> On 24/04/2019 15:35, Chase Peeler wrote:
> >> Total files scanned:  20,767
> > Total lines scanned:  4,013,170
> > Total short open tag references:  6,787
> > Total files w/ short open tag references:  1,665
>
> 1. Open project in PHPStorm (or equivalent).
>
> 2. Run inspections.
>
> 3. Click convert short open tags.
>
> As I've mentioned in other posts, I don't trust this to do a blind
find/replace. Some of our legacy code files are REALLY bad. Just doing auto
formatting on them in PhpStorm will break things.


> Personally I prefer the shorter look of "<? if(...) { ?>" when writing
> templates, but not enough to be up in arms about its removal.
>
> I personally don't like using short tags. I haven't used them since there
was a rumor they would be removed in PHP 6. My objections have nothing to
do with me personally wanting to keep using short tags.


> If anything I'm more concerned about potential code + data leaks.
>
> One of my major concerns as well. I find it ironic that one of the
justifications for the RFC was the potential for code leaks if code with
short open tags is used in an environment where short open tags are
disabled. The solution to that was to guarantee that code with short open
tags will leak code.


> Something which was previously perfectly legitimate code, no longer
> being considered code, could be quite the problematic situation...
> especially if that code happened to be protective logic such as "if"
> statements.
>
> Exactly my point. Much of our legacy code is left alone as much as
possible. We go in there when absolutely necessary due to functional
changes in our applications. This change forces us to go in there for
changes that don't relate to application functions and don't provide any
meaningful enhancement to the language itself, either.


> <? if ($admin) { ?>
>    User secret: <?= htmlspecialchars($secret) ?>
> <? } ?>
>
> I would have preferred that the parser encountering <? threw a compile
> error for quite some time rather than just magically ceasing to be
> relevant.
>
> I agree. I think showing a blank page would be better than leaking code.


> The XML argument holds no weight with me.
>
> Me either. I definitely don't think it is serious enough to justify the BC
break given that it can be easily worked around.


> --
> Mark Randall
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

-- 
Chase Peeler
chasepeeler@gmail.com

--000000000000117fc5058748ffd1--