Commit Graph

8 Commits

Author SHA1 Message Date
phil
e285bfacc1 Add a new example to SYNOPSIS, change the example. This is in response
to the fact that the /bin/sh set command always sets the exit status to
0, so testing $? will not help discover if getopt found an error if
getopt is used via "set -- `getopt ....`".  (POSIX 1003.2 D11 draft says
that the sh set command must return 0 as the exit status.)

I think that POSIX is wrong or that is is not well enough specified to
allow the result of the set to be the exit status of the getopt.  But
considering the sequential nature of execution, the set is done last
and is the "last command" and therefore must be the one to set the exit
status.  At least there is a work-around for shell scripts.
1997-07-18 00:18:26 +00:00
tls
9d225a1783 RCS ID police 1997-01-09 20:18:21 +00:00
jtc
8f2827a1fb update some old-man macros that hadn't been updated; PR #1194 1995-07-07 22:41:30 +00:00
cgd
7bcf9338df specify man pages the new way. 1994-12-22 12:29:38 +00:00
jtc
7e06b2a1e2 Fix spelling errors. 1994-01-11 02:21:43 +00:00
mycroft
aee4b07b8a Add RCS identifiers, remove some completely useless RCS logs and patchkit
headers, and a few other insignificant changes.
1993-08-02 17:48:44 +00:00
nate
66cb129044 Got rid of cruft at the bottom of the man page 1993-07-27 18:09:27 +00:00
brezak
a7ee7f88c1 Add getopt(1) from ref public sources. 1993-06-21 12:43:56 +00:00