Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:105175
MIME-Version: 1.0
References: <CAF+90c_DYFQ_7dXvHg-8DfVJ9zQT8xYfFObiJCLHFskFgqhJeQ@mail.gmail.com>
 <CAEYWF=7GGiQ1d5262vDu6A1U3kV0hcJyqXmbDPg2zePskGQxsg@mail.gmail.com>
In-Reply-To: <CAEYWF=7GGiQ1d5262vDu6A1U3kV0hcJyqXmbDPg2zePskGQxsg@mail.gmail.com>
Date: Tue, 9 Apr 2019 14:54:49 +0100
Message-ID: <CALKiJKq8sVYmwuVtBn_j0x3yO6VpVgeLs6WmsxX36O_qRkaSWQ@mail.gmail.com>
To: bishop@php.net
Cc: Nikita Popov <nikita.ppv@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000009b5b120586194c12"
Subject: Re: [PHP-DEV] [RFC] Deprecate left-associative ternary operator
From: rowan.collins@gmail.com (Rowan Collins)

--0000000000009b5b120586194c12
Content-Type: text/plain; charset="UTF-8"

On Tue, 9 Apr 2019 at 11:19, Bishop Bettini <bishop@php.net> wrote:

> See also Bug 61915[1], which suggests leaving ? left and introducing ?? for
> right. Personally I don't see any benefit to keeping a ternary with left
> associativity.
>


?? wouldn't work, because that's now the null-coalescing operator. (I've no
idea if it would be ambiguous to the parser to have it mean both, but it
would be horrible for humans to read!)

Obviously, that doesn't rule out having a new syntax of some sort, but it
highlights the usual problem with suggesting new operators: we're running
out of punctuation!

Regards,
-- 
Rowan Collins
[IMSoP]

--0000000000009b5b120586194c12--