Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:76499
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain notjam.es designates 209.85.220.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <slrnlunm9p.775.dsp@dsp.local>
References: <CAESVnVqd6m5-Dmhff0OiSFZxRNVBX8AvCQQmVYnDt7+gOJ-xug@mail.gmail.com>
 <BEDB9A15-DBC6-4C7F-BEA2-31779534EFA1@ajf.me> <CAESVnVrM6=TPVXbfSnV+jP=Lmiie83-fx6JdJcxENhLWbiZa6Q@mail.gmail.com>
 <slrnlunm9p.775.dsp@dsp.local>
Date: Wed, 13 Aug 2014 18:12:52 -0400
Message-ID: <CANjWU4gauv=RRe2mrSrfWBQsnG_qc1toEXOtGgEWiwSdeuSvUw@mail.gmail.com>
To: David Soria Parra <dsp@php.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [VOTE] Mutliple defaults in switch statements
From: james@notjam.es (James Ward)

I'm not entirely sure that a backwards compatibility break in a minor
release would be considered non-controversial.

While this change is pretty trivial, both technically and
syntactically, I'm unsure why there even is an RFC process in place if
it's going to be ignored because it's "too much trouble".

I was also under the impression that RFCs exist to get comments which
on a particular subject - which may or may not include nitpicking
because what may be a small issue to some people could be a large
issue to others.  It's been shown previously where this could be used
and could cause code that previously executed to not execute which
seems like a problem.

I see this as a bad design choice in the language which should be
rectified... just in a major version.