From: Alan Watson <email@example.com>
Subject: Re: How to edit filenames in rc scripts without sed
Date: Mon, 16 Aug 1993 13:08:24 -0400 [thread overview]
Message-ID: <9308161708.AA17951@oldp.astro.wisc.edu> (raw)
I concur with Steve.
However, I would like to point out one possible problem with basename
in this regard -- many basename executables are /bin/sh scripts which
call expr three times. On my machine, the difference in speed between
the /bin/sh-based system basename and the pure-binary GNU basename is a
factor of 4 (which is the difference in the number of fork/exec
Anything based on ifs separation will probably come to grief on file
names containing repeated dots, such as `foo..bar'.
next reply other threads:[~1993-08-16 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-08-16 17:08 Alan Watson [this message]
-- strict thread matches above, loose matches on Subject: below --
1993-08-16 16:30 Steve_Kilbane
1993-08-16 16:19 Vincent Broman
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).