From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-35157-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 22181 invoked by alias); 15 May 2015 21:48:02 -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: 35157
Received: (qmail 19562 invoked from network); 15 May 2015 21:48:00 -0000
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW,
	RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no
	version=3.4.0
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:from:message-id:date:in-reply-to:comments
         :references:to:subject:mime-version:content-type;
        bh=PcfppNzLdEl21+zIQqwTxFp1q2IhNWVz6Wn0bJPFVsk=;
        b=VU7XJbgXeIpjlKg7zvorKpb1swnLeejk7r0CQpcAWD7u0qz1ckCj2miyky+hYnfNr9
         A69u7mfQ8XbjY5iJHUAWvU8Eix6Lgd4mbWpCsa6rMTIQ0SSYZzTahsT2Lt54DAQExkgO
         BEa5QvzdROmHlaVHcW53R3CY8JjVsm7ZHpIJ5f3yqbyrRshjrJgTtsFkWkjAj7XEFiMf
         je+ZpYPWaTZbCWQLCebnIs954MMNlDfb9UfRWR50/5ZrTtb26Q/i19alLjabOEXvrb6l
         mIRTogIyU4QWC+HVJrwwWeK/2dxU7QvRD/glfWaNUZlIC6raiLkOkU64vKIngAR2GRtz
         +r1g==
X-Gm-Message-State: ALoCoQmeL8A4bj86MJIZSH3fvXcq4ftS9VRjllD2Pwep4LQ7xnIalRTB25sbbCszXt5lkNASWthT
X-Received: by 10.182.144.163 with SMTP id sn3mr9956620obb.37.1431726476302;
        Fri, 15 May 2015 14:47:56 -0700 (PDT)
From: Bart Schaefer <schaefer@brasslantern.com>
Message-Id: <150515144804.ZM32343@torch.brasslantern.com>
Date: Fri, 15 May 2015 14:48:04 -0700
In-Reply-To: <20150515214825.124dcf03@ntlworld.com>
Comments: In reply to Peter Stephenson <p.w.stephenson@ntlworld.com>
        "Re: 'case' pattern matching bug with bracket expressions" (May 15,  9:48pm)
References: <55549FB2.80705@inlv.org> 
	<20150514154238.0e547ff0@pwslap01u.europe.root.pri> 
	<5554C3A5.4030205@inlv.org> 
	<20150514165557.59f6bdc9@pwslap01u.europe.root.pri> 
	<20150515093851.57b973bc@pwslap01u.europe.root.pri> 
	<20150515214825.124dcf03@ntlworld.com>
X-Mailer: OpenZMail Classic (0.9.2 24April2005)
To: zsh-workers@zsh.org
Subject: Re: 'case' pattern matching bug with bracket expressions
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On May 15,  9:48pm, Peter Stephenson wrote:
} Subject: Re: 'case' pattern matching bug with bracket expressions
}
} On Fri, 15 May 2015 09:38:51 +0100
} Peter Stephenson <p.stephenson@samsung.com> wrote:
} > I don't think changing the case parsing to do proper words is *that*
} > difficult --- it's always been a bit of a hack, so could do with
} > being fixed.
} 
} I'm on the case, but just to note this isn't completely benign.  There
} are (few) places in functions where we rely on the fact that anything in
} parentheses is parsed as a single quoted string, which won't happen any
} more.

Hm.  It appears we always parsed this "correctly" when using the old style
case statment:

torch% case "foo bar baz" in
case> foo bar *) echo here;;
zsh: parse error near `bar'

So perhaps the most benign thing is to apply the word parsing inside the
matched parens only in some sort of POSIX mode?

} I don't want to have to propagate the
} existing hack any more, however, so this isn't really possible to work
} around.

Urm.  OK.