Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85503
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.215.10 cause and error)
Message-ID: <1427459047.17377.23.camel@kuechenschabe>
To: Michael Morris <tendoaki@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
Date: Fri, 27 Mar 2015 13:24:07 +0100
In-Reply-To: <CAGovj_OSqNG5pX-LmWZWe59bHiGvqMB+pKH+nuWzb+zP+cXPig@mail.gmail.com>
References: 
	<CAGovj_OG5qJP5-Wi+3urYwLoCBmT40GVN0Ea8mjPm-GxVdYj_A@mail.gmail.com>
	 <BD2202DD-9E1A-4F1F-8938-A024C9A49F2D@gmail.com>
	 <20150326224056.GB28328@phcomp.co.uk>
	 <822A4769-D028-425A-A1A9-0626414B9B29@gmail.com>
	 <CAGovj_OSqNG5pX-LmWZWe59bHiGvqMB+pKH+nuWzb+zP+cXPig@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Fix the Tenary Operator -- Please!? Please?
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Fri, 2015-03-27 at 08:03 -0400, Michael Morris wrote:
> While breaking backwards compatibility for its own sake is bad, avoiding it
> to keep a bug in the system is worse in my opinion. And again, this is a
> bug. If the way PHP associates could be used for something that would be
> different, but it can't. I honestly doubt any code even exists that takes
> advantage of the current behavior.

What you are suggesting is not just "breaking BC" but "Changing behavior
of code in a hard to debug way" as previously working code will suddenly
start to do something else than expected probably without emitting any
error.

If you want this to run this requires a clear migration strategy for the
billions of lines of code out there.

Till this is provided please help focusing on things we can actually
improve, like testing PHP 7 to make sure it will be a stable release.

Thanks,
johannes