{"id":630,"date":"2014-04-12T00:01:11","date_gmt":"2014-04-12T07:01:11","guid":{"rendered":"http:\/\/c-for-dummies.com\/blog\/?p=630"},"modified":"2014-04-28T07:11:43","modified_gmt":"2014-04-28T14:11:43","slug":"reading-command-line-options","status":"publish","type":"post","link":"https:\/\/c-for-dummies.com\/blog\/?p=630","title":{"rendered":"Reading Command Line Options"},"content":{"rendered":"

You might think that the command line is a relic of the past. For a mortal user, that’s correct: The only people I know who still dwell at the command prompt are power users. I keep a command prompt (terminal) window open on my computers, just because using the terminal is fast and I happen to know the commands. Yet, internally, all graphical operating systems still reference the command line.
\n
\nIn fact, knowing a few command line tricks is one of those treasured “Windows secrets” you might read about. That’s because even Windows programs use command line options and arguments. So if your dream is to become a Windows programmer, you will eventually have to deal with the main()<\/em> function’s twin arguments, argc<\/code> and *argv[]<\/code>.<\/p>\n

argc<\/code> is the arg<\/em>ument c<\/em>ount<\/p>\n

argv<\/code> are the arg<\/em>ument v<\/em>alues, strings<\/p>\n

Yes, *argv[]<\/code> can be written as **argv<\/code>. To do so is pure evil.<\/p>\n

The **argv<\/code> variable references a string of pointers. Each pointer holds a single argument specified at the command prompt that ran the program. Even Windows programs use those arguments, so this variable isn’t a quaint antique from the days when computers ran only in text-mode.<\/p>\n

While you don’t see a command prompt when a Windows program launches, the system()<\/em> or GUI equivalent command is fully capable of specifying command line arguments.<\/p><\/blockquote>\n

The argc<\/code> variable is an int<\/em> value that describes how many **argv<\/code> pointers are available. Even when argc<\/code> is zero, the **argv<\/code> pointer still references a single item: the name of the program or command being run.<\/p>\n

\r\n#include <stdio.h>\r\n\r\nint main(int argc, char **argv)\r\n{\r\n    int x;\r\n\r\n    for(x=0;x<argc;x++)\r\n        printf(\"Argument %d: %s\\n\",x,*(argv+x));\r\n\r\n    return(0);\r\n}<\/pre>\n
The main()<\/em> function declares its arguments at Line 3. A for<\/em> loop at Line 7 inches through each of the arguments; even when argc<\/code> equals zero, the loop spins once, displaying the argument zero, which is the program’s name.<\/p>\n
The *(argv+x)<\/code> construction in Line 8 uses variable x<\/code> to offset each of the pointers referenced by argv<\/code>. Here’s a sample run:<\/p>\n
blog$<\/span> .\/a.out roses are red \"violets are blue\"
\nArgument 0: .\/a.out
\nArgument 1: roses
\nArgument 2: are
\nArgument 3: red
\nArgument 4: violets are blue<\/code><\/p>\n
Above, the program name is a.out<\/code>. See how the argument enclosed in double quotes is treated as one item? Figure 1 illustrates Code::Block’s output on a Windows PC:<\/p>\n
\"Figure<\/a>
Figure 1. Output to a DOS window for Code::Blocks. (Click to embiggen.)<\/p><\/div>\n
In Code::Blocks, you must specify the command line arguments by using the Project>Set programs’ arguments command. Type the arguments into the Select Target dialog box, shown in Figure 2.<\/p>\n
\"Figure
Figure 2. Setting command line arguments in Code::Blocks.<\/p><\/div>\n
Yes, I know that the apostrophe after programs<\/em> is improper English. I suppose some programmers have a “stick the apostrophe anywhere” attitude about English like other programmers have a “stick the asterisk anywhere” attitude about pointers.<\/p><\/blockquote>\n
This code could have also been written by using array notation, which — honestly — is how most C programmers would write it:<\/p>\n
\r\n#include <stdio.h>\r\n\r\nint main(int argc, char *argv[])\r\n{\r\n    int x;\r\n\r\n    for(x=0;x<argc;x++)\r\n        printf(\"Argument %d: %s\\n\",x,argv[x]);\r\n\r\n    return(0);\r\n}<\/pre>\n
You’ll find one other location where the **<\/code> type of variable is encountered: the computer’s environment. My Lesson from April 2013<\/a> briefly covered how it works.<\/p>\n","protected":false},"excerpt":{"rendered":"
The **<\/code> type of variable rears its ugly head is when your code deals with command line arguments. Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-630","post","type-post","status-publish","format-standard","hentry","category-main"],"_links":{"self":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/630","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=630"}],"version-history":[{"count":7,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/630\/revisions"}],"predecessor-version":[{"id":693,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/630\/revisions\/693"}],"wp:attachment":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=630"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=630"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=630"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}