[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: problem with egrep and fgrep
From: |
Ralph Corderoy |
Subject: |
Re: problem with egrep and fgrep |
Date: |
Tue, 07 Sep 2004 09:48:04 GMT |
Hi Bruce,
> There are several simple, straight forward solutions:
>
> 1. The script can evaluate $(dirname $0) and the extra time is the
> cost of sticking strictly to not evaluating $(basename $0) in the
> program itself. If performance tuning is an issue, the script author
> can use the flag to the real grep program.
I'm not sure expecting the path of the script to be in argv[0] is
portable. IIRC there's some older Unixes that didn't do this.
> 3. Be willing to conceed that traditional usage might be more
> important than adhering to a coding standard written after fgrep and
> egrep. Besides, the language of the standard allows for grandfathered
> utilities. These are old enough to qualify.
Agreed, I'd rather have expected behaviour than conformance to a coding
standard written after that behaviour existed, especially if that
standard provides a `get out'.
Cheers,
--
Ralph Corderoy. http://inputplus.co.uk/ralph/ http://troff.org/
Message not available
- Message not available
- Re: problem with egrep and fgrep, Ralph Corderoy, 2004/09/02
- Re: problem with egrep and fgrep, Bob Proulx, 2004/09/03
- Message not available
- Re: problem with egrep and fgrep, Ralph Corderoy, 2004/09/07
- Re: problem with egrep and fgrep, Bob Proulx, 2004/09/12
- Re: problem with egrep and fgrep, Paul Jarc, 2004/09/13
- Re: problem with egrep and fgrep, Bob Proulx, 2004/09/13
- Re: problem with egrep and fgrep, Paul Jarc, 2004/09/13
- Re: problem with egrep and fgrep, Eli Zaretskii, 2004/09/13
- Message not available
- Re: problem with egrep and fgrep, Eric Backus, 2004/09/13
- Re: problem with egrep and fgrep, Bob Proulx, 2004/09/15