Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:76372
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.48 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAESVnVr0J5qyAc-L0Yt_3Ahab5LVgtUErgoKsSPvgwe=QzppTw@mail.gmail.com>
References: <CAESVnVr0J5qyAc-L0Yt_3Ahab5LVgtUErgoKsSPvgwe=QzppTw@mail.gmail.com>
Date: Wed, 6 Aug 2014 12:00:25 +0200
Message-ID: <CAH-PCH4bRSGrgicicxtNcQVUBM3gW-TBP1_3RVukw-0=TUpc3A@mail.gmail.com>
To: Sara Golemon <pollita@php.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c2c7a28d924e04fff30ab9
Subject: Re: [PHP-DEV] [RFC] Disallow multiple default blocks in a single
 switch statement
From: tyra3l@gmail.com (Ferenc Kovacs)

--001a11c2c7a28d924e04fff30ab9
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, Aug 6, 2014 at 6:38 AM, Sara Golemon <pollita@php.net> wrote:

> https://wiki.php.net/rfc/switch.default.multiple
>
> 'Cause this code is silly (even if it had case blocks), but we allow it:
>
> switch ($expr) {
>   default:
>     notExecuted();
>     break;
>   default:
>     executed();
> }
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
Hi,

I think dropping this behavior is a good idea, but I'm confused by the
reasoning related to the langspec.
This rfc targets php.next (which is a safe move as this has BC break albeit
would require some questionable code), but the langspec was agreed to be
based on 5.6 and document how that works.
So even if we accept this rfc, and remove the multiple default case,
wouldn't we still need to document the current behavior in the spec (maybe
mentioning that it will go away in php-net)?

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--001a11c2c7a28d924e04fff30ab9--