From: Rich Salz <rsalz@bbn.com>
To: malte@techfak.uni-bielefeld.de, rc@archone.tamu.edu
Subject: Re: improving "~" builtin ?!
Date: Thu, 12 Dec 1991 09:32:47 -0600 [thread overview]
Message-ID: <9112121532.AA17433@litchi.bbn.com> (raw)
I think it's a bad idea and adds lots of complexity for no general-purpose
gain. For example:
~ 2 foo.yacc [fg]oo* *.yacc
Does the first pattern become "[f" or is the 2 the number of pattern
tokens so that it becomes "[fg]o"? If the first, then the pattern doesn't
match; if the second, then it does match. Confusing, and requires
introducing a new concept "the pattern match token".
What about the second pattern -- it becomes "*." When compared with "fo"
it now fails! Counter-intuitive. If strcmp succeeds you expect strncmp
to succeed.
/r$
next reply other threads:[~1991-12-12 15:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1991-12-12 15:32 Rich Salz [this message]
-- strict thread matches above, loose matches on Subject: below --
1991-12-12 15:49 Byron Rakitzis
1991-12-12 15:10 malte
1991-12-12 13:06 malte
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=9112121532.AA17433@litchi.bbn.com \
--to=rsalz@bbn.com \
--cc=malte@techfak.uni-bielefeld.de \
--cc=rc@archone.tamu.edu \
/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.
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).