Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:105236
MIME-Version: 1.0
References: <CAFPFaMJEn=gjk5jAAxR2bF=4Mt3r0FJCm6mbOCReOmyybtAkkg@mail.gmail.com>
In-Reply-To: <CAFPFaMJEn=gjk5jAAxR2bF=4Mt3r0FJCm6mbOCReOmyybtAkkg@mail.gmail.com>
Date: Thu, 11 Apr 2019 11:14:06 +0100
Message-ID: <CAPg3XxL2GESpYiH+-NmhT28r_CTutA=Yh87Z9+JdAtLrszktWQ@mail.gmail.com>
To: "G. P. B." <george.banyard@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000006a1ec105863e747f"
Subject: Re: [PHP-DEV] [RFC] [VOTE] Deprecate PHP's short open tags
From: petercowburn@gmail.com (Peter Cowburn)

--0000000000006a1ec105863e747f
Content-Type: text/plain; charset="UTF-8"

On Wed, 10 Apr 2019 at 11:44, G. P. B. <george.banyard@gmail.com> wrote:

> Hello Internals,
>
> As there have been no further comments the voting for my RFC [1] to
> deprecate PHP's
> short open tags has started and will run for two (2) weeks.
>

Firstly, I apologize for not mentioning this before the vote was opened.

Does the primary (it's probably not fair to call it that, for this RFC)
vote include changing the default (php -n) from On to Off? That's what is
specified in the very concise proposal section, so it seems reasonable to
assume it's the case, but I just want to be sure since the actual vote
question doesn't mention changing the default value.

With the current state of voting, it is looking like we could end up such
that we don't deprecate (and disable by default, maybe) the feature, but
jump straight to removing it.  That's not usually how feature removal
works.  It would've been better, IMO, to just take the proposal
("Deprecate and disable short_open_tag in PHP 7.4 and remove PHP's short
open tags in PHP 8.0.") and make that a yes/no vote.

Best regards
>
> George P. Banyard
>
> [1] https://wiki.php.net/rfc/deprecate_php_short_tags
>

--0000000000006a1ec105863e747f--