From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-workers@sunsite.dk
Subject: Re: treatment of empty strings - why is this not a bug?
Date: Sat, 17 Jan 2009 17:53:12 +0000 [thread overview]
Message-ID: <20090117175312.107130d7@pws-pc> (raw)
In-Reply-To: <m3vdsemrc6.fsf@klanderman.net>
On Sat, 17 Jan 2009 00:31:05 -0500
Greg Klanderman <gak@klanderman.net> wrote:
> >>>>> Bart Schaefer <schaefer@brasslantern.com> writes:
>
> > Consider an array populated by using a glob pattern, which is then
> > subjected to replacement using $arr:s/pat// or $arr:h or $arr:t.
> > You don't know at time of execution what will be matched in by the
> > glob, nor necessarily what will be left behind after substitution.
> > If the substitution results in an emtpy string, how often do you
> > want that to remain in the argument list of whatever action you next
> > apply to the contents of the array?
>
> I do not agree with this reasoning, but I don't think it's worth
> continuing to argue about it.
It's not just reasoning, it's actually used all over the place for
eliminating unwanted matches.
It's probably worth getting one think crystal clear: there is absolutely
no likelihood of changing basic syntactic defaults, which is a recipe
for disaster. So you're right, there's not a lot point arguing.
--
Peter Stephenson <p.w.stephenson@ntlworld.com>
Web page now at http://homepage.ntlworld.com/p.w.stephenson/
next prev parent reply other threads:[~2009-01-17 17:53 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 7:32 Greg Klanderman
2009-01-13 19:24 ` Peter Stephenson
2009-01-13 22:08 ` Peter Stephenson
2009-01-15 20:11 ` Greg Klanderman
2009-01-15 20:29 ` Peter Stephenson
2009-01-16 10:02 ` Peter Stephenson
2009-01-15 20:28 ` Greg Klanderman
2009-01-15 20:34 ` Peter Stephenson
2009-01-16 4:19 ` Bart Schaefer
2009-01-16 17:35 ` Greg Klanderman
2009-01-16 17:55 ` Peter Stephenson
2009-01-16 19:40 ` Greg Klanderman
2009-01-16 23:26 ` Richard Hartmann
2009-01-17 3:45 ` Bart Schaefer
2009-01-17 3:35 ` Bart Schaefer
2009-01-17 5:31 ` Greg Klanderman
2009-01-17 17:53 ` Peter Stephenson [this message]
2009-05-17 4:55 PATCH: make PROMPT_SP end-of-line marker configurable Greg Klanderman
2009-05-17 17:27 ` Peter Stephenson
2009-05-17 18:04 ` Greg Klanderman
2009-05-17 19:23 ` Peter Stephenson
2009-05-18 1:00 ` Greg Klanderman
2009-05-18 18:27 ` Greg Klanderman
[not found] <gak@klanderman.net>
2009-06-26 20:40 ` bug in ztrftime(): '%e' and '%f' specifiers swapped Greg Klanderman
2009-06-26 21:23 ` Peter Stephenson
2009-06-26 21:57 ` Greg Klanderman
2010-02-05 17:01 have '&' automatically disown? Greg Klanderman
2010-02-05 17:33 ` Peter Stephenson
2010-02-05 17:36 ` Peter Stephenson
2010-02-06 3:26 ` Greg Klanderman
2010-02-07 18:20 ` Peter Stephenson
2010-02-07 21:06 ` Greg Klanderman
2010-02-07 21:34 ` Peter Stephenson
2010-02-07 22:36 ` Bart Schaefer
2010-09-02 14:57 ` Greg Klanderman
2010-09-05 19:11 ` Bart Schaefer
2010-09-06 1:50 ` Greg Klanderman
2010-02-07 21:59 ` 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=20090117175312.107130d7@pws-pc \
--to=p.w.stephenson@ntlworld.com \
--cc=zsh-workers@sunsite.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).