Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106380
MIME-Version: 1.0
References: <CAFPFaMLpZ=okschrpeH77AhZTHcvFBuPf1S1bXH6psxmvABK7g@mail.gmail.com>
 <CAJHtznwZ_oPA5vWds6mCYAUSiyCrvLrUWSAUj7pV9DeU2Zzp1w@mail.gmail.com>
In-Reply-To: <CAJHtznwZ_oPA5vWds6mCYAUSiyCrvLrUWSAUj7pV9DeU2Zzp1w@mail.gmail.com>
Date: Mon, 5 Aug 2019 21:05:04 +0200
Message-ID: <CAFPFaM+OT67UiD8uo08iXc-LZRUgs1wFF+ZaW7XdycT-OMagTQ@mail.gmail.com>
To: Zeev Suraski <zeev@php.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000739c0f058f6363d5"
Subject: Re: [PHP-DEV] [RFC] [DISCUSSION] Deprecate PHP's short open tags V2
From: george.banyard@gmail.com ("G. P. B.")

--000000000000739c0f058f6363d5
Content-Type: text/plain; charset="UTF-8"

On Mon, 5 Aug 2019, 20:47 Zeev Suraski, <zeev@php.net> wrote:

> As we head closer to the vote - and in light of what I said towards the end
> of my message in https://externals.io/message/106256#106278, as well as
> the
> points Dan articulated regarding the current issue of negative feedback not
> getting the same level of visibility as the RFC itself - I'd like to figure
> out a temp solution until we amend our rules.
>
> George - are you OK with having a section that illustrates the issues that
> me and some others have brought up with this deprecation in the RFC
> itself?  Or add a link to a separate page, along the lines of what Dan
> proposed?
>
> Thanks,
>
> Zeev
>

I'd prefer Dan's approach and having a seperate page linked at the top of
the RFC.

I'll start voting tomorrow and will link to your page in the same message
as the voting announcement.

Best regards

George P. Banyard

>

--000000000000739c0f058f6363d5--