From: Chet Ramey <chet.ramey@case.edu>
To: Peter Stephenson <p.stephenson@samsung.com>,
Martijn Dekker <martijn@inlv.org>,
zsh-workers@zsh.org
Cc: chet.ramey@case.edu
Subject: Re: 'case' pattern matching bug with bracket expressions
Date: Thu, 14 May 2015 19:45:50 -0400 [thread overview]
Message-ID: <555533AE.4000705@case.edu> (raw)
In-Reply-To: <20150514154238.0e547ff0@pwslap01u.europe.root.pri>
On 5/14/15 10:42 AM, Peter Stephenson wrote:
> The handling of ']' at the start is mandated, if I've
> followed all the logic corretly --- POSIX 2007 Shell and Utilities
> 2.13.1 says:
>
> [
> If an open bracket introduces a bracket expression as in XBD RE
> Bracket Expression, except that the <exclamation-mark> character (
> '!' ) shall replace the <circumflex> character ( '^' ) in its role
> in a non-matching list in the regular expression notation, it shall
> introduce a pattern bracket expression. A bracket expression
> starting with an unquoted <circumflex> character produces
> unspecified results. Otherwise, '[' shall match the character
> itself.
>
> The languaqge is a little turgid, but I think it's saying "unless
> you have ^ or [ just go with the RE rules in [section 9.3.5]".
I think it means that improperly-formed pattern bracket expressions have
to be matched by a literal `[' followed by whatever the following
characters mean.
> I haven't read through the "case" doc so there may be some killer reason
> why that " | " has to be a case separator and not part of a
> square-bracketed expression. But that would seem to imply some form of
> hierarchical parsing in which those characters couldn't occur within a
> pattern.
It's the grammar. If you want `|' to be in a pattern you have to quote it.
Otherwise it's a metacharacter and a token delimiter (section 2.2).
The basic idea is that you tokenize case patterns as words and analyze them
as patterns after doing so.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU chet@case.edu http://cnswww.cns.cwru.edu/~chet/
prev parent reply other threads:[~2015-05-14 23:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 13:14 Martijn Dekker
2015-05-14 13:50 ` [BUG] " Martijn Dekker
2015-05-14 14:42 ` Peter Stephenson
2015-05-14 15:47 ` Martijn Dekker
2015-05-14 15:55 ` Peter Stephenson
2015-05-14 17:30 ` Bart Schaefer
2015-05-15 0:05 ` Chet Ramey
2015-05-14 23:51 ` Chet Ramey
2015-05-15 8:38 ` Peter Stephenson
2015-05-15 20:48 ` Peter Stephenson
2015-05-15 21:48 ` Bart Schaefer
2015-05-14 16:17 ` Peter Stephenson
2015-05-14 17:07 ` Martijn Dekker
2015-05-14 17:43 ` Peter Stephenson
2015-05-15 0:09 ` Chet Ramey
2015-05-14 23:59 ` Chet Ramey
2015-05-14 21:23 ` Chet Ramey
2015-05-14 23:45 ` Chet Ramey [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=555533AE.4000705@case.edu \
--to=chet.ramey@case.edu \
--cc=martijn@inlv.org \
--cc=p.stephenson@samsung.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).