02-20-2019
Your question is not clear at all. In first code Input arguments are always defined in the variable argc. In the second example, the parameters for the 64-bit system are enumerated. Since the transition from 32 to 64-bit broke the compatibility of the transfer in a function an indefinite number of parameters. Some parameters were passed to the function through the registers and not through the stack. Therefore, macros were invented va_list, va_start, va_end. These are all different things. Choose what you need.
This User Gave Thanks to nezabudka For This Post:
10 More Discussions You Might Find Interesting
1. Programming
I'm using getopt() to get command line options.One the optons accepts and argument.The argument is and offset.I was wondering how can I scecify that it's argument is of the type off_t.I've something like this "offset=(off_t)optarg" and it don't work. (1 Reply)
Discussion started by: angelfly
1 Replies
2. Shell Programming and Scripting
scriptname
i have made a script to perform so tasks and i managed to complete the tasks for all the options
the problem i am facing is that i can run the scripts individually but i would like to make it such that it can accept multiple options and give me the appropriate output
e.g.... (1 Reply)
Discussion started by: problems
1 Replies
3. Shell Programming and Scripting
#!/bin/sh
set -- `getopt "abco:" "$@"`
a= b= c= o=
while :
do
case "$1" in
-a) a=1;;
-b) b=1;;
-c) c=1;;
-o) shift; o="$1";;
--) break;;
esac
shift
done
shift # get rid of --
# rest of script...
# e.g.
ls -l $@ (6 Replies)
Discussion started by: Hitori
6 Replies
4. Shell Programming and Scripting
I m trying to use getopt
This is my script, but it doesn't take argument in variable,
Please help.
set - - `getopt mscl: $*`
if
then
echo "Exiting...."
exit 2
fi
for i in $*
do
case $i in
-m) MAIL="$i"; shift;;
-s) SCRIPT=$OPTARG; shift;;
-c) COB=$OPTARG; shift;;... (2 Replies)
Discussion started by: darshakraut
2 Replies
5. Shell Programming and Scripting
:)
Can anybody help me about how to use getopt in shell scripting. (3 Replies)
Discussion started by: darshakraut
3 Replies
6. Solaris
Hi All,
Could anyone tell me how to use getopt command.....?
Thanks,
Pintu (2 Replies)
Discussion started by: pintupatro
2 Replies
7. Shell Programming and Scripting
Hi,
I want to use the getopt function to parse some arguments for a script.
while getopts "i:f:r:" OPTION
do
case $OPTION in
i) iter=$OPTARG;;
f) frame=$OPTARG;;
r) roi=$OPTARG;;
?) echo Usage: ......
exit 2;;
esac
done
However, I... (5 Replies)
Discussion started by: giorgos193
5 Replies
8. HP-UX
I have a macro defined like this:
#define MM7_RETURN(errorNr, ...) \
{ \
if(errorNr != MM7_RS_NoError) \
{ ... (1 Reply)
Discussion started by: Marzullo
1 Replies
9. Shell Programming and Scripting
I am struggling to understand how getopt can be used in a csh script.
can anybody post a csh script using getopt.
Please! (4 Replies)
Discussion started by: animesharma
4 Replies
10. Shell Programming and Scripting
Hi All,
An old work friend wrote a script which I've been trying to understand how a section of it currently works and work out how i can add some command line switches which i can use later in the script to append the output depending on the command line arguements.
Currently it works by... (1 Reply)
Discussion started by: mutley2202
1 Replies
LEARN ABOUT MOJAVE
getopt
GETOPT(1) BSD General Commands Manual GETOPT(1)
NAME
getopt -- parse command options
SYNOPSIS
args=`getopt optstring $*` ; errcode=$?; set -- $args
DESCRIPTION
The getopt utility is used to break up options in command lines for easy parsing by shell procedures, and to check for legal options.
Optstring is 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 may or may not be separated from it by white space. The special option '--' is used to delimit the end of the options. The
getopt utility will place '--' in the arguments at the end of the options, or recognize it if used explicitly. The shell arguments ($1 $2
...) 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 argu-
ment.
EXAMPLES
The following code fragment shows how one might process the arguments for a command that can take the options -a and -b, and the option -o,
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
fi
set -- $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
do
case "$i"
in
-a|-b)
echo flag $i set; sflags="${i#-}$sflags";
shift;;
-o)
echo oarg is "'"$2"'"; oarg="$2"; shift;
shift;;
--)
shift; break;;
esac
done
echo 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 getopt 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. Behavior believed identical to the Bell version. Example changed in FreeBSD
version 3.2 and 4.0.
BUGS
Whatever getopt(3) has.
Arguments containing white space or embedded shell metacharacters generally will not survive intact; this looks easy to fix but isn't. Peo-
ple trying to fix getopt or the example in this manpage should check the history of this file in FreeBSD.
The error message for an invalid option is identified as coming from getopt rather than from the shell procedure containing the invocation of
getopt; this again is hard to fix.
The precise best way to use the set command to set the arguments without disrupting the value(s) of shell options varies from one shell ver-
sion to another.
Each shellscript has to carry complex code to parse arguments halfway correcty (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