Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #14259 > unrolled thread
| Started by | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| First post | 2018-06-20 16:03 -0400 |
| Last post | 2018-06-20 16:03 -0400 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: $OPTIND varibale value is different from sh Chet Ramey <chet.ramey@case.edu> - 2018-06-20 16:03 -0400
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Date | 2018-06-20 16:03 -0400 |
| Subject | Re: $OPTIND varibale value is different from sh |
| Message-ID | <mailman.2315.1529525010.1292.bug-bash@gnu.org> |
On 6/20/18 2:09 PM, Martijn Dekker wrote: > Op 20-06-18 om 13:39 schreef Greg Wooledge: >> I really don't understand what you're doing here, either. The only >> use of OPTIND is after the final call to getopts, when there are no >> more options to process. At that point, OPTIND tells you how many >> times you have to "shift" to get rid of all the options that were >> processed. (And you have to subtract 1, because legacy historical >> reasons.) > > In other words, because all the options have now been processed, OPTIND > points to the first argument *after* the list of options. I don't see how > that is "because legacy historical reasons". It seems both logical and > useful to me. It enables the universal idiom `shift $(( $OPTIND - 1 ))' to throw away the options and option arguments and deal with the rest of the arguments. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
Back to top | Article view | gnu.bash.bug
csiph-web