From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Peter Stephenson" <pws@pwstephenson.fsnet.co.uk>,
"Zsh hackers list" <zsh-workers@sunsite.auc.dk>
Subject: RE: bracket expressions and POSIX
Date: Mon, 2 Jul 2001 10:13:22 +0400 [thread overview]
Message-ID: <000301c102be$19047990$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <20010630190039.59EB714286@pwstephenson.fsnet.co.uk>
>
> Clint Adams wrote:
> > POSIX says that \ loses its special meaning within a bracket
> > expression for pattern matching
What gave you that idea? I would be highly surprised if POSIX had different
rules as XPG and SUS; and according to SUS the following still matches abc:
a["\b"]c
Actually, SUS explicitly speaks about both quoting (when parsed by shell)
and escaping (when pattern is interpreted).
<http://www.opengroup.org/onlinepubs/007908799/xcu/chap2.html#tag_001_013>
Note, that patterns in shell are *based* on regular expressions but not
identical (that probably has confused you).
(anyone remember off
> the top of their head how to match both a `]' and a `-'?).
If a bracket expression must specify both - and ], the ] must be placed
first (after the ^, if any) and the - last within the bracket expression.
Where zsh really violates POSIX:
==
Since each asterisk matches zero or more occurrences, the patterns a*b and
a**b have identical functionality
==
Another point is using collating elements, ranges etc ... anything that has
to deal with locale.
-andrej
next prev parent reply other threads:[~2001-07-02 6:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-29 18:22 Clint Adams
2001-06-30 2:14 ` Bart Schaefer
2001-06-30 19:00 ` Peter Stephenson
2001-06-30 18:25 ` Bart Schaefer
2001-07-02 6:13 ` Andrej Borsenkow [this message]
2001-07-02 7:10 ` Bart Schaefer
2001-07-02 7:33 ` Andrej Borsenkow
2001-07-02 7:44 ` Andrej Borsenkow
2001-07-02 13:41 ` Clint Adams
2001-07-02 14:47 ` Andrej Borsenkow
2001-07-02 14:57 ` Clint Adams
2001-07-02 13:31 ` Clint Adams
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='000301c102be$19047990$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=pws@pwstephenson.fsnet.co.uk \
--cc=zsh-workers@sunsite.auc.dk \
/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).