From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: broken parsing with $((`:`))
Date: Wed, 15 Apr 2015 08:13:48 -0700 [thread overview]
Message-ID: <150415081348.ZM26219@torch.brasslantern.com> (raw)
In-Reply-To: <20150415100324.296ffa3e@pwslap01u.europe.root.pri>
On Apr 15, 10:03am, Peter Stephenson wrote:
}
} Yes, indeed --- there's a funny internal special case for empty strings
} that I never quite get my head around.
}
} - if (!*s) {
} + if (!*s || *s == Nularg) {
I wonder if (a) there are other overlooked cases like this and (b) if it
would be useful to have a #define macro for (c == '\0' || c == Nularg).
A quick grep doesn't find existing cases of that test other than this
new one, but of course if the Nularg part were forgotten, it wouldn't.
I suspect it just isn't that common because Nularg goes away after the
parsing pass.
} (Please, God, make the problems with command and math substitution
} parsing stop now.)
Indeed ... at what point should we consider 5.0.8 to get all these little
edge-case fixes out into the field?
next prev parent reply other threads:[~2015-04-15 15:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 3:05 Mike Frysinger
2015-04-15 9:03 ` Peter Stephenson
2015-04-15 15:13 ` Bart Schaefer [this message]
2015-04-15 15:26 ` Peter Stephenson
2015-04-15 16:23 ` Potential 3.0.8 [was Re: broken parsing with $((`:`))] Bart Schaefer
2015-04-22 9:01 ` Peter Stephenson
2015-04-25 17:14 ` Pre-3.0.8 consolidated PATCH Bart Schaefer
2015-04-25 18:29 ` Axel Beckert
2015-04-25 18:46 ` FIVE-ZERO-EIGHT (was Re: Pre-3.0.8 consolidated PATCH) Bart Schaefer
2015-08-15 23:14 ` bug with expansion and backslashes Oliver Kiddle
2015-08-16 1:22 ` Bart Schaefer
2015-04-15 15:37 ` broken parsing with $((`:`)) Peter Stephenson
2015-04-15 16:13 ` Bart Schaefer
2015-04-15 16:31 ` Peter Stephenson
2015-04-17 4:39 Mikael Magnusson
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=150415081348.ZM26219@torch.brasslantern.com \
--to=schaefer@brasslantern.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).