Categories:
.NET (357)
C (330)
C++ (183)
CSS (84)
DBA (2)
General (7)
HTML (4)
Java (574)
JavaScript (106)
JSP (66)
Oracle (114)
Perl (46)
Perl (1)
PHP (1)
PL/SQL (1)
RSS (51)
Software QA (13)
SQL Server (1)
Windows (1)
XHTML (173)
Other Resources:
How can I open files mentioned on the command line, and parse option flags?
How can I open files mentioned on the command line, and parse option flags?
✍: Guest
Here is a skeleton which implements a traditional Unix-style argv parse, handling option flags beginning with -, and optional filenames. (The two flags accepted by this example are -a and -b; -b takes an argument.)
#include <stdio.h>
#include <string.h>
#include <errno.h>
main(int argc, char *argv[])
{
int argi;
int aflag = 0;
char *bval = NULL;
for(argi = 1; argi < argc && argv[argi][0] == '-'; argi++) {
char *p;
for(p = &argv[argi][1]; *p != '\0'; p++) {
switch(*p) {
case 'a':
aflag = 1;
printf("-a seen\n");
break;
case 'b':
bval = argv[++argi];
printf("-b seen ("%s")\n", bval);
break;
default:
fprintf(stderr,
"unknown option -%c\n", *p);
}
}
}
if(argi >= argc) {
/* no filename arguments; process stdin */
printf("processing standard input\n");
} else {
/* process filename arguments */
for(; argi < argc; argi++) {
FILE *ifp = fopen(argv[argi], "r");
if(ifp == NULL) {
fprintf(stderr, "can't open %s: %s\n",
argv[argi], strerror(errno));
continue;
}
printf("processing %s\n", argv[argi]);
fclose(ifp);
}
}
return 0;
}
(This code assumes that fopen sets errno when it fails, which is not guaranteed, but usually works, and makes error messages much more useful.
There are several canned functions available for doing command line parsing in a standard way; the most popular one is getopt.
Here is the above example, rewritten to use getopt:
extern char *optarg;
extern int optind;
main(int argc, char *argv[])
{
int aflag = 0;
char *bval = NULL;
int c;
while((c = getopt(argc, argv, "ab:")) != -1)
switch(c) {
case 'a':
aflag = 1;
printf("-a seen\n");
break;
case 'b':
bval = optarg;
printf("-b seen ("%s")\n", bval);
break;
}
if(optind >= argc) {
/* no filename arguments; process stdin */
printf("processing standard input\n");
} else {
/* process filename arguments */
for(; optind < argc; optind++) {
FILE *ifp = fopen(argv[optind], "r");
if(ifp == NULL) {
fprintf(stderr, "can't open %s: %s\n",
argv[optind], strerror(errno));
continue;
}
printf("processing %s\n", argv[optind]);
fclose(ifp);
}
}
return 0;
}
The examples above overlook a number of nuances: a lone ``-'' is often taken to mean ``read standard input''; the marker ``--'' often signifies the end of the options (proper versions of getopt do handle this); it's traditional to print a usage message when a command is invoked with improper or missing arguments.
If you're wondering how argv is laid out in memory, it's actually a ``ragged array'';
2015-03-11, 1316👍, 0💬
Popular Posts:
How To Use "IF" Statements on Multiple Conditions? - Oracle DBA FAQ - Understanding PL/SQL Language ...
How Can we change priority & what levels of priority are provided by Dot Net? Thread Priority ca...
What is Concern in AOP? gA concern is a particular goal, concept, or area of interesth There are m...
What is the difference between delegate and events? ã Actually events use delegates in bottom. But ...
How To Enter Microseconds in SQL Statements? - MySQL FAQs - Introduction to SQL Date and Time Handli...