Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101851
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAOv67gumf_dGzTCyyNu6zFy_N+i_pG3VjM3BkWfCw+FdhpY3Bg@mail.gmail.com>
References: <CAOv67guxH2CN5oAOj=+v_U94D_J42Q2MZJzWgVAmwe519-AOPA@mail.gmail.com>
 <CAPhkiZzpKPeJKnR7f+JMQ-8zS87_2g7WWcyhgwwoJNKHz6uf_w@mail.gmail.com>
 <CAOv67gveFaUEr-78-3+bp3KFFoVKnS0bHjTJD_g0tYKWrDBLgA@mail.gmail.com>
 <e3cff023-3c92-e479-257c-199b68b3e133@gmail.com> <CAOv67gumf_dGzTCyyNu6zFy_N+i_pG3VjM3BkWfCw+FdhpY3Bg@mail.gmail.com>
Date: Mon, 12 Feb 2018 14:36:16 -0600
Message-ID: <CAEUnE0enXSao=YDi4zNLc8S+EMUH7XL1twdgohkQG37oQksKhg@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="94eb2c18826873e8c5056509d4eb"
Subject: Re: [PHP-DEV][RFC][DISCUSSION] Deprecate the backtick operator
From: tendoaki@gmail.com (Michael Morris)

--94eb2c18826873e8c5056509d4eb
Content-Type: text/plain; charset="UTF-8"

On Mon, Feb 12, 2018 at 1:43 PM, Wes <netmo.php@gmail.com> wrote:

> Again, the reason is: in case in future PHP wants to use backticks for
> unicode strings, like javascript.
> If the community think it's feasible, in PHP 9, 10, whatever, it must be
> deprecated asap.
> If you think PHP should use a different syntax for unicode strings in
> future, you vote no.
> It's as simple as that. I am asking to reserve a particular syntax for
> something that could be needed in some years.
>

Any particular reason why "`unicode string `" wouldn't work?

Trust me, everyone here has at least one feature or operator they would
like to see done differently (cough - namespace operator -  \ - cough) but
the proverbial train left the station a long time ago.

--94eb2c18826873e8c5056509d4eb--