Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:107579 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 56572 invoked from network); 19 Oct 2019 09:37:06 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 19 Oct 2019 09:37:06 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id D187C2D207B for ; Sat, 19 Oct 2019 00:22:11 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp3.php.net X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: X-Spam-Virus: No Received: from mail-wm1-x32c.google.com (mail-wm1-x32c.google.com [IPv6:2a00:1450:4864:20::32c]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp3.php.net (Postfix) with ESMTPS for ; Sat, 19 Oct 2019 00:22:11 -0700 (PDT) Received: by mail-wm1-x32c.google.com with SMTP id r19so8262368wmh.2 for ; Sat, 19 Oct 2019 00:22:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=l1912NzVef6R6Ffu1jNBNIlA6v9VOiYnk9Bolkjqxs0=; b=aWJE8+7841a+ozRbsS8UuDYzmN608OXehGqIZkDOteb5OG5rwV77Y6xcYvARodgucO H5n9Ylxf59BrNZ2qdSlrSaTiB9CzVuKvpgXl5Fya0lt9GMWDW97HYTZ9yzK2wc+6NswJ Oqt2y5Cysv2KRk0a4hwZ3b+6ohBgY0ld4kS8vjOt2qtalrUjzzDl+eqUBr+V2M3sLwb4 PiUrdUDyOFwyqslda6HL6+hpJziT+AunQ0QNlJ2ux4/zjr19Fa3GaZ/J0Z4UwC7Bp/XX /r6rigfuWGC2IIzTufiLgPk1bMwetWJlf3TJrAyVXI9rsU1RerkVvmtMUdiZ7qyf7fF9 +uwg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=l1912NzVef6R6Ffu1jNBNIlA6v9VOiYnk9Bolkjqxs0=; b=ipVGzKNX5pRWV/1UJXOhrFEzGw7zHHYuWFq2/CCR2Z3sEYEEjRmLodnb4yXAC5KP9H BER5ijtOZ4UE+Bqxmq8avTbhe7FCuL3+QT9+aKFLYOYrdVlDgN+JqNY80PXr4QhmObCq YcgaAlCghsJVWaGQGJlnOlrgQXzj4G09SPNKQ0LF/ds5yLFiHS+vvOn+M+Eiil9ExCBH DbbztLycnF1nT1oshLTVwxpcYJtK/aXRgiXbkYNKBj31b/lzMyK8nOb7A0D76BHlpz+r HxiXcwPTf3RFiA5gkD85HRI0ORZp8qIXCiYx2Z92MushJbNgCoF0gWFDINzfLdMrovyZ RIVQ== X-Gm-Message-State: APjAAAXNyr58x4OrvsgM8nOOefSE81feEiKyiu1o6zpk6UYgj2D3vV/s GLtBF2zzmRX7B/F3jUiHZYmb6G0RxdEdUMf8u7Ap0muW X-Google-Smtp-Source: APXvYqxsHc2jz1i4GK3uim/R+y2X9rbIiO3O99tKo7DPV1QBsG/Z7rOwnkt7SA5eSYBz7RL4CpIyHw0ETAY9Z1XmBcE= X-Received: by 2002:a05:600c:23cd:: with SMTP id p13mr988878wmb.30.1571469729799; Sat, 19 Oct 2019 00:22:09 -0700 (PDT) MIME-Version: 1.0 References: <929062F1-E83F-4D81-B2C6-3916B744E101@newclarity.net> <5da8e051.1c69fb81.b05ef.ef7dSMTPIN_ADDED_MISSING@mx.google.com> <11ada3a9-ee9a-1364-7a06-96d1533d544b@alec.pl> In-Reply-To: <11ada3a9-ee9a-1364-7a06-96d1533d544b@alec.pl> Date: Sat, 19 Oct 2019 00:21:57 -0700 Message-ID: To: "A.L.E.C" Cc: PHP internals list Content-Type: multipart/alternative; boundary="0000000000000525c905953e4f2b" X-Envelope-From: Subject: Re: [PHP-DEV] Adding explicit intent for SWITCH/CASE fall through? From: kris.craig@gmail.com (Kris Craig) --0000000000000525c905953e4f2b Content-Type: text/plain; charset="UTF-8" On Sat, Oct 19, 2019 at 12:06 AM A.L.E.C wrote: > On 10/18/19 8:57 PM, Mike Schinkel wrote: > > Imo, this would make more sense if fallthrough did something more, e.g. > allowing > > case X: > if (something) { > fallthrough; > } > something-else; > break; > case Y: .... > > +1 If we're going to do this, let's take the opportunity to make it even more useful. I love the idea of being able to explicitly define fallthrough points in a case. I agree that "continue" is the logically ideal solution, but the BC breakage negates that. So I'd have to go with "next", as it's both concise and descriptive. --Kris --0000000000000525c905953e4f2b--