From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-38908-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 21097 invoked by alias); 21 Jul 2016 18:33:26 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 38908
Received: (qmail 7573 invoked from network); 21 Jul 2016 18:33:26 -0000
X-Qmail-Scanner-Diagnostics: from mail-lf0-f52.google.com by f.primenet.com.au (envelope-from <schaefer@brasslantern.com>, uid 7791) with qmail-scanner-2.11 
 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1.  
 Clear:RC:0(209.85.215.52):SA:0(0.0/5.0):. 
 Processed in 0.122096 secs); 21 Jul 2016 18:33:26 -0000
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=0.0 required=5.0 tests=HTML_MESSAGE,T_DKIM_INVALID
	autolearn=unavailable autolearn_force=no version=3.4.1
X-Envelope-From: schaefer@brasslantern.com
X-Qmail-Scanner-Mime-Attachments: |
X-Qmail-Scanner-Zip-Files: |
Received-SPF: none (ns1.primenet.com.au: domain at brasslantern.com does not designate permitted sender hosts)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=brasslantern-com.20150623.gappssmtp.com; s=20150623;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc;
        bh=kjipZTzqpgThGQyS/19D2rZIDFHt1vwtmVlg27flZ2A=;
        b=ikj7OCZC54CsWo5dKbFQ6ySAEV0GKofbdt0B/+FirwvLMGIbDF16Xj/yBpla2z7r7I
         OoEvuROT4BmQ3Z8EJUR6XjMW3m1lvq4px5T6LM7dAFHX5ezVRcMyLA5k7TeK7JLyCi/o
         4OK1iapf9yIeklR7WxDvjN1gTIcvfL2sKwaPygTsAeXqI+23GExD6XAyMMUHZrLjayLl
         KA1RlH3ISd98cEFZjYobjpTspgLDve1GAAHf1svKgN0rCapTqq8wyB7CCqoFtk0Tyktm
         J1b8aVIyUPYZJzmYXZgX932wYa7aExc5hzwXkyweqE3FoI+I6ZZe6l+pePbiOLyKGKfb
         SfJg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:mime-version:in-reply-to:references:date
         :message-id:subject:from:to:cc;
        bh=kjipZTzqpgThGQyS/19D2rZIDFHt1vwtmVlg27flZ2A=;
        b=TmvD1TIVx1TIlpWuEHkVHmYEhzKEAIl+lx9V2yYluMtcRc5mEyIRxvs5g75jEnVyEd
         AinM6W9qmjXSMR/p/oHAW92s8JGusD9Ttiw14cuF5GDpV+G7CwpTZqERznrifwVdUysh
         bY7Id+CB/yVuxN1oXDPmmn/g5xSHXpnXd5/ksGz9fvhzOeOW/rL7OvCAWQqx0L0TlhAb
         R2Unbjx15S2fdb1iL/NO74Q+peMpQGshs9ycwQ06gEChSQMdaZp0lL9tq29YrVGPVg2Y
         ZsPAvm5M9diCvC3Ci4JFkmYLCl0sdSqw4tofn2N4gPyvP+hTOLeSD6aEj1QL0Rry+WEA
         uatw==
X-Gm-Message-State: ALyK8tLKydHL7ac1qFbRQzWTgdzVBEpBw3XZWWxcDbsXWMFu6jT+xby2e9JkC7HX7J8K32CPM9Pu2tRLMyCVeA==
MIME-Version: 1.0
X-Received: by 10.25.84.132 with SMTP id i126mr22368639lfb.116.1469125999649;
 Thu, 21 Jul 2016 11:33:19 -0700 (PDT)
In-Reply-To: <CAJnbjpAJWFdTHHJc5DqQvipavoYk8CpBQRDqaP+Mg_SrCqnJ9g@mail.gmail.com>
References: <CAJnbjpAJWFdTHHJc5DqQvipavoYk8CpBQRDqaP+Mg_SrCqnJ9g@mail.gmail.com>
Date: Thu, 21 Jul 2016 11:33:19 -0700
Message-ID: <CAH+w=7YnLYDrSMT7KR3G8QwrZNVKTonsjmOA85jM0JwY8Mmsog@mail.gmail.com>
Subject: Re: Feature request: Bash compliance
From: Bart Schaefer <schaefer@brasslantern.com>
To: =?UTF-8?Q?Sebastian_H=C3=B6ffner?= <info@sebastian-hoeffner.de>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Content-Type: multipart/alternative; boundary=001a1141292e56fec60538298d98

--001a1141292e56fec60538298d98
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Jul 21, 2016 11:29 AM, "Sebastian H=C3=B6ffner" <info@sebastian-hoeffner=
.de>
wrote:
>
> Hi zsh developers,
>
> Bash allows ;& in switch-case statements as a fall-through, for which zsh
> has ;| .

Zsh has allowed the ;& syntax for a long time now.  Where are you
encountering a problem with it?  Or are you just assuming it's a problem
based on someone's write-up?

--001a1141292e56fec60538298d98--