Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106391
MIME-Version: 1.0
References: <CAFPFaML19B_RehrUQLEy_oFae-H5r3+BpUGg=GF1js83cJpJqQ@mail.gmail.com>
In-Reply-To: <CAFPFaML19B_RehrUQLEy_oFae-H5r3+BpUGg=GF1js83cJpJqQ@mail.gmail.com>
Date: Tue, 6 Aug 2019 12:59:13 -0400
Message-ID: <CAPKYkKxHkQojFnCs09htRFvTrV_SReQV7YVo6RxRSmuN9H_Q0w@mail.gmail.com>
To: "G. P. B." <george.banyard@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000026db2d058f75bff0"
Subject: Re: [PHP-DEV] [RFC] [VOTE] Deprecate PHP's short open tags, again
From: chasepeeler@gmail.com (Chase Peeler)

--00000000000026db2d058f75bff0
Content-Type: text/plain; charset="UTF-8"

I'm not a voter, but, I have a question. If this fails, does that mean the
original RFC that passed is still in effect?

If I did have a vote, I would be against this RFC for the reasons laid out
by Zeev in the counter argument. However, I feel the negative impacts of
possible code leaks that will be caused by the original RFC are even worse.
If I did have a vote, I might feel forced to vote for this. At least with
this RFC we wouldn't really see any of the other negative impacts until PHP
9, given us time to revisit and possibly reverse that part of this RFC.

On Tue, Aug 6, 2019 at 7:34 AM G. P. B. <george.banyard@gmail.com> wrote:

> The voting for the "Deprecate short open tags, again" [1] RFC has begun.
> It is expected to last two (2) weeks until 2019-08-20.
>
> A counter argument to this RFC is available at
> https://wiki.php.net/rfc/counterargument/deprecate_php_short_tags
>
> Best regards
>
> George P. Banyard
>
> [1] https://wiki.php.net/rfc/deprecate_php_short_tags_v2
>


-- 
Chase Peeler
chasepeeler@gmail.com

--00000000000026db2d058f75bff0--