Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Reading long options in C++ program
Top Forums Programming Reading long options in C++ program Post 302611867 by kristinu on Friday 23rd of March 2012 04:38:25 PM
Old 03-23-2012
Reading long options in C++ program
I am reading arguments passed to a C++ program which accepts long options.

Long options start with '--', with the value joined with the option by an = sign, with no intervening spaces.

An example is as follows:

Code:
programName --vdz=15.0

I want to store 'vdz' in variable 'key', whereas 15.0 is stored in variable 'value'.

However I also need to find the character string starting from the first occurance of '='. I call it 'after'. Then assign 'value' by going to the second character position onward.

Code is as follows:
Code:
const char* after = strchr(argv[i], '=');
if (after != NULL) const char* value = after + 1;

Well, 'after' can be viewed as the value I want. Thus I am wondering whether I can assign 'value' immediately, or come up with a better descriptive variable name than 'after'.

Any suggestions?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

reading long filenames from nero to AIX

One of my colleagues is having an issue moving files between a windows box and the AIX servers in the office. The filenames are being truncated though i don't know to what extent. He's using Nero to burn the CD and I think he mentioned he's using Joliet. I found another thread that shows a... (1 Reply)
Discussion started by: categoryzd
1 Replies

2. Shell Programming and Scripting

Help with shell script to run the commands reading options from local file

I have to use shell script to run series of commands on another unix box by connecting through SSH and giving user credentials. For running commands on remote machine I have to use options reading from a local file. Process: Connecting to remote unix server <host1.ibm.com> through ssh Login: ... (2 Replies)
Discussion started by: itsprout
2 Replies

3. Shell Programming and Scripting

using getopt for both short and long options

Hi , I am using getopt for both short and long options as below SHORTOPTS="a:c" LONGOPTS="alpha:,charlie" OPTS=$(getopt -o $SHORTOPTS --longoptions $LONGOPTS -n "$progname" -- "$@") eval set -- "$OPTS" while ; do case $1 in -a|--alpha) echo "-a or --alpha... (0 Replies)
Discussion started by: padmisri
0 Replies

4. Shell Programming and Scripting

using getopt for both short and long options

Hi , I am using getopt for both short and long options as below SHORTOPTS="a:c" LONGOPTS="alpha:,charlie" OPTS=$(getopt -o $SHORTOPTS --longoptions $LONGOPTS -n "$progname" -- "$@") eval set -- "$OPTS" while ; do case $1 in -a|--alpha) echo "-a or --alpha... (1 Reply)
Discussion started by: padmisri
1 Replies

5. Shell Programming and Scripting

using getopt for both short and long options

Hi , I am using getopt for both short and long options as below SHORTOPTS="a:c" LONGOPTS="alpha:,charlie" OPTS=$(getopt -o $SHORTOPTS --longoptions $LONGOPTS -n "$progname" -- "$@") eval set -- "$OPTS" while ; do case $1 in -a|--alpha) echo "-a or --alpha... (1 Reply)
Discussion started by: padmisri
1 Replies

6. Shell Programming and Scripting

Reading command options one by one

Hi, Just some questions on the script below...? Given: bash-2.03$ command -a option1 name1 name2 ParseOptions() { local Len=${#@} local Ctr=2 #always start at 2 local Name=() local Iter=0 while ; do if <- Is this correct? so I can get the $2... (2 Replies)
Discussion started by: h0ujun
2 Replies

7. Shell Programming and Scripting

Reading command line options from bash script

I have the following code and I am calling it using ./raytrac.bash -u and getting problems. For some reason opt_usage is still 0. opt_usage=0 iarg=0 narg=$# while (($iarg < $narg)) do (( iarg = $iarg + 1 )) arg=$argv usrInputFlag=`echo $arg | awk '/=/ {print 1}; ! /=/... (22 Replies)
Discussion started by: kristinu
22 Replies

8. Shell Programming and Scripting

How to display a message if program hangs(takes too long)

I have a ksh script (script1) that calls another ksh script (script2). If script2.ksh hangs or takes too long to execute I want script1.ksh to kill the call to script2.ksh and instead just display "Script2 can't run right now". Could someone help me with coding this? (1 Reply)
Discussion started by: mrskittles99
1 Replies

9. Shell Programming and Scripting

Perl :: Getopt::Long in the program

While going through some of the perl script... I had found the below line.. use Getopt::Long; my $GetOptionsReturnCode = GetOptions ( '<>' => sub { push(@unknownArg, @_); }, 'h|help' => sub { &helpMessage(); exit 0; }, ); Could anyone please explain the above one ... (1 Reply)
Discussion started by: scriptscript
1 Replies

10. Shell Programming and Scripting

Reading a long literal continued next line

I am trying to identify all messages or prompts from a number of COBOL programs and they can usually be identified by a pair of double quotes on one line. However, sometimes the literal will not be finished on the first line but after a dash in column 7 of the next line, the literal will be... (6 Replies)
Discussion started by: wbport
6 Replies

LEARN ABOUT LINUX

cvs-debuild

CVS-DEBUILD(1)                                                General Commands Manual                                               CVS-DEBUILD(1)

NAME

       cvs-debuild - build a Debian package using cvs-buildpackage and debuild

SYNOPSIS

       cvs-debuild [debuild options] [cvs-buildpackage options] [--lintian-opts lintian options]

DESCRIPTION

       cvs-debuild  is  a  wrapper  around cvs-buildpackage to run it with debuild as the package-building program.  (This cannot simply be accom-
       plished using the -C option of cvs-buildpackage, as it does not know how to handle all of the special debuild options.)

       The program simply stashes the debuild and lintian options, and passes them to debuild when it is called by cvs-buildpackage.  All  of  the
       standard debuild options may be used (as listed below), but note that the root command specified by any --rootcmd or -r command-line option
       will be passed as an option to cvs-buildpackage.  The first non-debuild option detected will  signal  the  start  of  the  cvs-buildpackage
       options.

       The  selection  of  the  root  command is slightly subtle: if there are any command-line options, these will be used.  If not, then if cvs-
       buildpackage is set up to use a default root command, that will be used.  Finally, if neither of these are the case, then debuild will  use
       its procedures to determine an appropriate command, as described in its documentation.

       See the manpages for debuild(1) and cvs-buildpackage for more information about the behaviour of each.

OPTIONS

       The  following are the debuild options recognised by cvs-debuild.  All cvs-buildpackage and lintian options are simply passed to the appro-
       priate program.  For explanations of the meanings of these variables, see debuild(1).

       --no-conf, --noconf

       --rootcmd=gain-root-command, -rgain-root-command

       --preserve-env

       --preserve-envvar=var, -evar

       --set-envvar=var=value, -evar=value

       --lintian, --no-lintian

       --ignore-dirname, --check-dirname
              These should not be needed, but it is provided nevertheless.

SEE ALSO

       cvs-buildpackage(1), debuild(1), dpkg-buildpackage(1) and lintian(1).

AUTHOR

       This program was written by Julian Gilbey <jdg@debian.org>.

DEBIAN                                                           Debian Utilities                                                   CVS-DEBUILD(1)
All times are GMT -4. The time now is 01:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy