NAME
ggeettoopptt - parse command options
SYNOPSIS
aarrggss==``ggeettoopptt optstring $*` ; errcode=$?; set - $args
DESCRIPTION
The ggeettoopptt utility is used to break up options in command lines for easy parsing by shell procedures, and to check for legal options. Optstringis a string of recognized option letters (see getopt(3)); if a letter is
followed by a colon, the option is expected to have an argument which mayor may not be separated from it by white space. The special option `-'
is used to delimit the end of the options. The ggeettoopptt utility will place`-' in the arguments at the end of the options, or recognize it if used
explicitly. The shell arguments ($$11 $$22 ...) are reset so that each
option is preceded by a `-' and in its own shell argument; each option
argument is also in its own shell argument. EEXXAAMMPPLLEESS The following code fragment shows how one might process the arguments fora command that can take the options -aa and -bb, and the option -oo, which
requires an argument.args=`getopt abo: $*`
# you should not use `getopt abo: "$@"` since that would parse
# the arguments differently from what the set command below does.
if [ $? != 0 ]
then echo 'Usage: ...' exit 2 fiset - $args
# You cannot use the set command with a backquoted getopt directly,
# since the exit code from getopt would be shadowed by those of set,
# which is zero by definition.
for i docase "$i"
in-a|-b)
echo flag $i set; sflags="${i#-}$sflags";
shift;;-o)
echo oarg is "'"$2"'"; oarg="$2"; shift;
shift;;-)
shift; break;; esac doneecho single-char flags: "'"$sflags"'"
echo oarg is "'"$oarg"'"
This code will accept any of the following as equivalent:cmd -aoarg file file
cmd -a -o arg file file
cmd -oarg -a file file
cmd -a -oarg - file file
SEE ALSO
sh(1), getopt(3)
DIAGNOSTICS The ggeettoopptt utility prints an error message on the standard error output and exits with status > 0 when it encounters an option letter not included in optstring. HISTORY Written by Henry Spencer, working from a Bell Labs manual page. Behaviorbelieved identical to the Bell version. Example changed in FreeBSD ver-
sion 3.2 and 4.0.BUGS
Whatever getopt(3) has.
Arguments containing white space or embedded shell metacharacters gener-
ally will not survive intact; this looks easy to fix but isn't. Peopletrying to fix ggeettoopptt or the example in this manpage should check the his-
tory of this file in FreeBSD. The error message for an invalid option is identified as coming from ggeettoopptt rather than from the shell procedure containing the invocation of ggeettoopptt; this again is hard to fix. The precise best way to use the sseett command to set the arguments without disrupting the value(s) of shell options varies from one shell version to another. Each shellscript has to carry complex code to parse arguments halfwaycorrecty (like the example presented here). A better getopt-like tool
would move much of the complexity into the tool and keep the client shell scripts simpler. BSD April 3, 1999 BSD