blob: 89363f95e5b72fff3a8419e449bdff911e3b35f9 [file] [log] [blame]
Misha Brukman9718e962003-10-24 19:59:21 +00001<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
2 "http://www.w3.org/TR/html4/strict.dtd">
3<html>
4<head>
Reid Spencer9bbba0912004-11-16 06:11:52 +00005 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Misha Brukman9718e962003-10-24 19:59:21 +00006 <title>CommandLine 2.0 Library Manual</title>
Misha Brukman3c299112003-11-07 18:11:14 +00007 <link rel="stylesheet" href="llvm.css" type="text/css">
Misha Brukman9718e962003-10-24 19:59:21 +00008</head>
9<body>
Chris Lattner209c7f42001-07-23 23:03:12 +000010
Misha Brukman9718e962003-10-24 19:59:21 +000011<div class="doc_title">
12 CommandLine 2.0 Library Manual
13</div>
Chris Lattner209c7f42001-07-23 23:03:12 +000014
15<ol>
Misha Brukman9718e962003-10-24 19:59:21 +000016 <li><a href="#introduction">Introduction</a></li>
17
Chris Lattner209c7f42001-07-23 23:03:12 +000018 <li><a href="#quickstart">Quick Start Guide</a>
19 <ol>
Misha Brukman9718e962003-10-24 19:59:21 +000020 <li><a href="#bool">Boolean Arguments</a></li>
21 <li><a href="#alias">Argument Aliases</a></li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +000022 <li><a href="#onealternative">Selecting an alternative from a
Misha Brukman9718e962003-10-24 19:59:21 +000023 set of possibilities</a></li>
24 <li><a href="#namedalternatives">Named alternatives</a></li>
25 <li><a href="#list">Parsing a list of options</a></li>
Jim Laskey1d8f6262005-08-25 22:52:43 +000026 <li><a href="#bits">Collecting options as a set of flags</a></li>
Misha Brukman9718e962003-10-24 19:59:21 +000027 <li><a href="#description">Adding freeform text to help output</a></li>
28 </ol></li>
29
Chris Lattner209c7f42001-07-23 23:03:12 +000030 <li><a href="#referenceguide">Reference Guide</a>
Chris Lattnerae853632002-07-25 19:27:01 +000031 <ol>
Chris Lattnere76d4ab2002-08-06 19:36:06 +000032 <li><a href="#positional">Positional Arguments</a>
Chris Lattnerae853632002-07-25 19:27:01 +000033 <ul>
Misha Brukman9718e962003-10-24 19:59:21 +000034 <li><a href="#--">Specifying positional options with hyphens</a></li>
Reid Spencer2c8ab582004-08-13 20:19:14 +000035 <li><a href="#getPosition">Determining absolute position with
36 getPosition</a></li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +000037 <li><a href="#cl::ConsumeAfter">The <tt>cl::ConsumeAfter</tt>
Misha Brukman9718e962003-10-24 19:59:21 +000038 modifier</a></li>
39 </ul></li>
40
41 <li><a href="#storage">Internal vs External Storage</a></li>
42
43 <li><a href="#attributes">Option Attributes</a></li>
44
Chris Lattnere76d4ab2002-08-06 19:36:06 +000045 <li><a href="#modifiers">Option Modifiers</a>
Chris Lattnerae853632002-07-25 19:27:01 +000046 <ul>
Misha Brukman9718e962003-10-24 19:59:21 +000047 <li><a href="#hiding">Hiding an option from <tt>--help</tt>
48 output</a></li>
49 <li><a href="#numoccurrences">Controlling the number of occurrences
50 required and allowed</a></li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +000051 <li><a href="#valrequired">Controlling whether or not a value must be
Misha Brukman9718e962003-10-24 19:59:21 +000052 specified</a></li>
53 <li><a href="#formatting">Controlling other formatting options</a></li>
54 <li><a href="#misc">Miscellaneous option modifiers</a></li>
55 </ul></li>
56
Chris Lattnerc1ae40c2002-08-07 18:27:04 +000057 <li><a href="#toplevel">Top-Level Classes and Functions</a>
Chris Lattnere76d4ab2002-08-06 19:36:06 +000058 <ul>
Misha Brukman9718e962003-10-24 19:59:21 +000059 <li><a href="#cl::ParseCommandLineOptions">The
60 <tt>cl::ParseCommandLineOptions</tt> function</a></li>
61 <li><a href="#cl::ParseEnvironmentOptions">The
62 <tt>cl::ParseEnvironmentOptions</tt> function</a></li>
63 <li><a href="#cl::opt">The <tt>cl::opt</tt> class</a></li>
64 <li><a href="#cl::list">The <tt>cl::list</tt> class</a></li>
Jim Laskey1d8f6262005-08-25 22:52:43 +000065 <li><a href="#cl::bits">The <tt>cl::bits</tt> class</a></li>
Misha Brukman9718e962003-10-24 19:59:21 +000066 <li><a href="#cl::alias">The <tt>cl::alias</tt> class</a></li>
Reid Spencer9bbba0912004-11-16 06:11:52 +000067 <li><a href="#cl::extrahelp">The <tt>cl::extrahelp</tt> class</a></li>
Misha Brukman9718e962003-10-24 19:59:21 +000068 </ul></li>
69
Chris Lattnere76d4ab2002-08-06 19:36:06 +000070 <li><a href="#builtinparsers">Builtin parsers</a>
71 <ul>
72 <li><a href="#genericparser">The Generic <tt>parser&lt;t&gt;</tt>
Misha Brukman9718e962003-10-24 19:59:21 +000073 parser</a></li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +000074 <li><a href="#boolparser">The <tt>parser&lt;bool&gt;</tt>
Misha Brukman9718e962003-10-24 19:59:21 +000075 specialization</a></li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +000076 <li><a href="#stringparser">The <tt>parser&lt;string&gt;</tt>
Misha Brukman9718e962003-10-24 19:59:21 +000077 specialization</a></li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +000078 <li><a href="#intparser">The <tt>parser&lt;int&gt;</tt>
Misha Brukman9718e962003-10-24 19:59:21 +000079 specialization</a></li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +000080 <li><a href="#doubleparser">The <tt>parser&lt;double&gt;</tt> and
Misha Brukman9718e962003-10-24 19:59:21 +000081 <tt>parser&lt;float&gt;</tt> specializations</a></li>
82 </ul></li>
83 </ol></li>
Chris Lattner209c7f42001-07-23 23:03:12 +000084 <li><a href="#extensionguide">Extension Guide</a>
Chris Lattnerae853632002-07-25 19:27:01 +000085 <ol>
Misha Brukman9718e962003-10-24 19:59:21 +000086 <li><a href="#customparser">Writing a custom parser</a></li>
87 <li><a href="#explotingexternal">Exploiting external storage</a></li>
88 <li><a href="#dynamicopts">Dynamically adding command line
89 options</a></li>
90 </ol></li>
91</ol>
Chris Lattnere76d4ab2002-08-06 19:36:06 +000092
Chris Lattner7911ce22004-05-23 21:07:27 +000093<div class="doc_author">
94 <p>Written by <a href="mailto:sabre@nondot.org">Chris Lattner</a></p>
Misha Brukman9718e962003-10-24 19:59:21 +000095</div>
Chris Lattner209c7f42001-07-23 23:03:12 +000096
97<!-- *********************************************************************** -->
Misha Brukman9718e962003-10-24 19:59:21 +000098<div class="doc_section">
Misha Brukman8becd712003-11-07 19:42:44 +000099 <a name="introduction">Introduction</a>
Misha Brukman9718e962003-10-24 19:59:21 +0000100</div>
Chris Lattner209c7f42001-07-23 23:03:12 +0000101<!-- *********************************************************************** -->
102
Misha Brukman9718e962003-10-24 19:59:21 +0000103<div class="doc_text">
104
105<p>This document describes the CommandLine argument processing library. It will
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000106show you how to use it, and what it can do. The CommandLine library uses a
107declarative approach to specifying the command line options that your program
108takes. By default, these options declarations implicitly hold the value parsed
109for the option declared (of course this <a href="#storage">can be
Misha Brukman9718e962003-10-24 19:59:21 +0000110changed</a>).</p>
Chris Lattner209c7f42001-07-23 23:03:12 +0000111
Misha Brukman9718e962003-10-24 19:59:21 +0000112<p>Although there are a <b>lot</b> of command line argument parsing libraries
113out there in many different languages, none of them fit well with what I needed.
114By looking at the features and problems of other libraries, I designed the
115CommandLine library to have the following features:</p>
Chris Lattner209c7f42001-07-23 23:03:12 +0000116
117<ol>
Chris Lattnerae853632002-07-25 19:27:01 +0000118<li>Speed: The CommandLine library is very quick and uses little resources. The
119parsing time of the library is directly proportional to the number of arguments
120parsed, not the the number of options recognized. Additionally, command line
Chris Lattneredf351f2003-06-21 21:45:56 +0000121argument values are captured transparently into user defined global variables,
122which can be accessed like any other variable (and with the same
Misha Brukman9718e962003-10-24 19:59:21 +0000123performance).</li>
Chris Lattner209c7f42001-07-23 23:03:12 +0000124
Chris Lattnerae853632002-07-25 19:27:01 +0000125<li>Type Safe: As a user of CommandLine, you don't have to worry about
126remembering the type of arguments that you want (is it an int? a string? a
127bool? an enum?) and keep casting it around. Not only does this help prevent
Misha Brukman9718e962003-10-24 19:59:21 +0000128error prone constructs, it also leads to dramatically cleaner source code.</li>
Chris Lattner209c7f42001-07-23 23:03:12 +0000129
Chris Lattnerae853632002-07-25 19:27:01 +0000130<li>No subclasses required: To use CommandLine, you instantiate variables that
131correspond to the arguments that you would like to capture, you don't subclass a
Misha Brukman9718e962003-10-24 19:59:21 +0000132parser. This means that you don't have to write <b>any</b> boilerplate
133code.</li>
Chris Lattner209c7f42001-07-23 23:03:12 +0000134
Chris Lattnerae853632002-07-25 19:27:01 +0000135<li>Globally accessible: Libraries can specify command line arguments that are
136automatically enabled in any tool that links to the library. This is possible
137because the application doesn't have to keep a "list" of arguments to pass to
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000138the parser. This also makes supporting <a href="#dynamicopts">dynamically
Misha Brukman9718e962003-10-24 19:59:21 +0000139loaded options</a> trivial.</li>
Chris Lattner209c7f42001-07-23 23:03:12 +0000140
Chris Lattnerc1ae40c2002-08-07 18:27:04 +0000141<li>Cleaner: CommandLine supports enum and other types directly, meaning that
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000142there is less error and more security built into the library. You don't have to
143worry about whether your integral command line argument accidentally got
Misha Brukman9718e962003-10-24 19:59:21 +0000144assigned a value that is not valid for your enum type.</li>
Chris Lattner209c7f42001-07-23 23:03:12 +0000145
Chris Lattnerae853632002-07-25 19:27:01 +0000146<li>Powerful: The CommandLine library supports many different types of
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000147arguments, from simple <a href="#boolparser">boolean flags</a> to <a
148href="#cl::opt">scalars arguments</a> (<a href="#stringparser">strings</a>, <a
149href="#intparser">integers</a>, <a href="#genericparser">enums</a>, <a
150href="#doubleparser">doubles</a>), to <a href="#cl::list">lists of
Misha Brukman9718e962003-10-24 19:59:21 +0000151arguments</a>. This is possible because CommandLine is...</li>
Chris Lattner209c7f42001-07-23 23:03:12 +0000152
Chris Lattnerae853632002-07-25 19:27:01 +0000153<li>Extensible: It is very simple to add a new argument type to CommandLine.
154Simply specify the parser that you want to use with the command line option when
Misha Brukman9718e962003-10-24 19:59:21 +0000155you declare it. <a href="#customparser">Custom parsers</a> are no problem.</li>
Chris Lattner209c7f42001-07-23 23:03:12 +0000156
Chris Lattnerae853632002-07-25 19:27:01 +0000157<li>Labor Saving: The CommandLine library cuts down on the amount of grunt work
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000158that you, the user, have to do. For example, it automatically provides a
159<tt>--help</tt> option that shows the available command line options for your
Misha Brukman9718e962003-10-24 19:59:21 +0000160tool. Additionally, it does most of the basic correctness checking for
161you.</li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000162
163<li>Capable: The CommandLine library can handle lots of different forms of
164options often found in real programs. For example, <a
165href="#positional">positional</a> arguments, <tt>ls</tt> style <a
166href="#cl::Grouping">grouping</a> options (to allow processing '<tt>ls
167-lad</tt>' naturally), <tt>ld</tt> style <a href="#cl::Prefix">prefix</a>
168options (to parse '<tt>-lmalloc -L/usr/lib</tt>'), and <a
Misha Brukman9718e962003-10-24 19:59:21 +0000169href="#cl::ConsumeAfter">interpreter style options</a>.</li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000170
Chris Lattner209c7f42001-07-23 23:03:12 +0000171</ol>
172
Misha Brukman9718e962003-10-24 19:59:21 +0000173<p>This document will hopefully let you jump in and start using CommandLine in
174your utility quickly and painlessly. Additionally it should be a simple
175reference manual to figure out how stuff works. If it is failing in some area
176(or you want an extension to the library), nag the author, <a
177href="mailto:sabre@nondot.org">Chris Lattner</a>.</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000178
Misha Brukman9718e962003-10-24 19:59:21 +0000179</div>
Chris Lattner209c7f42001-07-23 23:03:12 +0000180
181<!-- *********************************************************************** -->
Misha Brukman9718e962003-10-24 19:59:21 +0000182<div class="doc_section">
183 <a name="quickstart">Quick Start Guide</a>
184</div>
Chris Lattner209c7f42001-07-23 23:03:12 +0000185<!-- *********************************************************************** -->
186
Misha Brukman9718e962003-10-24 19:59:21 +0000187<div class="doc_text">
188
189<p>This section of the manual runs through a simple CommandLine'ification of a
Chris Lattnerae853632002-07-25 19:27:01 +0000190basic compiler tool. This is intended to show you how to jump into using the
191CommandLine library in your own program, and show you some of the cool things it
Misha Brukman9718e962003-10-24 19:59:21 +0000192can do.</p>
Chris Lattner209c7f42001-07-23 23:03:12 +0000193
Misha Brukman9718e962003-10-24 19:59:21 +0000194<p>To start out, you need to include the CommandLine header file into your
195program:</p>
Chris Lattner209c7f42001-07-23 23:03:12 +0000196
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000197<div class="doc_code"><pre>
Andrew Lenharth94f3d1a2005-11-14 19:32:05 +0000198 #include "llvm/Support/CommandLine.h"
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000199</pre></div>
Chris Lattner209c7f42001-07-23 23:03:12 +0000200
Misha Brukman9718e962003-10-24 19:59:21 +0000201<p>Additionally, you need to add this as the first line of your main
202program:</p>
Chris Lattner209c7f42001-07-23 23:03:12 +0000203
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000204<div class="doc_code"><pre>
Chris Lattner209c7f42001-07-23 23:03:12 +0000205int main(int argc, char **argv) {
Chris Lattnerc1ae40c2002-08-07 18:27:04 +0000206 <a href="#cl::ParseCommandLineOptions">cl::ParseCommandLineOptions</a>(argc, argv);
Chris Lattner209c7f42001-07-23 23:03:12 +0000207 ...
208}
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000209</pre></div>
Chris Lattner209c7f42001-07-23 23:03:12 +0000210
Misha Brukman9718e962003-10-24 19:59:21 +0000211<p>... which actually parses the arguments and fills in the variable
212declarations.</p>
Chris Lattner209c7f42001-07-23 23:03:12 +0000213
Misha Brukman9718e962003-10-24 19:59:21 +0000214<p>Now that you are ready to support command line arguments, we need to tell the
Chris Lattnerae853632002-07-25 19:27:01 +0000215system which ones we want, and what type of argument they are. The CommandLine
Chris Lattneredf351f2003-06-21 21:45:56 +0000216library uses a declarative syntax to model command line arguments with the
217global variable declarations that capture the parsed values. This means that
218for every command line option that you would like to support, there should be a
219global variable declaration to capture the result. For example, in a compiler,
220we would like to support the unix standard '<tt>-o &lt;filename&gt;</tt>' option
221to specify where to put the output. With the CommandLine library, this is
Misha Brukman9718e962003-10-24 19:59:21 +0000222represented like this:</p>
Chris Lattner209c7f42001-07-23 23:03:12 +0000223
Misha Brukmanc53aefb2004-05-12 18:42:35 +0000224<a name="value_desc_example"></a>
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000225<div class="doc_code"><pre>
Misha Brukmanc53aefb2004-05-12 18:42:35 +0000226<a href="#cl::opt">cl::opt</a>&lt;string&gt; OutputFilename("<i>o</i>", <a href="#cl::desc">cl::desc</a>("<i>Specify output filename</i>"), <a href="#cl::value_desc">cl::value_desc</a>("<i>filename</i>"));
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000227</pre></div>
Chris Lattner209c7f42001-07-23 23:03:12 +0000228
Misha Brukman9718e962003-10-24 19:59:21 +0000229<p>This declares a global variable "<tt>OutputFilename</tt>" that is used to
Chris Lattneredf351f2003-06-21 21:45:56 +0000230capture the result of the "<tt>o</tt>" argument (first parameter). We specify
231that this is a simple scalar option by using the "<tt><a
232href="#cl::opt">cl::opt</a></tt>" template (as opposed to the <a
233href="#list">"<tt>cl::list</tt> template</a>), and tell the CommandLine library
Misha Brukman9718e962003-10-24 19:59:21 +0000234that the data type that we are parsing is a string.</p>
Chris Lattnerae853632002-07-25 19:27:01 +0000235
Misha Brukman9718e962003-10-24 19:59:21 +0000236<p>The second and third parameters (which are optional) are used to specify what
237to output for the "<tt>--help</tt>" option. In this case, we get a line that
238looks like this:</p>
Chris Lattner209c7f42001-07-23 23:03:12 +0000239
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000240<div class="doc_code"><pre>
Chris Lattnerae853632002-07-25 19:27:01 +0000241USAGE: compiler [options]
Chris Lattner209c7f42001-07-23 23:03:12 +0000242
Chris Lattnerae853632002-07-25 19:27:01 +0000243OPTIONS:
244 -help - display available options (--help-hidden for more)
Chris Lattnerc1ae40c2002-08-07 18:27:04 +0000245 <b>-o &lt;filename&gt; - Specify output filename</b>
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000246</pre></div>
Chris Lattnerae853632002-07-25 19:27:01 +0000247
Misha Brukman9718e962003-10-24 19:59:21 +0000248<p>Because we specified that the command line option should parse using the
Chris Lattnerae853632002-07-25 19:27:01 +0000249<tt>string</tt> data type, the variable declared is automatically usable as a
250real string in all contexts that a normal C++ string object may be used. For
Misha Brukman9718e962003-10-24 19:59:21 +0000251example:</p>
Chris Lattner209c7f42001-07-23 23:03:12 +0000252
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000253<div class="doc_code"><pre>
Chris Lattner209c7f42001-07-23 23:03:12 +0000254 ...
255 ofstream Output(OutputFilename.c_str());
256 if (Out.good()) ...
257 ...
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000258</pre></div>
Chris Lattner209c7f42001-07-23 23:03:12 +0000259
Misha Brukman9718e962003-10-24 19:59:21 +0000260<p>There are many different options that you can use to customize the command
261line option handling library, but the above example shows the general interface
262to these options. The options can be specified in any order, and are specified
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000263with helper functions like <a href="#cl::desc"><tt>cl::desc(...)</tt></a>, so
Chris Lattnerc1ae40c2002-08-07 18:27:04 +0000264there are no positional dependencies to remember. The available options are
Misha Brukman9718e962003-10-24 19:59:21 +0000265discussed in detail in the <a href="#referenceguide">Reference Guide</a>.</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000266
Misha Brukman9718e962003-10-24 19:59:21 +0000267<p>Continuing the example, we would like to have our compiler take an input
Chris Lattnerae853632002-07-25 19:27:01 +0000268filename as well as an output filename, but we do not want the input filename to
269be specified with a hyphen (ie, not <tt>-filename.c</tt>). To support this
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000270style of argument, the CommandLine library allows for <a
271href="#positional">positional</a> arguments to be specified for the program.
272These positional arguments are filled with command line parameters that are not
Misha Brukman9718e962003-10-24 19:59:21 +0000273in option form. We use this feature like this:</p>
Chris Lattner209c7f42001-07-23 23:03:12 +0000274
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000275<div class="doc_code"><pre>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000276<a href="#cl::opt">cl::opt</a>&lt;string&gt; InputFilename(<a href="#cl::Positional">cl::Positional</a>, <a href="#cl::desc">cl::desc</a>("<i>&lt;input file&gt;</i>"), <a href="#cl::init">cl::init</a>("<i>-</i>"));
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000277</pre></div>
Chris Lattner209c7f42001-07-23 23:03:12 +0000278
Misha Brukman9718e962003-10-24 19:59:21 +0000279<p>This declaration indicates that the first positional argument should be
280treated as the input filename. Here we use the <tt><a
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000281href="#cl::init">cl::init</a></tt> option to specify an initial value for the
282command line option, which is used if the option is not specified (if you do not
283specify a <tt><a href="#cl::init">cl::init</a></tt> modifier for an option, then
284the default constructor for the data type is used to initialize the value).
Chris Lattnerae853632002-07-25 19:27:01 +0000285Command line options default to being optional, so if we would like to require
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000286that the user always specify an input filename, we would add the <tt><a
287href="#cl::Required">cl::Required</a></tt> flag, and we could eliminate the
Misha Brukman9718e962003-10-24 19:59:21 +0000288<tt><a href="#cl::init">cl::init</a></tt> modifier, like this:</p>
Chris Lattner209c7f42001-07-23 23:03:12 +0000289
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000290<div class="doc_code"><pre>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000291<a href="#cl::opt">cl::opt</a>&lt;string&gt; InputFilename(<a href="#cl::Positional">cl::Positional</a>, <a href="#cl::desc">cl::desc</a>("<i>&lt;input file&gt;</i>"), <b><a href="#cl::Required">cl::Required</a></b>);
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000292</pre></div>
Chris Lattner209c7f42001-07-23 23:03:12 +0000293
Misha Brukman9718e962003-10-24 19:59:21 +0000294<p>Again, the CommandLine library does not require the options to be specified
295in any particular order, so the above declaration is equivalent to:</p>
Chris Lattnerae853632002-07-25 19:27:01 +0000296
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000297<div class="doc_code"><pre>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000298<a href="#cl::opt">cl::opt</a>&lt;string&gt; InputFilename(<a href="#cl::Positional">cl::Positional</a>, <a href="#cl::Required">cl::Required</a>, <a href="#cl::desc">cl::desc</a>("<i>&lt;input file&gt;</i>"));
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000299</pre></div>
Chris Lattnerae853632002-07-25 19:27:01 +0000300
Misha Brukman9718e962003-10-24 19:59:21 +0000301<p>By simply adding the <tt><a href="#cl::Required">cl::Required</a></tt> flag,
302the CommandLine library will automatically issue an error if the argument is not
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000303specified, which shifts all of the command line option verification code out of
304your application into the library. This is just one example of how using flags
305can alter the default behaviour of the library, on a per-option basis. By
306adding one of the declarations above, the <tt>--help</tt> option synopsis is now
Misha Brukman9718e962003-10-24 19:59:21 +0000307extended to:</p>
Chris Lattnerae853632002-07-25 19:27:01 +0000308
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000309<div class="doc_code"><pre>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +0000310USAGE: compiler [options] <b>&lt;input file&gt;</b>
Chris Lattnerae853632002-07-25 19:27:01 +0000311
312OPTIONS:
313 -help - display available options (--help-hidden for more)
314 -o &lt;filename&gt; - Specify output filename
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000315</pre></div>
Chris Lattnerae853632002-07-25 19:27:01 +0000316
Misha Brukman9718e962003-10-24 19:59:21 +0000317<p>... indicating that an input filename is expected.</p>
Chris Lattnerae853632002-07-25 19:27:01 +0000318
Misha Brukman9718e962003-10-24 19:59:21 +0000319</div>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +0000320
Chris Lattner209c7f42001-07-23 23:03:12 +0000321<!-- ======================================================================= -->
Misha Brukman9718e962003-10-24 19:59:21 +0000322<div class="doc_subsection">
323 <a name="bool">Boolean Arguments</a>
324</div>
Chris Lattner209c7f42001-07-23 23:03:12 +0000325
Misha Brukman9718e962003-10-24 19:59:21 +0000326<div class="doc_text">
327
328<p>In addition to input and output filenames, we would like the compiler example
329to support three boolean flags: "<tt>-f</tt>" to force overwriting of the output
Chris Lattnerae853632002-07-25 19:27:01 +0000330file, "<tt>--quiet</tt>" to enable quiet mode, and "<tt>-q</tt>" for backwards
331compatibility with some of our users. We can support these by declaring options
Misha Brukman9718e962003-10-24 19:59:21 +0000332of boolean type like this:</p>
Chris Lattner209c7f42001-07-23 23:03:12 +0000333
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000334<div class="doc_code"><pre>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000335<a href="#cl::opt">cl::opt</a>&lt;bool&gt; Force ("<i>f</i>", <a href="#cl::desc">cl::desc</a>("<i>Overwrite output files</i>"));
336<a href="#cl::opt">cl::opt</a>&lt;bool&gt; Quiet ("<i>quiet</i>", <a href="#cl::desc">cl::desc</a>("<i>Don't print informational messages</i>"));
337<a href="#cl::opt">cl::opt</a>&lt;bool&gt; Quiet2("<i>q</i>", <a href="#cl::desc">cl::desc</a>("<i>Don't print informational messages</i>"), <a href="#cl::Hidden">cl::Hidden</a>);
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000338</pre></div>
Chris Lattner209c7f42001-07-23 23:03:12 +0000339
Misha Brukman9718e962003-10-24 19:59:21 +0000340<p>This does what you would expect: it declares three boolean variables
Chris Lattnerae853632002-07-25 19:27:01 +0000341("<tt>Force</tt>", "<tt>Quiet</tt>", and "<tt>Quiet2</tt>") to recognize these
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000342options. Note that the "<tt>-q</tt>" option is specified with the "<a
343href="#cl::Hidden"><tt>cl::Hidden</tt></a>" flag. This modifier prevents it
344from being shown by the standard "<tt>--help</tt>" output (note that it is still
Misha Brukman9718e962003-10-24 19:59:21 +0000345shown in the "<tt>--help-hidden</tt>" output).</p>
Chris Lattnerae853632002-07-25 19:27:01 +0000346
Misha Brukman9718e962003-10-24 19:59:21 +0000347<p>The CommandLine library uses a <a href="#builtinparsers">different parser</a>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +0000348for different data types. For example, in the string case, the argument passed
349to the option is copied literally into the content of the string variable... we
350obviously cannot do that in the boolean case, however, so we must use a smarter
351parser. In the case of the boolean parser, it allows no options (in which case
352it assigns the value of true to the variable), or it allows the values
353"<tt>true</tt>" or "<tt>false</tt>" to be specified, allowing any of the
Misha Brukman9718e962003-10-24 19:59:21 +0000354following inputs:</p>
Chris Lattner209c7f42001-07-23 23:03:12 +0000355
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000356<div class="doc_code"><pre>
Chris Lattnerae853632002-07-25 19:27:01 +0000357 compiler -f # No value, 'Force' == true
358 compiler -f=true # Value specified, 'Force' == true
359 compiler -f=TRUE # Value specified, 'Force' == true
360 compiler -f=FALSE # Value specified, 'Force' == false
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000361</pre></div>
Chris Lattnerae853632002-07-25 19:27:01 +0000362
Misha Brukman9718e962003-10-24 19:59:21 +0000363<p>... you get the idea. The <a href="#boolparser">bool parser</a> just turns
364the string values into boolean values, and rejects things like '<tt>compiler
Chris Lattnerc1ae40c2002-08-07 18:27:04 +0000365-f=foo</tt>'. Similarly, the <a href="#doubleparser">float</a>, <a
366href="#doubleparser">double</a>, and <a href="#intparser">int</a> parsers work
367like you would expect, using the '<tt>strtol</tt>' and '<tt>strtod</tt>' C
Misha Brukman9718e962003-10-24 19:59:21 +0000368library calls to parse the string value into the specified data type.</p>
Chris Lattnerae853632002-07-25 19:27:01 +0000369
Misha Brukman9718e962003-10-24 19:59:21 +0000370<p>With the declarations above, "<tt>compiler --help</tt>" emits this:</p>
Chris Lattnerae853632002-07-25 19:27:01 +0000371
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000372<div class="doc_code"><pre>
Chris Lattnerae853632002-07-25 19:27:01 +0000373USAGE: compiler [options] &lt;input file&gt;
Chris Lattner209c7f42001-07-23 23:03:12 +0000374
375OPTIONS:
Chris Lattnerc1ae40c2002-08-07 18:27:04 +0000376 <b>-f - Overwrite output files</b>
Chris Lattner209c7f42001-07-23 23:03:12 +0000377 -o - Override output filename
Chris Lattnerc1ae40c2002-08-07 18:27:04 +0000378 <b>-quiet - Don't print informational messages</b>
Chris Lattner209c7f42001-07-23 23:03:12 +0000379 -help - display available options (--help-hidden for more)
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000380</pre></div>
Chris Lattner209c7f42001-07-23 23:03:12 +0000381
Misha Brukman9718e962003-10-24 19:59:21 +0000382<p>and "<tt>opt --help-hidden</tt>" prints this:</p>
Chris Lattner209c7f42001-07-23 23:03:12 +0000383
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000384<div class="doc_code"><pre>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +0000385USAGE: compiler [options] &lt;input file&gt;
Chris Lattner209c7f42001-07-23 23:03:12 +0000386
387OPTIONS:
388 -f - Overwrite output files
389 -o - Override output filename
Chris Lattnerc1ae40c2002-08-07 18:27:04 +0000390 <b>-q - Don't print informational messages</b>
Chris Lattner209c7f42001-07-23 23:03:12 +0000391 -quiet - Don't print informational messages
392 -help - display available options (--help-hidden for more)
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000393</pre></div>
Chris Lattner209c7f42001-07-23 23:03:12 +0000394
Misha Brukman9718e962003-10-24 19:59:21 +0000395<p>This brief example has shown you how to use the '<tt><a
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000396href="#cl::opt">cl::opt</a></tt>' class to parse simple scalar command line
397arguments. In addition to simple scalar arguments, the CommandLine library also
398provides primitives to support CommandLine option <a href="#alias">aliases</a>,
Misha Brukman9718e962003-10-24 19:59:21 +0000399and <a href="#list">lists</a> of options.</p>
Chris Lattner209c7f42001-07-23 23:03:12 +0000400
Misha Brukman9718e962003-10-24 19:59:21 +0000401</div>
Chris Lattner209c7f42001-07-23 23:03:12 +0000402
403<!-- ======================================================================= -->
Misha Brukman9718e962003-10-24 19:59:21 +0000404<div class="doc_subsection">
405 <a name="alias">Argument Aliases</a>
406</div>
Chris Lattner209c7f42001-07-23 23:03:12 +0000407
Misha Brukman9718e962003-10-24 19:59:21 +0000408<div class="doc_text">
409
410<p>So far, the example works well, except for the fact that we need to check the
411quiet condition like this now:</p>
Chris Lattner209c7f42001-07-23 23:03:12 +0000412
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000413<div class="doc_code"><pre>
Chris Lattner209c7f42001-07-23 23:03:12 +0000414...
415 if (!Quiet &amp;&amp; !Quiet2) printInformationalMessage(...);
416...
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000417</pre></div>
Chris Lattner209c7f42001-07-23 23:03:12 +0000418
Misha Brukman9718e962003-10-24 19:59:21 +0000419<p>... which is a real pain! Instead of defining two values for the same
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000420condition, we can use the "<tt><a href="#cl::alias">cl::alias</a></tt>" class to make the "<tt>-q</tt>"
Chris Lattnerae853632002-07-25 19:27:01 +0000421option an <b>alias</b> for the "<tt>-quiet</tt>" option, instead of providing
Misha Brukman9718e962003-10-24 19:59:21 +0000422a value itself:</p>
Chris Lattner209c7f42001-07-23 23:03:12 +0000423
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000424<div class="doc_code"><pre>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000425<a href="#cl::opt">cl::opt</a>&lt;bool&gt; Force ("<i>f</i>", <a href="#cl::desc">cl::desc</a>("<i>Overwrite output files</i>"));
426<a href="#cl::opt">cl::opt</a>&lt;bool&gt; Quiet ("<i>quiet</i>", <a href="#cl::desc">cl::desc</a>("<i>Don't print informational messages</i>"));
427<a href="#cl::alias">cl::alias</a> QuietA("<i>q</i>", <a href="#cl::desc">cl::desc</a>("<i>Alias for -quiet</i>"), <a href="#cl::aliasopt">cl::aliasopt</a>(Quiet));
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000428</pre></div>
Chris Lattner209c7f42001-07-23 23:03:12 +0000429
Misha Brukman9718e962003-10-24 19:59:21 +0000430<p>The third line (which is the only one we modified from above) defines a
Chris Lattnerae853632002-07-25 19:27:01 +0000431"<tt>-q</tt> alias that updates the "<tt>Quiet</tt>" variable (as specified by
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000432the <tt><a href="#cl::aliasopt">cl::aliasopt</a></tt> modifier) whenever it is
433specified. Because aliases do not hold state, the only thing the program has to
434query is the <tt>Quiet</tt> variable now. Another nice feature of aliases is
435that they automatically hide themselves from the <tt>-help</tt> output
436(although, again, they are still visible in the <tt>--help-hidden
Misha Brukman9718e962003-10-24 19:59:21 +0000437output</tt>).</p>
Chris Lattnerae853632002-07-25 19:27:01 +0000438
Misha Brukman9718e962003-10-24 19:59:21 +0000439<p>Now the application code can simply use:</p>
Chris Lattner209c7f42001-07-23 23:03:12 +0000440
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000441<div class="doc_code"><pre>
Chris Lattner209c7f42001-07-23 23:03:12 +0000442...
443 if (!Quiet) printInformationalMessage(...);
444...
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000445</pre></div>
Chris Lattner209c7f42001-07-23 23:03:12 +0000446
Misha Brukman9718e962003-10-24 19:59:21 +0000447<p>... which is much nicer! The "<tt><a href="#cl::alias">cl::alias</a></tt>"
448can be used to specify an alternative name for any variable type, and has many
449uses.</p>
Chris Lattnerae853632002-07-25 19:27:01 +0000450
Misha Brukman9718e962003-10-24 19:59:21 +0000451</div>
Chris Lattner209c7f42001-07-23 23:03:12 +0000452
453<!-- ======================================================================= -->
Misha Brukman9718e962003-10-24 19:59:21 +0000454<div class="doc_subsection">
455 <a name="onealternative">Selecting an alternative from a set of
456 possibilities</a>
457</div>
Chris Lattner209c7f42001-07-23 23:03:12 +0000458
Misha Brukman9718e962003-10-24 19:59:21 +0000459<div class="doc_text">
460
461<p>So far, we have seen how the CommandLine library handles builtin types like
Chris Lattnerae853632002-07-25 19:27:01 +0000462<tt>std::string</tt>, <tt>bool</tt> and <tt>int</tt>, but how does it handle
Misha Brukman9718e962003-10-24 19:59:21 +0000463things it doesn't know about, like enums or '<tt>int*</tt>'s?</p>
Chris Lattner209c7f42001-07-23 23:03:12 +0000464
Misha Brukman9718e962003-10-24 19:59:21 +0000465<p>The answer is that it uses a table driven generic parser (unless you specify
Chris Lattnerae853632002-07-25 19:27:01 +0000466your own parser, as described in the <a href="#extensionguide">Extension
Reid Spencerd8473372004-08-10 16:38:18 +0000467Guide</a>). This parser maps literal strings to whatever type is required, and
Misha Brukman9718e962003-10-24 19:59:21 +0000468requires you to tell it what this mapping should be.</p>
Chris Lattnerae853632002-07-25 19:27:01 +0000469
Reid Spencerd8473372004-08-10 16:38:18 +0000470<p>Lets say that we would like to add four optimization levels to our
Misha Brukman9718e962003-10-24 19:59:21 +0000471optimizer, using the standard flags "<tt>-g</tt>", "<tt>-O0</tt>",
472"<tt>-O1</tt>", and "<tt>-O2</tt>". We could easily implement this with boolean
473options like above, but there are several problems with this strategy:</p>
Chris Lattner209c7f42001-07-23 23:03:12 +0000474
475<ol>
Chris Lattnerae853632002-07-25 19:27:01 +0000476<li>A user could specify more than one of the options at a time, for example,
477"<tt>opt -O3 -O2</tt>". The CommandLine library would not be able to catch this
Misha Brukman9718e962003-10-24 19:59:21 +0000478erroneous input for us.</li>
Chris Lattnerae853632002-07-25 19:27:01 +0000479
Misha Brukman9718e962003-10-24 19:59:21 +0000480<li>We would have to test 4 different variables to see which ones are set.</li>
Chris Lattnerae853632002-07-25 19:27:01 +0000481
482<li>This doesn't map to the numeric levels that we want... so we cannot easily
Misha Brukman9718e962003-10-24 19:59:21 +0000483see if some level &gt;= "<tt>-O1</tt>" is enabled.</li>
Chris Lattnerae853632002-07-25 19:27:01 +0000484
Misha Brukman9718e962003-10-24 19:59:21 +0000485</ol>
Chris Lattner209c7f42001-07-23 23:03:12 +0000486
Misha Brukman9718e962003-10-24 19:59:21 +0000487<p>To cope with these problems, we can use an enum value, and have the
488CommandLine library fill it in with the appropriate level directly, which is
489used like this:</p>
Chris Lattner209c7f42001-07-23 23:03:12 +0000490
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000491<div class="doc_code"><pre>
Chris Lattner209c7f42001-07-23 23:03:12 +0000492enum OptLevel {
493 g, O1, O2, O3
494};
495
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000496<a href="#cl::opt">cl::opt</a>&lt;OptLevel&gt; OptimizationLevel(<a href="#cl::desc">cl::desc</a>("<i>Choose optimization level:</i>"),
497 <a href="#cl::values">cl::values</a>(
Chris Lattnerae853632002-07-25 19:27:01 +0000498 clEnumVal(g , "<i>No optimizations, enable debugging</i>"),
499 clEnumVal(O1, "<i>Enable trivial optimizations</i>"),
500 clEnumVal(O2, "<i>Enable default optimizations</i>"),
501 clEnumVal(O3, "<i>Enable expensive optimizations</i>"),
Chris Lattnerb406ead2004-07-16 00:10:54 +0000502 clEnumValEnd));
Chris Lattner209c7f42001-07-23 23:03:12 +0000503
504...
Chris Lattnerae853632002-07-25 19:27:01 +0000505 if (OptimizationLevel &gt;= O2) doPartialRedundancyElimination(...);
Chris Lattner209c7f42001-07-23 23:03:12 +0000506...
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000507</pre></div>
Chris Lattner209c7f42001-07-23 23:03:12 +0000508
Misha Brukman9718e962003-10-24 19:59:21 +0000509<p>This declaration defines a variable "<tt>OptimizationLevel</tt>" of the
Chris Lattnerae853632002-07-25 19:27:01 +0000510"<tt>OptLevel</tt>" enum type. This variable can be assigned any of the values
511that are listed in the declaration (Note that the declaration list must be
Chris Lattnerb406ead2004-07-16 00:10:54 +0000512terminated with the "<tt>clEnumValEnd</tt>" argument!). The CommandLine
513library enforces
Chris Lattnerae853632002-07-25 19:27:01 +0000514that the user can only specify one of the options, and it ensure that only valid
515enum values can be specified. The "<tt>clEnumVal</tt>" macros ensure that the
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000516command line arguments matched the enum values. With this option added, our
Misha Brukman9718e962003-10-24 19:59:21 +0000517help output now is:</p>
Chris Lattner209c7f42001-07-23 23:03:12 +0000518
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000519<div class="doc_code"><pre>
Chris Lattnerae853632002-07-25 19:27:01 +0000520USAGE: compiler [options] &lt;input file&gt;
Chris Lattner209c7f42001-07-23 23:03:12 +0000521
Chris Lattnerae853632002-07-25 19:27:01 +0000522OPTIONS:
Chris Lattnerc1ae40c2002-08-07 18:27:04 +0000523 <b>Choose optimization level:
Chris Lattnerae853632002-07-25 19:27:01 +0000524 -g - No optimizations, enable debugging
525 -O1 - Enable trivial optimizations
526 -O2 - Enable default optimizations
Chris Lattnerc1ae40c2002-08-07 18:27:04 +0000527 -O3 - Enable expensive optimizations</b>
Chris Lattnerae853632002-07-25 19:27:01 +0000528 -f - Overwrite output files
529 -help - display available options (--help-hidden for more)
530 -o &lt;filename&gt; - Specify output filename
531 -quiet - Don't print informational messages
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000532</pre></div>
Chris Lattner209c7f42001-07-23 23:03:12 +0000533
Misha Brukman9718e962003-10-24 19:59:21 +0000534<p>In this case, it is sort of awkward that flag names correspond directly to
535enum names, because we probably don't want a enum definition named "<tt>g</tt>"
536in our program. Because of this, we can alternatively write this example like
537this:</p>
Chris Lattner209c7f42001-07-23 23:03:12 +0000538
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000539<div class="doc_code"><pre>
Chris Lattner209c7f42001-07-23 23:03:12 +0000540enum OptLevel {
541 Debug, O1, O2, O3
542};
543
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000544<a href="#cl::opt">cl::opt</a>&lt;OptLevel&gt; OptimizationLevel(<a href="#cl::desc">cl::desc</a>("<i>Choose optimization level:</i>"),
545 <a href="#cl::values">cl::values</a>(
Chris Lattnerae853632002-07-25 19:27:01 +0000546 clEnumValN(Debug, "g", "<i>No optimizations, enable debugging</i>"),
547 clEnumVal(O1 , "<i>Enable trivial optimizations</i>"),
548 clEnumVal(O2 , "<i>Enable default optimizations</i>"),
549 clEnumVal(O3 , "<i>Enable expensive optimizations</i>"),
Chris Lattnerb406ead2004-07-16 00:10:54 +0000550 clEnumValEnd));
Chris Lattner209c7f42001-07-23 23:03:12 +0000551
552...
553 if (OptimizationLevel == Debug) outputDebugInfo(...);
554...
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000555</pre></div>
Chris Lattner209c7f42001-07-23 23:03:12 +0000556
Misha Brukman9718e962003-10-24 19:59:21 +0000557<p>By using the "<tt>clEnumValN</tt>" macro instead of "<tt>clEnumVal</tt>", we
558can directly specify the name that the flag should get. In general a direct
559mapping is nice, but sometimes you can't or don't want to preserve the mapping,
560which is when you would use it.</p>
Chris Lattnerae853632002-07-25 19:27:01 +0000561
Misha Brukman9718e962003-10-24 19:59:21 +0000562</div>
Chris Lattner209c7f42001-07-23 23:03:12 +0000563
564<!-- ======================================================================= -->
Misha Brukman9718e962003-10-24 19:59:21 +0000565<div class="doc_subsection">
566 <a name="namedalternatives">Named Alternatives</a>
567</div>
Chris Lattner209c7f42001-07-23 23:03:12 +0000568
Misha Brukman9718e962003-10-24 19:59:21 +0000569<div class="doc_text">
570
571<p>Another useful argument form is a named alternative style. We shall use this
Chris Lattnerae853632002-07-25 19:27:01 +0000572style in our compiler to specify different debug levels that can be used.
573Instead of each debug level being its own switch, we want to support the
574following options, of which only one can be specified at a time:
575"<tt>--debug-level=none</tt>", "<tt>--debug-level=quick</tt>",
576"<tt>--debug-level=detailed</tt>". To do this, we use the exact same format as
577our optimization level flags, but we also specify an option name. For this
Misha Brukman9718e962003-10-24 19:59:21 +0000578case, the code looks like this:</p>
Chris Lattner209c7f42001-07-23 23:03:12 +0000579
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000580<div class="doc_code"><pre>
Chris Lattner209c7f42001-07-23 23:03:12 +0000581enum DebugLev {
582 nodebuginfo, quick, detailed
583};
584
585// Enable Debug Options to be specified on the command line
Chris Lattnerdc844fa2003-06-03 04:40:06 +0000586<a href="#cl::opt">cl::opt</a>&lt;DebugLev&gt; DebugLevel("<i>debug_level</i>", <a href="#cl::desc">cl::desc</a>("<i>Set the debugging level:</i>"),
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000587 <a href="#cl::values">cl::values</a>(
Chris Lattnerae853632002-07-25 19:27:01 +0000588 clEnumValN(nodebuginfo, "none", "<i>disable debug information</i>"),
589 clEnumVal(quick, "<i>enable quick debug information</i>"),
590 clEnumVal(detailed, "<i>enable detailed debug information</i>"),
Chris Lattnerb406ead2004-07-16 00:10:54 +0000591 clEnumValEnd));
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000592</pre></div>
Chris Lattner209c7f42001-07-23 23:03:12 +0000593
Misha Brukman9718e962003-10-24 19:59:21 +0000594<p>This definition defines an enumerated command line variable of type "<tt>enum
Chris Lattnerae853632002-07-25 19:27:01 +0000595DebugLev</tt>", which works exactly the same way as before. The difference here
596is just the interface exposed to the user of your program and the help output by
Misha Brukman9718e962003-10-24 19:59:21 +0000597the "<tt>--help</tt>" option:</p>
Chris Lattner209c7f42001-07-23 23:03:12 +0000598
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000599<div class="doc_code"><pre>
Chris Lattnerae853632002-07-25 19:27:01 +0000600USAGE: compiler [options] &lt;input file&gt;
601
Chris Lattner209c7f42001-07-23 23:03:12 +0000602OPTIONS:
Chris Lattnerae853632002-07-25 19:27:01 +0000603 Choose optimization level:
604 -g - No optimizations, enable debugging
605 -O1 - Enable trivial optimizations
606 -O2 - Enable default optimizations
607 -O3 - Enable expensive optimizations
Chris Lattnerc1ae40c2002-08-07 18:27:04 +0000608 <b>-debug_level - Set the debugging level:
Chris Lattnerae853632002-07-25 19:27:01 +0000609 =none - disable debug information
610 =quick - enable quick debug information
Chris Lattnerc1ae40c2002-08-07 18:27:04 +0000611 =detailed - enable detailed debug information</b>
Chris Lattnerae853632002-07-25 19:27:01 +0000612 -f - Overwrite output files
613 -help - display available options (--help-hidden for more)
614 -o &lt;filename&gt; - Specify output filename
615 -quiet - Don't print informational messages
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000616</pre></div>
Chris Lattner209c7f42001-07-23 23:03:12 +0000617
Misha Brukman9718e962003-10-24 19:59:21 +0000618<p>Again, the only structural difference between the debug level declaration and
John Criswellc24d4822004-11-21 14:34:34 +0000619the optimization level declaration is that the debug level declaration includes
Chris Lattnerae853632002-07-25 19:27:01 +0000620an option name (<tt>"debug_level"</tt>), which automatically changes how the
621library processes the argument. The CommandLine library supports both forms so
Misha Brukman9718e962003-10-24 19:59:21 +0000622that you can choose the form most appropriate for your application.</p>
Chris Lattnerae853632002-07-25 19:27:01 +0000623
Misha Brukman9718e962003-10-24 19:59:21 +0000624</div>
Chris Lattner209c7f42001-07-23 23:03:12 +0000625
626<!-- ======================================================================= -->
Misha Brukman9718e962003-10-24 19:59:21 +0000627<div class="doc_subsection">
628 <a name="list">Parsing a list of options</a>
629</div>
Chris Lattner209c7f42001-07-23 23:03:12 +0000630
Misha Brukman9718e962003-10-24 19:59:21 +0000631<div class="doc_text">
632
633<p>Now that we have the standard run of the mill argument types out of the way,
Chris Lattnerae853632002-07-25 19:27:01 +0000634lets get a little wild and crazy. Lets say that we want our optimizer to accept
635a <b>list</b> of optimizations to perform, allowing duplicates. For example, we
636might want to run: "<tt>compiler -dce -constprop -inline -dce -strip</tt>". In
637this case, the order of the arguments and the number of appearances is very
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000638important. This is what the "<tt><a href="#cl::list">cl::list</a></tt>"
639template is for. First, start by defining an enum of the optimizations that you
Misha Brukman9718e962003-10-24 19:59:21 +0000640would like to perform:</p>
Chris Lattner209c7f42001-07-23 23:03:12 +0000641
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000642<div class="doc_code"><pre>
Chris Lattner209c7f42001-07-23 23:03:12 +0000643enum Opts {
Chris Lattnerae853632002-07-25 19:27:01 +0000644 // 'inline' is a C++ keyword, so name it 'inlining'
Chris Lattner209c7f42001-07-23 23:03:12 +0000645 dce, constprop, inlining, strip
Chris Lattnerae853632002-07-25 19:27:01 +0000646};
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000647</pre></div>
Chris Lattner209c7f42001-07-23 23:03:12 +0000648
Misha Brukman9718e962003-10-24 19:59:21 +0000649<p>Then define your "<tt><a href="#cl::list">cl::list</a></tt>" variable:</p>
Chris Lattner209c7f42001-07-23 23:03:12 +0000650
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000651<div class="doc_code"><pre>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000652<a href="#cl::list">cl::list</a>&lt;Opts&gt; OptimizationList(<a href="#cl::desc">cl::desc</a>("<i>Available Optimizations:</i>"),
653 <a href="#cl::values">cl::values</a>(
Chris Lattnerae853632002-07-25 19:27:01 +0000654 clEnumVal(dce , "<i>Dead Code Elimination</i>"),
Misha Brukman82c89b92003-05-20 21:01:22 +0000655 clEnumVal(constprop , "<i>Constant Propagation</i>"),
Chris Lattnerae853632002-07-25 19:27:01 +0000656 clEnumValN(inlining, "<i>inline</i>", "<i>Procedure Integration</i>"),
657 clEnumVal(strip , "<i>Strip Symbols</i>"),
Chris Lattnerb406ead2004-07-16 00:10:54 +0000658 clEnumValEnd));
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000659</pre></div>
Chris Lattner209c7f42001-07-23 23:03:12 +0000660
Misha Brukman9718e962003-10-24 19:59:21 +0000661<p>This defines a variable that is conceptually of the type
Chris Lattnerae853632002-07-25 19:27:01 +0000662"<tt>std::vector&lt;enum Opts&gt;</tt>". Thus, you can access it with standard
Misha Brukman9718e962003-10-24 19:59:21 +0000663vector methods:</p>
Chris Lattner209c7f42001-07-23 23:03:12 +0000664
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000665<div class="doc_code"><pre>
Chris Lattnerae853632002-07-25 19:27:01 +0000666 for (unsigned i = 0; i != OptimizationList.size(); ++i)
Chris Lattner209c7f42001-07-23 23:03:12 +0000667 switch (OptimizationList[i])
668 ...
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000669</pre></div>
Chris Lattner209c7f42001-07-23 23:03:12 +0000670
Misha Brukman9718e962003-10-24 19:59:21 +0000671<p>... to iterate through the list of options specified.</p>
Chris Lattner209c7f42001-07-23 23:03:12 +0000672
Misha Brukman9718e962003-10-24 19:59:21 +0000673<p>Note that the "<tt><a href="#cl::list">cl::list</a></tt>" template is
674completely general and may be used with any data types or other arguments that
675you can use with the "<tt><a href="#cl::opt">cl::opt</a></tt>" template. One
676especially useful way to use a list is to capture all of the positional
677arguments together if there may be more than one specified. In the case of a
678linker, for example, the linker takes several '<tt>.o</tt>' files, and needs to
679capture them into a list. This is naturally specified as:</p>
Chris Lattner3e5fe172002-04-13 18:35:59 +0000680
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000681<div class="doc_code"><pre>
Chris Lattner3e5fe172002-04-13 18:35:59 +0000682...
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000683<a href="#cl::list">cl::list</a>&lt;std::string&gt; InputFilenames(<a href="#cl::Positional">cl::Positional</a>, <a href="#cl::desc">cl::desc</a>("&lt;Input files&gt;"), <a href="#cl::OneOrMore">cl::OneOrMore</a>);
Chris Lattner3e5fe172002-04-13 18:35:59 +0000684...
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000685</pre></div>
Chris Lattner3e5fe172002-04-13 18:35:59 +0000686
Misha Brukman9718e962003-10-24 19:59:21 +0000687<p>This variable works just like a "<tt>vector&lt;string&gt;</tt>" object. As
Chris Lattnerae853632002-07-25 19:27:01 +0000688such, accessing the list is simple, just like above. In this example, we used
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000689the <tt><a href="#cl::OneOrMore">cl::OneOrMore</a></tt> modifier to inform the
690CommandLine library that it is an error if the user does not specify any
691<tt>.o</tt> files on our command line. Again, this just reduces the amount of
Misha Brukman9718e962003-10-24 19:59:21 +0000692checking we have to do.</p>
Chris Lattner3e5fe172002-04-13 18:35:59 +0000693
Misha Brukman9718e962003-10-24 19:59:21 +0000694</div>
Chris Lattner3e5fe172002-04-13 18:35:59 +0000695
Chris Lattnerc1ae40c2002-08-07 18:27:04 +0000696<!-- ======================================================================= -->
Misha Brukman9718e962003-10-24 19:59:21 +0000697<div class="doc_subsection">
Jim Laskey1d8f6262005-08-25 22:52:43 +0000698 <a name="bits">Collecting options as a set of flags</a>
699</div>
700
701<div class="doc_text">
702
703<p>Instead of collecting sets of options in a list, it is also possible to
Jim Laskey22b7dfa2005-08-26 09:25:54 +0000704gather information for enum values in a <b>bit vector</b>. The represention used by
705the <a href="#bits"><tt>cl::bits</tt></a> class is an <tt>unsigned</tt>
Jim Laskey1d8f6262005-08-25 22:52:43 +0000706integer. An enum value is represented by a 0/1 in the enum's ordinal value bit
707position. 1 indicating that the enum was specified, 0 otherwise. As each
708specified value is parsed, the resulting enum's bit is set in the option's bit
709vector:</p>
710
711<div class="doc_code"><pre>
712 <i>bits</i> |= 1 << (unsigned)<i>enum</i>;
713</pre></div>
714
Jim Laskey26029222005-08-25 23:01:25 +0000715<p>Options that are specified multiple times are redundant. Any instances after
716the first are discarded.</p>
Jim Laskey1d8f6262005-08-25 22:52:43 +0000717
718<p>Reworking the above list example, we could replace <a href="#list">
719<tt>cl::list</tt></a> with <a href="#bits"><tt>cl::bits</tt></a>:</p>
720
721<div class="doc_code"><pre>
722<a href="#cl::bits">cl::bits</a>&lt;Opts&gt; OptimizationBits(<a href="#cl::desc">cl::desc</a>("<i>Available Optimizations:</i>"),
723 <a href="#cl::values">cl::values</a>(
724 clEnumVal(dce , "<i>Dead Code Elimination</i>"),
725 clEnumVal(constprop , "<i>Constant Propagation</i>"),
726 clEnumValN(inlining, "<i>inline</i>", "<i>Procedure Integration</i>"),
727 clEnumVal(strip , "<i>Strip Symbols</i>"),
728 clEnumValEnd));
729</pre></div>
730
731<p>To test to see if <tt>constprop</tt> was specified, we can use the
732<tt>cl:bits::isSet</tt> function:</p>
733
734<div class="doc_code"><pre>
735 if (OptimizationBits.isSet(constprop)) {
736 ...
737 }
738</pre></div>
739
740<p>It's also possible to get the raw bit vector using the
741<tt>cl::bits::getBits</tt> function:</p>
742
743<div class="doc_code"><pre>
Jim Laskey22b7dfa2005-08-26 09:25:54 +0000744 unsigned bits = OptimizationBits.getBits();
Jim Laskey1d8f6262005-08-25 22:52:43 +0000745</pre></div>
746
747<p>Finally, if external storage is used, then the location specified must be of
Jim Laskey22b7dfa2005-08-26 09:25:54 +0000748<b>type</b> <tt>unsigned</tt>. In all other ways a <a
Jim Laskey1d8f6262005-08-25 22:52:43 +0000749href="#bits"><tt>cl::bits</tt></a> option is morally equivalent to a <a
Jim Laskey22b7dfa2005-08-26 09:25:54 +0000750href="#list"> <tt>cl::list</tt></a> option.</p>
Jim Laskey1d8f6262005-08-25 22:52:43 +0000751
752</div>
753
754
755<!-- ======================================================================= -->
756<div class="doc_subsection">
Misha Brukman9718e962003-10-24 19:59:21 +0000757 <a name="description">Adding freeform text to help output</a>
758</div>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +0000759
Misha Brukman9718e962003-10-24 19:59:21 +0000760<div class="doc_text">
761
762<p>As our program grows and becomes more mature, we may decide to put summary
Chris Lattnerc1ae40c2002-08-07 18:27:04 +0000763information about what it does into the help output. The help output is styled
764to look similar to a Unix <tt>man</tt> page, providing concise information about
765a program. Unix <tt>man</tt> pages, however often have a description about what
766the program does. To add this to your CommandLine program, simply pass a third
767argument to the <a
768href="#cl::ParseCommandLineOptions"><tt>cl::ParseCommandLineOptions</tt></a>
769call in main. This additional argument is then printed as the overview
770information for your program, allowing you to include any additional information
Misha Brukman9718e962003-10-24 19:59:21 +0000771that you want. For example:</p>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +0000772
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000773<div class="doc_code"><pre>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +0000774int main(int argc, char **argv) {
775 <a href="#cl::ParseCommandLineOptions">cl::ParseCommandLineOptions</a>(argc, argv, " CommandLine compiler example\n\n"
776 " This program blah blah blah...\n");
777 ...
778}
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000779</pre></div>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +0000780
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000781<p>would yield the help output:</p>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +0000782
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000783<div class="doc_code"><pre>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +0000784<b>OVERVIEW: CommandLine compiler example
785
786 This program blah blah blah...</b>
787
788USAGE: compiler [options] &lt;input file&gt;
789
790OPTIONS:
791 ...
792 -help - display available options (--help-hidden for more)
793 -o &lt;filename&gt; - Specify output filename
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000794</pre></div>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +0000795
Misha Brukman9718e962003-10-24 19:59:21 +0000796</div>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +0000797
798
Chris Lattner209c7f42001-07-23 23:03:12 +0000799<!-- *********************************************************************** -->
Misha Brukman9718e962003-10-24 19:59:21 +0000800<div class="doc_section">
801 <a name="referenceguide">Reference Guide</a>
802</div>
Chris Lattner209c7f42001-07-23 23:03:12 +0000803<!-- *********************************************************************** -->
804
Misha Brukman9718e962003-10-24 19:59:21 +0000805<div class="doc_text">
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000806
Misha Brukman9718e962003-10-24 19:59:21 +0000807<p>Now that you know the basics of how to use the CommandLine library, this
808section will give you the detailed information you need to tune how command line
809options work, as well as information on more "advanced" command line option
810processing capabilities.</p>
811
812</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000813
814<!-- ======================================================================= -->
Misha Brukman9718e962003-10-24 19:59:21 +0000815<div class="doc_subsection">
816 <a name="positional">Positional Arguments</a>
817</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000818
Misha Brukman9718e962003-10-24 19:59:21 +0000819<div class="doc_text">
820
821<p>Positional arguments are those arguments that are not named, and are not
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000822specified with a hyphen. Positional arguments should be used when an option is
823specified by its position alone. For example, the standard Unix <tt>grep</tt>
824tool takes a regular expression argument, and an optional filename to search
825through (which defaults to standard input if a filename is not specified).
Misha Brukman9718e962003-10-24 19:59:21 +0000826Using the CommandLine library, this would be specified as:</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000827
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000828<div class="doc_code"><pre>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000829<a href="#cl::opt">cl::opt</a>&lt;string&gt; Regex (<a href="#cl::Positional">cl::Positional</a>, <a href="#cl::desc">cl::desc</a>("<i>&lt;regular expression&gt;</i>"), <a href="#cl::Required">cl::Required</a>);
830<a href="#cl::opt">cl::opt</a>&lt;string&gt; Filename(<a href="#cl::Positional">cl::Positional</a>, <a href="#cl::desc">cl::desc</a>("<i>&lt;input file&gt;</i>"), <a href="#cl::init">cl::init</a>("<i>-</i>"));
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000831</pre></div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000832
Misha Brukman9718e962003-10-24 19:59:21 +0000833<p>Given these two option declarations, the <tt>--help</tt> output for our grep
834replacement would look like this:</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000835
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000836<div class="doc_code"><pre>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +0000837USAGE: spiffygrep [options] <b>&lt;regular expression&gt; &lt;input file&gt;</b>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000838
839OPTIONS:
840 -help - display available options (--help-hidden for more)
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000841</pre></div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000842
Misha Brukman9718e962003-10-24 19:59:21 +0000843<p>... and the resultant program could be used just like the standard
844<tt>grep</tt> tool.</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000845
Misha Brukman9718e962003-10-24 19:59:21 +0000846<p>Positional arguments are sorted by their order of construction. This means
847that command line options will be ordered according to how they are listed in a
Reid Spencer2c8ab582004-08-13 20:19:14 +0000848.cpp file, but will not have an ordering defined if the positional arguments
Misha Brukman9718e962003-10-24 19:59:21 +0000849are defined in multiple .cpp files. The fix for this problem is simply to
850define all of your positional arguments in one .cpp file.</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000851
Misha Brukman9718e962003-10-24 19:59:21 +0000852</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000853
854
855<!-- _______________________________________________________________________ -->
Misha Brukman9718e962003-10-24 19:59:21 +0000856<div class="doc_subsubsection">
857 <a name="--">Specifying positional options with hyphens</a>
858</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000859
Misha Brukman9718e962003-10-24 19:59:21 +0000860<div class="doc_text">
861
862<p>Sometimes you may want to specify a value to your positional argument that
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000863starts with a hyphen (for example, searching for '<tt>-foo</tt>' in a file). At
864first, you will have trouble doing this, because it will try to find an argument
865named '<tt>-foo</tt>', and will fail (and single quotes will not save you).
Misha Brukman9718e962003-10-24 19:59:21 +0000866Note that the system <tt>grep</tt> has the same problem:</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000867
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000868<div class="doc_code"><pre>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000869 $ spiffygrep '-foo' test.txt
870 Unknown command line argument '-foo'. Try: spiffygrep --help'
871
872 $ grep '-foo' test.txt
873 grep: illegal option -- f
874 grep: illegal option -- o
875 grep: illegal option -- o
876 Usage: grep -hblcnsviw pattern file . . .
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000877</pre></div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000878
Misha Brukman9718e962003-10-24 19:59:21 +0000879<p>The solution for this problem is the same for both your tool and the system
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000880version: use the '<tt>--</tt>' marker. When the user specifies '<tt>--</tt>' on
881the command line, it is telling the program that all options after the
882'<tt>--</tt>' should be treated as positional arguments, not options. Thus, we
Misha Brukman9718e962003-10-24 19:59:21 +0000883can use it like this:</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000884
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000885<div class="doc_code"><pre>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000886 $ spiffygrep -- -foo test.txt
887 ...output...
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000888</pre></div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000889
Misha Brukman9718e962003-10-24 19:59:21 +0000890</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000891
892<!-- _______________________________________________________________________ -->
Misha Brukman9718e962003-10-24 19:59:21 +0000893<div class="doc_subsubsection">
Reid Spencer2c8ab582004-08-13 20:19:14 +0000894 <a name="getPosition">Determining absolute position with getPosition()</a>
895</div>
896<div class="doc_text">
897 <p>Sometimes an option can affect or modify the meaning of another option. For
898 example, consider <tt>gcc</tt>'s <tt>-x LANG</tt> option. This tells
899 <tt>gcc</tt> to ignore the suffix of subsequent positional arguments and force
900 the file to be interpreted as if it contained source code in language
901 <tt>LANG</tt>. In order to handle this properly , you need to know the
902 absolute position of each argument, especially those in lists, so their
903 interaction(s) can be applied correctly. This is also useful for options like
904 <tt>-llibname</tt> which is actually a positional argument that starts with
905 a dash.</p>
906 <p>So, generally, the problem is that you have two <tt>cl::list</tt> variables
907 that interact in some way. To ensure the correct interaction, you can use the
908 <tt>cl::list::getPosition(optnum)</tt> method. This method returns the
909 absolute position (as found on the command line) of the <tt>optnum</tt>
910 item in the <tt>cl::list</tt>.</p>
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000911 <p>The idiom for usage is like this:</p>
912
913 <div class="doc_code"><pre>
Reid Spencer2c8ab582004-08-13 20:19:14 +0000914 static cl::list&lt;std::string&gt; Files(cl::Positional, cl::OneOrMore);
915 static cl::listlt;std::string&gt; Libraries("l", cl::ZeroOrMore);
916
917 int main(int argc, char**argv) {
918 // ...
919 std::vector&lt;std::string&gt;::iterator fileIt = Files.begin();
920 std::vector&lt;std::string&gt;::iterator libIt = Libraries.begin();
921 unsigned libPos = 0, filePos = 0;
922 while ( 1 ) {
923 if ( libIt != Libraries.end() )
924 libPos = Libraries.getPosition( libIt - Libraries.begin() );
925 else
926 libPos = 0;
927 if ( fileIt != Files.end() )
928 filePos = Files.getPosition( fileIt - Files.begin() );
929 else
930 filePos = 0;
931
932 if ( filePos != 0 &amp;&amp; (libPos == 0 || filePos &lt; libPos) ) {
933 // Source File Is next
934 ++fileIt;
935 }
936 else if ( libPos != 0 &amp;&amp; (filePos == 0 || libPos &lt; filePos) ) {
937 // Library is next
938 ++libIt;
939 }
940 else
941 break; // we're done with the list
942 }
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000943 }</pre></div>
944
Reid Spencer2c8ab582004-08-13 20:19:14 +0000945 <p>Note that, for compatibility reasons, the <tt>cl::opt</tt> also supports an
946 <tt>unsigned getPosition()</tt> option that will provide the absolute position
947 of that option. You can apply the same approach as above with a
948 <tt>cl::opt</tt> and a <tt>cl::list</tt> option as you can with two lists.</p>
949</div>
950
951<!-- _______________________________________________________________________ -->
952<div class="doc_subsubsection">
Misha Brukman9718e962003-10-24 19:59:21 +0000953 <a name="cl::ConsumeAfter">The <tt>cl::ConsumeAfter</tt> modifier</a>
954</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000955
Misha Brukman9718e962003-10-24 19:59:21 +0000956<div class="doc_text">
957
958<p>The <tt>cl::ConsumeAfter</tt> <a href="#formatting">formatting option</a> is
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000959used to construct programs that use "interpreter style" option processing. With
960this style of option processing, all arguments specified after the last
961positional argument are treated as special interpreter arguments that are not
Misha Brukman9718e962003-10-24 19:59:21 +0000962interpreted by the command line argument.</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000963
Misha Brukman9718e962003-10-24 19:59:21 +0000964<p>As a concrete example, lets say we are developing a replacement for the
965standard Unix Bourne shell (<tt>/bin/sh</tt>). To run <tt>/bin/sh</tt>, first
966you specify options to the shell itself (like <tt>-x</tt> which turns on trace
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000967output), then you specify the name of the script to run, then you specify
968arguments to the script. These arguments to the script are parsed by the bourne
969shell command line option processor, but are not interpreted as options to the
Misha Brukman9718e962003-10-24 19:59:21 +0000970shell itself. Using the CommandLine library, we would specify this as:</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000971
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000972<div class="doc_code"><pre>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000973<a href="#cl::opt">cl::opt</a>&lt;string&gt; Script(<a href="#cl::Positional">cl::Positional</a>, <a href="#cl::desc">cl::desc</a>("<i>&lt;input script&gt;</i>"), <a href="#cl::init">cl::init</a>("-"));
974<a href="#cl::list">cl::list</a>&lt;string&gt; Argv(<a href="#cl::ConsumeAfter">cl::ConsumeAfter</a>, <a href="#cl::desc">cl::desc</a>("<i>&lt;program arguments&gt;...</i>"));
975<a href="#cl::opt">cl::opt</a>&lt;bool&gt; Trace("<i>x</i>", <a href="#cl::desc">cl::desc</a>("<i>Enable trace output</i>"));
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000976</pre></div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000977
Misha Brukman9718e962003-10-24 19:59:21 +0000978<p>which automatically provides the help output:</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000979
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000980<div class="doc_code"><pre>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +0000981USAGE: spiffysh [options] <b>&lt;input script&gt; &lt;program arguments&gt;...</b>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000982
983OPTIONS:
984 -help - display available options (--help-hidden for more)
Chris Lattnerc1ae40c2002-08-07 18:27:04 +0000985 <b>-x - Enable trace output</b>
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000986</pre></div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000987
Misha Brukmanf75c4b42005-03-11 00:00:33 +0000988<p>At runtime, if we run our new shell replacement as `<tt>spiffysh -x test.sh
Misha Brukman9718e962003-10-24 19:59:21 +0000989-a -x -y bar</tt>', the <tt>Trace</tt> variable will be set to true, the
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000990<tt>Script</tt> variable will be set to "<tt>test.sh</tt>", and the
Misha Brukman9718e962003-10-24 19:59:21 +0000991<tt>Argv</tt> list will contain <tt>["-a", "-x", "-y", "bar"]</tt>, because they
992were specified after the last positional argument (which is the script
993name).</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +0000994
Misha Brukman9718e962003-10-24 19:59:21 +0000995<p>There are several limitations to when <tt>cl::ConsumeAfter</tt> options can
996be specified. For example, only one <tt>cl::ConsumeAfter</tt> can be specified
997per program, there must be at least one <a href="#positional">positional
Chris Lattnerbe801bf2004-05-06 22:03:59 +0000998argument</a> specified, there must not be any <a href="#cl::list">cl::list</a>
999positional arguments, and the <tt>cl::ConsumeAfter</tt> option should be a <a
Misha Brukman9718e962003-10-24 19:59:21 +00001000href="#cl::list">cl::list</a> option.</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001001
Misha Brukman9718e962003-10-24 19:59:21 +00001002</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001003
1004<!-- ======================================================================= -->
Chris Lattnerbe801bf2004-05-06 22:03:59 +00001005<div class="doc_subsection">
Misha Brukman9718e962003-10-24 19:59:21 +00001006 <a name="storage">Internal vs External Storage</a>
1007</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001008
Misha Brukman9718e962003-10-24 19:59:21 +00001009<div class="doc_text">
1010
1011<p>By default, all command line options automatically hold the value that they
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001012parse from the command line. This is very convenient in the common case,
1013especially when combined with the ability to define command line options in the
Misha Brukman9718e962003-10-24 19:59:21 +00001014files that use them. This is called the internal storage model.</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001015
Misha Brukman9718e962003-10-24 19:59:21 +00001016<p>Sometimes, however, it is nice to separate the command line option processing
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001017code from the storage of the value parsed. For example, lets say that we have a
1018'<tt>-debug</tt>' option that we would like to use to enable debug information
1019across the entire body of our program. In this case, the boolean value
1020controlling the debug code should be globally accessable (in a header file, for
1021example) yet the command line option processing code should not be exposed to
1022all of these clients (requiring lots of .cpp files to #include
Misha Brukman9718e962003-10-24 19:59:21 +00001023<tt>CommandLine.h</tt>).</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001024
Misha Brukman9718e962003-10-24 19:59:21 +00001025<p>To do this, set up your .h file with your option, like this for example:</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001026
Misha Brukman1fc9f8e2005-02-09 22:49:05 +00001027<div class="doc_code">
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001028<pre>
1029<i>// DebugFlag.h - Get access to the '-debug' command line option
1030//
1031
1032// DebugFlag - This boolean is set to true if the '-debug' command line option
1033// is specified. This should probably not be referenced directly, instead, use
1034// the DEBUG macro below.
1035//</i>
1036extern bool DebugFlag;
1037
1038<i>// DEBUG macro - This macro should be used by code to emit debug information.
1039// In the '-debug' option is specified on the command line, and if this is a
1040// debug build, then the code specified as the option to the macro will be
1041// executed. Otherwise it will not be. Example:
1042//
Misha Brukman1fc9f8e2005-02-09 22:49:05 +00001043// DEBUG(std::cerr &lt;&lt; "Bitset contains: " &lt;&lt; Bitset &lt;&lt; "\n");
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001044//</i>
Misha Brukman1fc9f8e2005-02-09 22:49:05 +00001045<span class="doc_hilite">#ifdef NDEBUG
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001046#define DEBUG(X)
1047#else
Misha Brukman1fc9f8e2005-02-09 22:49:05 +00001048#define DEBUG(X)</span> do { if (DebugFlag) { X; } } while (0)
1049<span class="doc_hilite">#endif</span>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001050</pre>
Misha Brukman1fc9f8e2005-02-09 22:49:05 +00001051</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001052
Misha Brukman9718e962003-10-24 19:59:21 +00001053<p>This allows clients to blissfully use the <tt>DEBUG()</tt> macro, or the
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001054<tt>DebugFlag</tt> explicitly if they want to. Now we just need to be able to
1055set the <tt>DebugFlag</tt> boolean when the option is set. To do this, we pass
1056an additial argument to our command line argument processor, and we specify
Misha Brukman9718e962003-10-24 19:59:21 +00001057where to fill in with the <a href="#cl::location">cl::location</a>
1058attribute:</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001059
Misha Brukman1fc9f8e2005-02-09 22:49:05 +00001060<div class="doc_code">
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001061<pre>
Misha Brukman1fc9f8e2005-02-09 22:49:05 +00001062bool DebugFlag; <i>// the actual value</i>
Chris Lattner589a4cc2003-08-01 21:30:37 +00001063static <a href="#cl::opt">cl::opt</a>&lt;bool, true&gt; <i>// The parser</i>
Misha Brukman1fc9f8e2005-02-09 22:49:05 +00001064Debug("<i>debug</i>", <a href="#cl::desc">cl::desc</a>("<i>Enable debug output</i>"), <a href="#cl::Hidden">cl::Hidden</a>, <a href="#cl::location">cl::location</a>(DebugFlag));
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001065</pre>
Misha Brukman1fc9f8e2005-02-09 22:49:05 +00001066</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001067
Misha Brukman9718e962003-10-24 19:59:21 +00001068<p>In the above example, we specify "<tt>true</tt>" as the second argument to
Misha Brukman1fc9f8e2005-02-09 22:49:05 +00001069the <tt><a href="#cl::opt">cl::opt</a></tt> template, indicating that the
1070template should not maintain a copy of the value itself. In addition to this,
1071we specify the <tt><a href="#cl::location">cl::location</a></tt> attribute, so
1072that <tt>DebugFlag</tt> is automatically set.</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001073
Misha Brukman9718e962003-10-24 19:59:21 +00001074</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001075
1076<!-- ======================================================================= -->
Misha Brukman9718e962003-10-24 19:59:21 +00001077<div class="doc_subsection">
1078 <a name="attributes">Option Attributes</a>
1079</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001080
Misha Brukman9718e962003-10-24 19:59:21 +00001081<div class="doc_text">
1082
1083<p>This section describes the basic attributes that you can specify on
1084options.</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001085
1086<ul>
1087
1088<li>The option name attribute (which is required for all options, except <a
1089href="#positional">positional options</a>) specifies what the option name is.
Misha Brukman9718e962003-10-24 19:59:21 +00001090This option is specified in simple double quotes:
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001091
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001092<pre>
1093<a href="#cl::opt">cl::opt</a>&lt;<b>bool</b>&gt; Quiet("<i>quiet</i>");
Misha Brukman9718e962003-10-24 19:59:21 +00001094</pre>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001095
Misha Brukman9718e962003-10-24 19:59:21 +00001096</li>
1097
1098<li><a name="cl::desc">The <b><tt>cl::desc</tt></b></a> attribute specifies a
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001099description for the option to be shown in the <tt>--help</tt> output for the
Misha Brukman9718e962003-10-24 19:59:21 +00001100program.</li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001101
Misha Brukman9718e962003-10-24 19:59:21 +00001102<li><a name="cl::value_desc">The <b><tt>cl::value_desc</tt></b></a> attribute
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001103specifies a string that can be used to fine tune the <tt>--help</tt> output for
1104a command line option. Look <a href="#value_desc_example">here</a> for an
Misha Brukman9718e962003-10-24 19:59:21 +00001105example.</li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001106
Misha Brukman9718e962003-10-24 19:59:21 +00001107<li><a name="cl::init">The <b><tt>cl::init</tt></b></a> attribute specifies an
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001108inital value for a <a href="#cl::opt">scalar</a> option. If this attribute is
1109not specified then the command line option value defaults to the value created
Brian Gaeke9d292ff2003-08-19 22:56:22 +00001110by the default constructor for the type. <b>Warning</b>: If you specify both
1111<b><tt>cl::init</tt></b> and <b><tt>cl::location</tt></b> for an option,
1112you must specify <b><tt>cl::location</tt></b> first, so that when the
1113command-line parser sees <b><tt>cl::init</tt></b>, it knows where to put the
1114initial value. (You will get an error at runtime if you don't put them in
Misha Brukman9718e962003-10-24 19:59:21 +00001115the right order.)</li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001116
Misha Brukman9718e962003-10-24 19:59:21 +00001117<li><a name="cl::location">The <b><tt>cl::location</tt></b></a> attribute where to
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001118store the value for a parsed command line option if using external storage. See
1119the section on <a href="#storage">Internal vs External Storage</a> for more
Misha Brukman9718e962003-10-24 19:59:21 +00001120information.</li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001121
Misha Brukman9718e962003-10-24 19:59:21 +00001122<li><a name="cl::aliasopt">The <b><tt>cl::aliasopt</tt></b></a> attribute
Misha Brukman1fc9f8e2005-02-09 22:49:05 +00001123specifies which option a <tt><a href="#cl::alias">cl::alias</a></tt> option is
1124an alias for.</li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001125
Misha Brukman9718e962003-10-24 19:59:21 +00001126<li><a name="cl::values">The <b><tt>cl::values</tt></b></a> attribute specifies
1127the string-to-value mapping to be used by the generic parser. It takes a
Chris Lattnerb406ead2004-07-16 00:10:54 +00001128<b>clEnumValEnd terminated</b> list of (option, value, description) triplets
1129that
Misha Brukman9718e962003-10-24 19:59:21 +00001130specify the option name, the value mapped to, and the description shown in the
1131<tt>--help</tt> for the tool. Because the generic parser is used most
1132frequently with enum values, two macros are often useful:
1133
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001134<ol>
Misha Brukman9718e962003-10-24 19:59:21 +00001135
1136<li><a name="clEnumVal">The <b><tt>clEnumVal</tt></b></a> macro is used as a
1137nice simple way to specify a triplet for an enum. This macro automatically
1138makes the option name be the same as the enum name. The first option to the
1139macro is the enum, the second is the description for the command line
1140option.</li>
1141
1142<li><a name="clEnumValN">The <b><tt>clEnumValN</tt></b></a> macro is used to
1143specify macro options where the option name doesn't equal the enum name. For
1144this macro, the first argument is the enum value, the second is the flag name,
1145and the second is the description.</li>
1146
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001147</ol>
1148
1149You will get a compile time error if you try to use cl::values with a parser
Misha Brukman9718e962003-10-24 19:59:21 +00001150that does not support it.</li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001151
1152</ul>
1153
Misha Brukman9718e962003-10-24 19:59:21 +00001154</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001155
1156<!-- ======================================================================= -->
Misha Brukman9718e962003-10-24 19:59:21 +00001157<div class="doc_subsection">
1158 <a name="modifiers">Option Modifiers</a>
1159</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001160
Misha Brukman9718e962003-10-24 19:59:21 +00001161<div class="doc_text">
1162
1163<p>Option modifiers are the flags and expressions that you pass into the
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001164constructors for <tt><a href="#cl::opt">cl::opt</a></tt> and <tt><a
1165href="#cl::list">cl::list</a></tt>. These modifiers give you the ability to
1166tweak how options are parsed and how <tt>--help</tt> output is generated to fit
Misha Brukman9718e962003-10-24 19:59:21 +00001167your application well.</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001168
Misha Brukman9718e962003-10-24 19:59:21 +00001169<p>These options fall into five main catagories:</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001170
1171<ol>
Misha Brukman9718e962003-10-24 19:59:21 +00001172<li><a href="#hiding">Hiding an option from <tt>--help</tt> output</a></li>
1173<li><a href="#numoccurrences">Controlling the number of occurrences
1174 required and allowed</a></li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001175<li><a href="#valrequired">Controlling whether or not a value must be
Misha Brukman9718e962003-10-24 19:59:21 +00001176 specified</a></li>
1177<li><a href="#formatting">Controlling other formatting options</a></li>
1178<li><a href="#misc">Miscellaneous option modifiers</a></li>
1179</ol>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001180
Misha Brukman9718e962003-10-24 19:59:21 +00001181<p>It is not possible to specify two options from the same catagory (you'll get
1182a runtime error) to a single option, except for options in the miscellaneous
Chris Lattner32a32842003-05-22 20:36:06 +00001183catagory. The CommandLine library specifies defaults for all of these settings
1184that are the most useful in practice and the most common, which mean that you
Misha Brukman9718e962003-10-24 19:59:21 +00001185usually shouldn't have to worry about these.</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001186
Misha Brukman9718e962003-10-24 19:59:21 +00001187</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001188
1189<!-- _______________________________________________________________________ -->
Misha Brukman9718e962003-10-24 19:59:21 +00001190<div class="doc_subsubsection">
1191 <a name="hiding">Hiding an option from <tt>--help</tt> output</a>
1192</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001193
Misha Brukman9718e962003-10-24 19:59:21 +00001194<div class="doc_text">
1195
1196<p>The <tt>cl::NotHidden</tt>, <tt>cl::Hidden</tt>, and
1197<tt>cl::ReallyHidden</tt> modifiers are used to control whether or not an option
1198appears in the <tt>--help</tt> and <tt>--help-hidden</tt> output for the
1199compiled program:</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001200
1201<ul>
1202
Misha Brukman9718e962003-10-24 19:59:21 +00001203<li><a name="cl::NotHidden">The <b><tt>cl::NotHidden</tt></b></a> modifier
1204(which is the default for <tt><a href="#cl::opt">cl::opt</a></tt> and <tt><a
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001205href="#cl::list">cl::list</a></tt> options), indicates the option is to appear
Misha Brukman9718e962003-10-24 19:59:21 +00001206in both help listings.</li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001207
Misha Brukman9718e962003-10-24 19:59:21 +00001208<li><a name="cl::Hidden">The <b><tt>cl::Hidden</tt></b></a> modifier (which is the
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001209default for <tt><a href="#cl::alias">cl::alias</a></tt> options), indicates that
1210the option should not appear in the <tt>--help</tt> output, but should appear in
Misha Brukman9718e962003-10-24 19:59:21 +00001211the <tt>--help-hidden</tt> output.</li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001212
Misha Brukman9718e962003-10-24 19:59:21 +00001213<li><a name="cl::ReallyHidden">The <b><tt>cl::ReallyHidden</tt></b></a> modifier,
1214indicates that the option should not appear in any help output.</li>
1215
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001216</ul>
1217
Misha Brukman9718e962003-10-24 19:59:21 +00001218</div>
1219
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001220<!-- _______________________________________________________________________ -->
Misha Brukman9718e962003-10-24 19:59:21 +00001221<div class="doc_subsubsection">
1222 <a name="numoccurrences">Controlling the number of occurrences required and
1223 allowed</a>
1224</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001225
Misha Brukman9718e962003-10-24 19:59:21 +00001226<div class="doc_text">
1227
1228<p>This group of options is used to control how many time an option is allowed
1229(or required) to be specified on the command line of your program. Specifying a
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001230value for this setting allows the CommandLine library to do error checking for
Misha Brukman9718e962003-10-24 19:59:21 +00001231you.</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001232
Misha Brukman9718e962003-10-24 19:59:21 +00001233<p>The allowed values for this option group are:</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001234
1235<ul>
Misha Brukman9718e962003-10-24 19:59:21 +00001236
1237<li><a name="cl::Optional">The <b><tt>cl::Optional</tt></b></a> modifier (which
1238is the default for the <tt><a href="#cl::opt">cl::opt</a></tt> and <tt><a
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001239href="#cl::alias">cl::alias</a></tt> classes) indicates that your program will
Misha Brukman9718e962003-10-24 19:59:21 +00001240allow either zero or one occurrence of the option to be specified.</li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001241
Misha Brukman9718e962003-10-24 19:59:21 +00001242<li><a name="cl::ZeroOrMore">The <b><tt>cl::ZeroOrMore</tt></b></a> modifier
1243(which is the default for the <tt><a href="#cl::list">cl::list</a></tt> class)
1244indicates that your program will allow the option to be specified zero or more
1245times.</li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001246
Misha Brukman9718e962003-10-24 19:59:21 +00001247<li><a name="cl::Required">The <b><tt>cl::Required</tt></b></a> modifier
1248indicates that the specified option must be specified exactly one time.</li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001249
Misha Brukman9718e962003-10-24 19:59:21 +00001250<li><a name="cl::OneOrMore">The <b><tt>cl::OneOrMore</tt></b></a> modifier
1251indicates that the option must be specified at least one time.</li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001252
Misha Brukman9718e962003-10-24 19:59:21 +00001253<li>The <b><tt>cl::ConsumeAfter</tt></b> modifier is described in the <a
1254href="#positional">Positional arguments section</a></li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001255
1256</ul>
1257
Misha Brukman9718e962003-10-24 19:59:21 +00001258<p>If an option is not specified, then the value of the option is equal to the
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001259value specified by the <tt><a href="#cl::init">cl::init</a></tt> attribute. If
1260the <tt><a href="#cl::init">cl::init</a></tt> attribute is not specified, the
Misha Brukman9718e962003-10-24 19:59:21 +00001261option value is initialized with the default constructor for the data type.</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001262
Misha Brukman9718e962003-10-24 19:59:21 +00001263<p>If an option is specified multiple times for an option of the <tt><a
1264href="#cl::opt">cl::opt</a></tt> class, only the last value will be
1265retained.</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001266
Misha Brukman9718e962003-10-24 19:59:21 +00001267</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001268
1269<!-- _______________________________________________________________________ -->
Misha Brukman9718e962003-10-24 19:59:21 +00001270<div class="doc_subsubsection">
1271 <a name="valrequired">Controlling whether or not a value must be specified</a>
1272</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001273
Misha Brukman9718e962003-10-24 19:59:21 +00001274<div class="doc_text">
1275
1276<p>This group of options is used to control whether or not the option allows a
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001277value to be present. In the case of the CommandLine library, a value is either
1278specified with an equal sign (e.g. '<tt>-index-depth=17</tt>') or as a trailing
Misha Brukman9718e962003-10-24 19:59:21 +00001279string (e.g. '<tt>-o a.out</tt>').</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001280
Misha Brukman9718e962003-10-24 19:59:21 +00001281<p>The allowed values for this option group are:</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001282
1283<ul>
Misha Brukman9718e962003-10-24 19:59:21 +00001284
1285<li><a name="cl::ValueOptional">The <b><tt>cl::ValueOptional</tt></b></a> modifier
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001286(which is the default for <tt>bool</tt> typed options) specifies that it is
1287acceptable to have a value, or not. A boolean argument can be enabled just by
1288appearing on the command line, or it can have an explicit '<tt>-foo=true</tt>'.
1289If an option is specified with this mode, it is illegal for the value to be
1290provided without the equal sign. Therefore '<tt>-foo true</tt>' is illegal. To
1291get this behavior, you must use the <a
Misha Brukman9718e962003-10-24 19:59:21 +00001292href="#cl::ValueRequired">cl::ValueRequired</a> modifier.</li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001293
Misha Brukman9718e962003-10-24 19:59:21 +00001294<li><a name="cl::ValueRequired">The <b><tt>cl::ValueRequired</tt></b></a> modifier
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001295(which is the default for all other types except for <a
1296href="#onealternative">unnamed alternatives using the generic parser</a>)
1297specifies that a value must be provided. This mode informs the command line
1298library that if an option is not provides with an equal sign, that the next
1299argument provided must be the value. This allows things like '<tt>-o
Misha Brukman9718e962003-10-24 19:59:21 +00001300a.out</tt>' to work.</li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001301
Misha Brukman9718e962003-10-24 19:59:21 +00001302<li><a name="cl::ValueDisallowed">The <b><tt>cl::ValueDisallowed</tt></b></a>
1303modifier (which is the default for <a href="#onealternative">unnamed
1304alternatives using the generic parser</a>) indicates that it is a runtime error
1305for the user to specify a value. This can be provided to disallow users from
1306providing options to boolean options (like '<tt>-foo=true</tt>').</li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001307
1308</ul>
1309
Misha Brukman9718e962003-10-24 19:59:21 +00001310<p>In general, the default values for this option group work just like you would
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001311want them to. As mentioned above, you can specify the <a
1312href="#cl::ValueDisallowed">cl::ValueDisallowed</a> modifier to a boolean
1313argument to restrict your command line parser. These options are mostly useful
Misha Brukman9718e962003-10-24 19:59:21 +00001314when <a href="#extensionguide">extending the library</a>.</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001315
Misha Brukman9718e962003-10-24 19:59:21 +00001316</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001317
1318<!-- _______________________________________________________________________ -->
Misha Brukman9718e962003-10-24 19:59:21 +00001319<div class="doc_subsubsection">
1320 <a name="formatting">Controlling other formatting options</a>
1321</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001322
Misha Brukman9718e962003-10-24 19:59:21 +00001323<div class="doc_text">
1324
1325<p>The formatting option group is used to specify that the command line option
1326has special abilities and is otherwise different from other command line
1327arguments. As usual, you can only specify at most one of these arguments.</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001328
1329<ul>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001330
Misha Brukman9718e962003-10-24 19:59:21 +00001331<li><a name="cl::NormalFormatting">The <b><tt>cl::NormalFormatting</tt></b></a>
1332modifier (which is the default all options) specifies that this option is
1333"normal".</li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001334
Misha Brukman9718e962003-10-24 19:59:21 +00001335<li><a name="cl::Positional">The <b><tt>cl::Positional</tt></b></a> modifier
1336specifies that this is a positional argument, that does not have a command line
1337option associated with it. See the <a href="#positional">Positional
1338Arguments</a> section for more information.</li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001339
Misha Brukman9718e962003-10-24 19:59:21 +00001340<li>The <b><a href="#cl::ConsumeAfter"><tt>cl::ConsumeAfter</tt></a></b> modifier
1341specifies that this option is used to capture "interpreter style" arguments. See <a href="#cl::ConsumeAfter">this section for more information</a>.</li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001342
Misha Brukman9718e962003-10-24 19:59:21 +00001343<li><a name="cl::Prefix">The <b><tt>cl::Prefix</tt></b></a> modifier specifies
Reid Spencer5f8448f2004-11-24 06:13:42 +00001344that this option prefixes its value. With 'Prefix' options, the equal sign does
1345not separate the value from the option name specified. Instead, the value is
1346everything after the prefix, including any equal sign if present. This is useful
1347for processing odd arguments like <tt>-lmalloc</tt> and <tt>-L/usr/lib</tt> in a
Misha Brukmanc43d9142005-05-10 22:05:27 +00001348linker tool or <tt>-DNAME=value</tt> in a compiler tool. Here, the
Reid Spencer5f8448f2004-11-24 06:13:42 +00001349'<tt>l</tt>', '<tt>D</tt>' and '<tt>L</tt>' options are normal string (or list)
Misha Brukmanc43d9142005-05-10 22:05:27 +00001350options, that have the <b><tt><a href="#cl::Prefix">cl::Prefix</a></tt></b>
1351modifier added to allow the CommandLine library to recognize them. Note that
1352<b><tt><a href="#cl::Prefix">cl::Prefix</a></tt></b> options must not have the
1353<b><tt><a href="#cl::ValueDisallowed">cl::ValueDisallowed</a></tt></b> modifier
1354specified.</li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001355
Misha Brukman9718e962003-10-24 19:59:21 +00001356<li><a name="cl::Grouping">The <b><tt>cl::Grouping</tt></b></a> modifier is used
1357to implement unix style tools (like <tt>ls</tt>) that have lots of single letter
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001358arguments, but only require a single dash. For example, the '<tt>ls -labF</tt>'
1359command actually enables four different options, all of which are single
Misha Brukmanc43d9142005-05-10 22:05:27 +00001360letters. Note that <b><tt><a href="#cl::Grouping">cl::Grouping</a></tt></b>
1361options cannot have values.</li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001362
1363</ul>
1364
Misha Brukmanc43d9142005-05-10 22:05:27 +00001365<p>The CommandLine library does not restrict how you use the <b><tt><a
1366href="#cl::Prefix">cl::Prefix</a></tt></b> or <b><tt><a
1367href="#cl::Grouping">cl::Grouping</a></tt></b> modifiers, but it is possible to
1368specify ambiguous argument settings. Thus, it is possible to have multiple
1369letter options that are prefix or grouping options, and they will still work as
1370designed.</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001371
Misha Brukman9718e962003-10-24 19:59:21 +00001372<p>To do this, the CommandLine library uses a greedy algorithm to parse the
1373input option into (potentially multiple) prefix and grouping options. The
1374strategy basically looks like this:</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001375
Misha Brukmanf75c4b42005-03-11 00:00:33 +00001376<div class="doc_code"><tt>parse(string OrigInput) {</tt>
Misha Brukmanc53aefb2004-05-12 18:42:35 +00001377
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001378<ol>
1379<li><tt>string input = OrigInput;</tt>
1380<li><tt>if (isOption(input)) return getOption(input).parse();</tt>&nbsp;&nbsp;&nbsp;&nbsp;<i>// Normal option</i>
1381<li><tt>while (!isOption(input) &amp;&amp; !input.empty()) input.pop_back();</tt>&nbsp;&nbsp;&nbsp;&nbsp;<i>// Remove the last letter</i>
1382<li><tt>if (input.empty()) return error();</tt>&nbsp;&nbsp;&nbsp;&nbsp;<i>// No matching option</i>
1383<li><tt>if (getOption(input).isPrefix())<br>
1384&nbsp;&nbsp;return getOption(input).parse(input);</tt>
1385<li><tt>while (!input.empty()) {&nbsp;&nbsp;&nbsp;&nbsp;<i>// Must be grouping options</i><br>
1386&nbsp;&nbsp;getOption(input).parse();<br>
1387&nbsp;&nbsp;OrigInput.erase(OrigInput.begin(), OrigInput.begin()+input.length());<br>
1388&nbsp;&nbsp;input = OrigInput;<br>
1389&nbsp;&nbsp;while (!isOption(input) &amp;&amp; !input.empty()) input.pop_back();<br>
1390}</tt>
Misha Brukmanc53aefb2004-05-12 18:42:35 +00001391<li><tt>if (!OrigInput.empty()) error();</tt></li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001392</ol>
Misha Brukmanc53aefb2004-05-12 18:42:35 +00001393
1394<p><tt>}</tt></p>
Misha Brukmanf75c4b42005-03-11 00:00:33 +00001395</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001396
Misha Brukman9718e962003-10-24 19:59:21 +00001397</div>
Chris Lattner32a32842003-05-22 20:36:06 +00001398
1399<!-- _______________________________________________________________________ -->
Misha Brukman9718e962003-10-24 19:59:21 +00001400<div class="doc_subsubsection">
1401 <a name="misc">Miscellaneous option modifiers</a>
1402</div>
Chris Lattner32a32842003-05-22 20:36:06 +00001403
Misha Brukman9718e962003-10-24 19:59:21 +00001404<div class="doc_text">
1405
1406<p>The miscellaneous option modifiers are the only flags where you can specify
1407more than one flag from the set: they are not mutually exclusive. These flags
1408specify boolean properties that modify the option.</p>
Chris Lattner32a32842003-05-22 20:36:06 +00001409
1410<ul>
1411
Misha Brukman9718e962003-10-24 19:59:21 +00001412<li><a name="cl::CommaSeparated">The <b><tt>cl::CommaSeparated</tt></b></a> modifier
Chris Lattner32a32842003-05-22 20:36:06 +00001413indicates that any commas specified for an option's value should be used to
1414split the value up into multiple values for the option. For example, these two
1415options are equivalent when <tt>cl::CommaSeparated</tt> is specified:
1416"<tt>-foo=a -foo=b -foo=c</tt>" and "<tt>-foo=a,b,c</tt>". This option only
1417makes sense to be used in a case where the option is allowed to accept one or
Misha Brukman9718e962003-10-24 19:59:21 +00001418more values (i.e. it is a <a href="#cl::list">cl::list</a> option).</li>
1419
Chris Lattnerbe801bf2004-05-06 22:03:59 +00001420<li><a name="cl::PositionalEatsArgs">The
1421<b><tt>cl::PositionalEatsArgs</tt></b></a> modifier (which only applies to
1422positional arguments, and only makes sense for lists) indicates that positional
1423argument should consume any strings after it (including strings that start with
1424a "-") up until another recognized positional argument. For example, if you
1425have two "eating" positional arguments "<tt>pos1</tt>" and "<tt>pos2</tt>" the
1426string "<tt>-pos1 -foo -bar baz -pos2 -bork</tt>" would cause the "<tt>-foo -bar
1427-baz</tt>" strings to be applied to the "<tt>-pos1</tt>" option and the
1428"<tt>-bork</tt>" string to be applied to the "<tt>-pos2</tt>" option.</li>
1429
Chris Lattner32a32842003-05-22 20:36:06 +00001430</ul>
1431
Chris Lattnerbe801bf2004-05-06 22:03:59 +00001432<p>So far, these are the only two miscellaneous option modifiers.</p>
Chris Lattner32a32842003-05-22 20:36:06 +00001433
Misha Brukman9718e962003-10-24 19:59:21 +00001434</div>
Chris Lattner32a32842003-05-22 20:36:06 +00001435
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001436<!-- ======================================================================= -->
Misha Brukman9718e962003-10-24 19:59:21 +00001437<div class="doc_subsection">
1438 <a name="toplevel">Top-Level Classes and Functions</a>
1439</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001440
Misha Brukman9718e962003-10-24 19:59:21 +00001441<div class="doc_text">
1442
1443<p>Despite all of the built-in flexibility, the CommandLine option library
1444really only consists of one function (<a
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001445href="#cl::ParseCommandLineOptions"><tt>cl::ParseCommandLineOptions</tt></a>)
1446and three main classes: <a href="#cl::opt"><tt>cl::opt</tt></a>, <a
1447href="#cl::list"><tt>cl::list</tt></a>, and <a
1448href="#cl::alias"><tt>cl::alias</tt></a>. This section describes these three
Misha Brukman9718e962003-10-24 19:59:21 +00001449classes in detail.</p>
1450
1451</div>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001452
1453<!-- _______________________________________________________________________ -->
Misha Brukman9718e962003-10-24 19:59:21 +00001454<div class="doc_subsubsection">
1455 <a name="cl::ParseCommandLineOptions">The <tt>cl::ParseCommandLineOptions</tt>
1456 function</a>
1457</div>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001458
Misha Brukman9718e962003-10-24 19:59:21 +00001459<div class="doc_text">
1460
1461<p>The <tt>cl::ParseCommandLineOptions</tt> function is designed to be called
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001462directly from <tt>main</tt>, and is used to fill in the values of all of the
1463command line option variables once <tt>argc</tt> and <tt>argv</tt> are
Misha Brukman9718e962003-10-24 19:59:21 +00001464available.</p>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001465
Misha Brukman9718e962003-10-24 19:59:21 +00001466<p>The <tt>cl::ParseCommandLineOptions</tt> function requires two parameters
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001467(<tt>argc</tt> and <tt>argv</tt>), but may also take an optional third parameter
1468which holds <a href="#description">additional extra text</a> to emit when the
Misha Brukman9718e962003-10-24 19:59:21 +00001469<tt>--help</tt> option is invoked.</p>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001470
Misha Brukman9718e962003-10-24 19:59:21 +00001471</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001472
1473<!-- _______________________________________________________________________ -->
Misha Brukman9718e962003-10-24 19:59:21 +00001474<div class="doc_subsubsection">
1475 <a name="cl::ParseEnvironmentOptions">The <tt>cl::ParseEnvironmentOptions</tt>
1476 function</a>
1477</div>
Brian Gaekee5842852003-08-19 23:11:43 +00001478
Misha Brukman9718e962003-10-24 19:59:21 +00001479<div class="doc_text">
Brian Gaekee5842852003-08-19 23:11:43 +00001480
Misha Brukman9718e962003-10-24 19:59:21 +00001481<p>The <tt>cl::ParseEnvironmentOptions</tt> function has mostly the same effects
1482as <a
1483href="#cl::ParseCommandLineOptions"><tt>cl::ParseCommandLineOptions</tt></a>,
1484except that it is designed to take values for options from an environment
1485variable, for those cases in which reading the command line is not convenient or
1486not desired. It fills in the values of all the command line option variables
1487just like <a
1488href="#cl::ParseCommandLineOptions"><tt>cl::ParseCommandLineOptions</tt></a>
1489does.</p>
1490
1491<p>It takes three parameters: first, the name of the program (since
1492<tt>argv</tt> may not be available, it can't just look in <tt>argv[0]</tt>),
1493second, the name of the environment variable to examine, and third, the optional
Brian Gaekee5842852003-08-19 23:11:43 +00001494<a href="#description">additional extra text</a> to emit when the
Misha Brukman9718e962003-10-24 19:59:21 +00001495<tt>--help</tt> option is invoked.</p>
Brian Gaekee5842852003-08-19 23:11:43 +00001496
Misha Brukman9718e962003-10-24 19:59:21 +00001497<p><tt>cl::ParseEnvironmentOptions</tt> will break the environment
Brian Gaekee5842852003-08-19 23:11:43 +00001498variable's value up into words and then process them using
1499<a href="#cl::ParseCommandLineOptions"><tt>cl::ParseCommandLineOptions</tt></a>.
1500<b>Note:</b> Currently <tt>cl::ParseEnvironmentOptions</tt> does not support
1501quoting, so an environment variable containing <tt>-option "foo bar"</tt> will
1502be parsed as three words, <tt>-option</tt>, <tt>"foo</tt>, and <tt>bar"</tt>,
1503which is different from what you would get from the shell with the same
Misha Brukman9718e962003-10-24 19:59:21 +00001504input.</p>
1505
1506</div>
Brian Gaekee5842852003-08-19 23:11:43 +00001507
1508<!-- _______________________________________________________________________ -->
Misha Brukman9718e962003-10-24 19:59:21 +00001509<div class="doc_subsubsection">
1510 <a name="cl::opt">The <tt>cl::opt</tt> class</a>
1511</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001512
Misha Brukman9718e962003-10-24 19:59:21 +00001513<div class="doc_text">
1514
1515<p>The <tt>cl::opt</tt> class is the class used to represent scalar command line
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001516options, and is the one used most of the time. It is a templated class which
1517can take up to three arguments (all except for the first have default values
Misha Brukman9718e962003-10-24 19:59:21 +00001518though):</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001519
Misha Brukmanf75c4b42005-03-11 00:00:33 +00001520<div class="doc_code"><pre>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001521<b>namespace</b> cl {
1522 <b>template</b> &lt;<b>class</b> DataType, <b>bool</b> ExternalStorage = <b>false</b>,
1523 <b>class</b> ParserClass = parser&lt;DataType&gt; &gt;
1524 <b>class</b> opt;
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001525}
Misha Brukmanf75c4b42005-03-11 00:00:33 +00001526</pre></div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001527
Misha Brukman9718e962003-10-24 19:59:21 +00001528<p>The first template argument specifies what underlying data type the command
1529line argument is, and is used to select a default parser implementation. The
1530second template argument is used to specify whether the option should contain
1531the storage for the option (the default) or whether external storage should be
1532used to contain the value parsed for the option (see <a href="#storage">Internal
1533vs External Storage</a> for more information).</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001534
Misha Brukman9718e962003-10-24 19:59:21 +00001535<p>The third template argument specifies which parser to use. The default value
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001536selects an instantiation of the <tt>parser</tt> class based on the underlying
1537data type of the option. In general, this default works well for most
1538applications, so this option is only used when using a <a
Misha Brukman9718e962003-10-24 19:59:21 +00001539href="#customparser">custom parser</a>.</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001540
Misha Brukman9718e962003-10-24 19:59:21 +00001541</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001542
1543<!-- _______________________________________________________________________ -->
Misha Brukman9718e962003-10-24 19:59:21 +00001544<div class="doc_subsubsection">
1545 <a name="cl::list">The <tt>cl::list</tt> class</a>
1546</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001547
Misha Brukman9718e962003-10-24 19:59:21 +00001548<div class="doc_text">
1549
1550<p>The <tt>cl::list</tt> class is the class used to represent a list of command
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001551line options. It too is a templated class which can take up to three
Misha Brukman9718e962003-10-24 19:59:21 +00001552arguments:</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001553
Misha Brukmanf75c4b42005-03-11 00:00:33 +00001554<div class="doc_code"><pre>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001555<b>namespace</b> cl {
1556 <b>template</b> &lt;<b>class</b> DataType, <b>class</b> Storage = <b>bool</b>,
1557 <b>class</b> ParserClass = parser&lt;DataType&gt; &gt;
1558 <b>class</b> list;
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001559}
Misha Brukmanf75c4b42005-03-11 00:00:33 +00001560</pre></div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001561
Misha Brukman9718e962003-10-24 19:59:21 +00001562<p>This class works the exact same as the <a
1563href="#cl::opt"><tt>cl::opt</tt></a> class, except that the second argument is
1564the <b>type</b> of the external storage, not a boolean value. For this class,
1565the marker type '<tt>bool</tt>' is used to indicate that internal storage should
1566be used.</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001567
Misha Brukman9718e962003-10-24 19:59:21 +00001568</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001569
1570<!-- _______________________________________________________________________ -->
Misha Brukman9718e962003-10-24 19:59:21 +00001571<div class="doc_subsubsection">
Jim Laskey1d8f6262005-08-25 22:52:43 +00001572 <a name="cl::bits">The <tt>cl::bits</tt> class</a>
1573</div>
1574
1575<div class="doc_text">
1576
1577<p>The <tt>cl::bits</tt> class is the class used to represent a list of command
1578line options in the form of a bit vector. It is also a templated class which
1579can take up to three arguments:</p>
1580
1581<div class="doc_code"><pre>
1582<b>namespace</b> cl {
1583 <b>template</b> &lt;<b>class</b> DataType, <b>class</b> Storage = <b>bool</b>,
1584 <b>class</b> ParserClass = parser&lt;DataType&gt; &gt;
1585 <b>class</b> bits;
1586}
1587</pre></div>
1588
1589<p>This class works the exact same as the <a
1590href="#cl::opt"><tt>cl::lists</tt></a> class, except that the second argument
Jim Laskey22b7dfa2005-08-26 09:25:54 +00001591must be of <b>type</b> <tt>unsigned</tt> if external storage is used.</p>
Jim Laskey1d8f6262005-08-25 22:52:43 +00001592
1593</div>
1594
1595<!-- _______________________________________________________________________ -->
1596<div class="doc_subsubsection">
Misha Brukman9718e962003-10-24 19:59:21 +00001597 <a name="cl::alias">The <tt>cl::alias</tt> class</a>
1598</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001599
Misha Brukman9718e962003-10-24 19:59:21 +00001600<div class="doc_text">
1601
1602<p>The <tt>cl::alias</tt> class is a nontemplated class that is used to form
1603aliases for other arguments.</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001604
Misha Brukmanf75c4b42005-03-11 00:00:33 +00001605<div class="doc_code"><pre>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001606<b>namespace</b> cl {
1607 <b>class</b> alias;
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001608}
Misha Brukmanf75c4b42005-03-11 00:00:33 +00001609</pre></div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001610
Misha Brukman9718e962003-10-24 19:59:21 +00001611<p>The <a href="#cl::aliasopt"><tt>cl::aliasopt</tt></a> attribute should be
1612used to specify which option this is an alias for. Alias arguments default to
1613being <a href="#cl::Hidden">Hidden</a>, and use the aliased options parser to do
1614the conversion from string to data.</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001615
Misha Brukman9718e962003-10-24 19:59:21 +00001616</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001617
Reid Spencer9bbba0912004-11-16 06:11:52 +00001618<!-- _______________________________________________________________________ -->
1619<div class="doc_subsubsection">
1620 <a name="cl::extrahelp">The <tt>cl::extrahelp</tt> class</a>
1621</div>
1622
1623<div class="doc_text">
1624
1625<p>The <tt>cl::extrahelp</tt> class is a nontemplated class that allows extra
1626help text to be printed out for the <tt>--help</tt> option.</p>
1627
Misha Brukmanf75c4b42005-03-11 00:00:33 +00001628<div class="doc_code"><pre>
Reid Spencer9bbba0912004-11-16 06:11:52 +00001629<b>namespace</b> cl {
1630 <b>struct</b> extrahelp;
1631}
Misha Brukmanf75c4b42005-03-11 00:00:33 +00001632</pre></div>
Reid Spencer9bbba0912004-11-16 06:11:52 +00001633
1634<p>To use the extrahelp, simply construct one with a <tt>const char*</tt>
1635parameter to the constructor. The text passed to the constructor will be printed
1636at the bottom of the help message, verbatim. Note that multiple
Misha Brukmanf75c4b42005-03-11 00:00:33 +00001637<tt>cl::extrahelp</tt> <b>can</b> be used, but this practice is discouraged. If
Reid Spencer9bbba0912004-11-16 06:11:52 +00001638your tool needs to print additional help information, put all that help into a
1639single <tt>cl::extrahelp</tt> instance.</p>
1640<p>For example:</p>
Misha Brukmanf75c4b42005-03-11 00:00:33 +00001641<div class="doc_code"><pre>
Reid Spencer9bbba0912004-11-16 06:11:52 +00001642 cl::extrahelp("\nADDITIONAL HELP:\n\n This is the extra help\n");
Misha Brukmanf75c4b42005-03-11 00:00:33 +00001643</pre></div>
Reid Spencer9bbba0912004-11-16 06:11:52 +00001644</div>
1645
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001646<!-- ======================================================================= -->
Misha Brukman9718e962003-10-24 19:59:21 +00001647<div class="doc_subsection">
1648 <a name="builtinparsers">Builtin parsers</a>
1649</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001650
Misha Brukman9718e962003-10-24 19:59:21 +00001651<div class="doc_text">
1652
1653<p>Parsers control how the string value taken from the command line is
1654translated into a typed value, suitable for use in a C++ program. By default,
1655the CommandLine library uses an instance of <tt>parser&lt;type&gt;</tt> if the
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001656command line option specifies that it uses values of type '<tt>type</tt>'.
1657Because of this, custom option processing is specified with specializations of
Misha Brukman9718e962003-10-24 19:59:21 +00001658the '<tt>parser</tt>' class.</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001659
Misha Brukman9718e962003-10-24 19:59:21 +00001660<p>The CommandLine library provides the following builtin parser
1661specializations, which are sufficient for most applications. It can, however,
1662also be extended to work with new data types and new ways of interpreting the
1663same data. See the <a href="#customparser">Writing a Custom Parser</a> for more
1664details on this type of library extension.</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001665
Misha Brukman9718e962003-10-24 19:59:21 +00001666<ul>
1667
1668<li><a name="genericparser">The <b>generic <tt>parser&lt;t&gt;</tt> parser</b></a>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001669can be used to map strings values to any data type, through the use of the <a
1670href="#cl::values">cl::values</a> property, which specifies the mapping
1671information. The most common use of this parser is for parsing enum values,
1672which allows you to use the CommandLine library for all of the error checking to
1673make sure that only valid enum values are specified (as opposed to accepting
1674arbitrary strings). Despite this, however, the generic parser class can be used
Misha Brukman9718e962003-10-24 19:59:21 +00001675for any data type.</li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001676
Misha Brukman9718e962003-10-24 19:59:21 +00001677<li><a name="boolparser">The <b><tt>parser&lt;bool&gt;</tt> specialization</b></a>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001678is used to convert boolean strings to a boolean value. Currently accepted
1679strings are "<tt>true</tt>", "<tt>TRUE</tt>", "<tt>True</tt>", "<tt>1</tt>",
Misha Brukman9718e962003-10-24 19:59:21 +00001680"<tt>false</tt>", "<tt>FALSE</tt>", "<tt>False</tt>", and "<tt>0</tt>".</li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001681
Misha Brukman9718e962003-10-24 19:59:21 +00001682<li><a name="stringparser">The <b><tt>parser&lt;string&gt;</tt>
1683specialization</b></a> simply stores the parsed string into the string value
1684specified. No conversion or modification of the data is performed.</li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001685
Misha Brukman9718e962003-10-24 19:59:21 +00001686<li><a name="intparser">The <b><tt>parser&lt;int&gt;</tt> specialization</b></a>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001687uses the C <tt>strtol</tt> function to parse the string input. As such, it will
1688accept a decimal number (with an optional '+' or '-' prefix) which must start
1689with a non-zero digit. It accepts octal numbers, which are identified with a
1690'<tt>0</tt>' prefix digit, and hexadecimal numbers with a prefix of
Misha Brukman9718e962003-10-24 19:59:21 +00001691'<tt>0x</tt>' or '<tt>0X</tt>'.</li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001692
Misha Brukman9718e962003-10-24 19:59:21 +00001693<li><a name="doubleparser">The <b><tt>parser&lt;double&gt;</tt></b></a> and
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001694<b><tt>parser&lt;float&gt;</tt> specializations</b> use the standard C
1695<tt>strtod</tt> function to convert floating point strings into floating point
1696values. As such, a broad range of string formats is supported, including
1697exponential notation (ex: <tt>1.7e15</tt>) and properly supports locales.
Misha Brukman9718e962003-10-24 19:59:21 +00001698</li>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001699
Misha Brukman9718e962003-10-24 19:59:21 +00001700</ul>
Chris Lattner209c7f42001-07-23 23:03:12 +00001701
Misha Brukman9718e962003-10-24 19:59:21 +00001702</div>
Chris Lattner209c7f42001-07-23 23:03:12 +00001703
1704<!-- *********************************************************************** -->
Misha Brukman9718e962003-10-24 19:59:21 +00001705<div class="doc_section">
1706 <a name="extensionguide">Extension Guide</a>
1707</div>
Chris Lattner209c7f42001-07-23 23:03:12 +00001708<!-- *********************************************************************** -->
1709
Misha Brukman9718e962003-10-24 19:59:21 +00001710<div class="doc_text">
1711
1712<p>Although the CommandLine library has a lot of functionality built into it
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001713already (as discussed previously), one of its true strengths lie in its
1714extensibility. This section discusses how the CommandLine library works under
Misha Brukman9718e962003-10-24 19:59:21 +00001715the covers and illustrates how to do some simple, common, extensions.</p>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001716
Misha Brukman9718e962003-10-24 19:59:21 +00001717</div>
Chris Lattner209c7f42001-07-23 23:03:12 +00001718
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001719<!-- ======================================================================= -->
Misha Brukman9718e962003-10-24 19:59:21 +00001720<div class="doc_subsection">
1721 <a name="customparser">Writing a custom parser</a>
1722</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001723
Misha Brukman9718e962003-10-24 19:59:21 +00001724<div class="doc_text">
1725
1726<p>One of the simplest and most common extensions is the use of a custom parser.
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001727As <a href="#builtinparsers">discussed previously</a>, parsers are the portion
1728of the CommandLine library that turns string input from the user into a
Misha Brukman9718e962003-10-24 19:59:21 +00001729particular parsed data type, validating the input in the process.</p>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001730
Misha Brukman9718e962003-10-24 19:59:21 +00001731<p>There are two ways to use a new parser:</p>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001732
1733<ol>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001734
Misha Brukman9718e962003-10-24 19:59:21 +00001735<li>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001736
Misha Brukman9718e962003-10-24 19:59:21 +00001737<p>Specialize the <a href="#genericparser"><tt>cl::parser</tt></a> template for
1738your custom data type.<p>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001739
Misha Brukman9718e962003-10-24 19:59:21 +00001740<p>This approach has the advantage that users of your custom data type will
1741automatically use your custom parser whenever they define an option with a value
1742type of your data type. The disadvantage of this approach is that it doesn't
1743work if your fundemental data type is something that is already supported.</p>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001744
Misha Brukman9718e962003-10-24 19:59:21 +00001745</li>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001746
Misha Brukman9718e962003-10-24 19:59:21 +00001747<li>
1748
1749<p>Write an independent class, using it explicitly from options that need
1750it.</p>
1751
1752<p>This approach works well in situations where you would line to parse an
1753option using special syntax for a not-very-special data-type. The drawback of
1754this approach is that users of your parser have to be aware that they are using
1755your parser, instead of the builtin ones.</p>
1756
1757</li>
1758
1759</ol>
1760
1761<p>To guide the discussion, we will discuss a custom parser that accepts file
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001762sizes, specified with an optional unit after the numeric size. For example, we
1763would like to parse "102kb", "41M", "1G" into the appropriate integer value. In
1764this case, the underlying data type we want to parse into is
1765'<tt>unsigned</tt>'. We choose approach #2 above because we don't want to make
Misha Brukman9718e962003-10-24 19:59:21 +00001766this the default for all <tt>unsigned</tt> options.</p>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001767
Misha Brukman9718e962003-10-24 19:59:21 +00001768<p>To start out, we declare our new <tt>FileSizeParser</tt> class:</p>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001769
Misha Brukmanf75c4b42005-03-11 00:00:33 +00001770<div class="doc_code"><pre>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001771<b>struct</b> FileSizeParser : <b>public</b> cl::basic_parser&lt;<b>unsigned</b>&gt; {
1772 <i>// parse - Return true on error.</i>
1773 <b>bool</b> parse(cl::Option &amp;O, <b>const char</b> *ArgName, <b>const</b> std::string &amp;ArgValue,
1774 <b>unsigned</b> &amp;Val);
1775};
Misha Brukmanf75c4b42005-03-11 00:00:33 +00001776</pre></div>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001777
Misha Brukman9718e962003-10-24 19:59:21 +00001778<p>Our new class inherits from the <tt>cl::basic_parser</tt> template class to
1779fill in the default, boiler plate, code for us. We give it the data type that
1780we parse into (the last argument to the <tt>parse</tt> method so that clients of
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001781our custom parser know what object type to pass in to the parse method (here we
Misha Brukman9718e962003-10-24 19:59:21 +00001782declare that we parse into '<tt>unsigned</tt>' variables.</p>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001783
Misha Brukman9718e962003-10-24 19:59:21 +00001784<p>For most purposes, the only method that must be implemented in a custom
1785parser is the <tt>parse</tt> method. The <tt>parse</tt> method is called
1786whenever the option is invoked, passing in the option itself, the option name,
1787the string to parse, and a reference to a return value. If the string to parse
1788is not well formed, the parser should output an error message and return true.
1789Otherwise it should return false and set '<tt>Val</tt>' to the parsed value. In
1790our example, we implement <tt>parse</tt> as:</p>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001791
Misha Brukmanf75c4b42005-03-11 00:00:33 +00001792<div class="doc_code"><pre>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001793<b>bool</b> FileSizeParser::parse(cl::Option &amp;O, <b>const char</b> *ArgName,
1794 <b>const</b> std::string &amp;Arg, <b>unsigned</b> &amp;Val) {
1795 <b>const char</b> *ArgStart = Arg.c_str();
1796 <b>char</b> *End;
1797
1798 <i>// Parse integer part, leaving 'End' pointing to the first non-integer char</i>
1799 Val = (unsigned)strtol(ArgStart, &amp;End, 0);
1800
1801 <b>while</b> (1) {
1802 <b>switch</b> (*End++) {
Chris Lattnerce5fcc32005-08-22 16:24:25 +00001803 <b>case</b> 0: <b>return</b> false; <i>// No error</i>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001804 <b>case</b> 'i': <i>// Ignore the 'i' in KiB if people use that</i>
1805 <b>case</b> 'b': <b>case</b> 'B': <i>// Ignore B suffix</i>
1806 <b>break</b>;
1807
1808 <b>case</b> 'g': <b>case</b> 'G': Val *= 1024*1024*1024; <b>break</b>;
1809 <b>case</b> 'm': <b>case</b> 'M': Val *= 1024*1024; <b>break</b>;
1810 <b>case</b> 'k': <b>case</b> 'K': Val *= 1024; <b>break</b>;
1811
1812 default:
1813 <i>// Print an error message if unrecognized character!</i>
1814 <b>return</b> O.error(": '" + Arg + "' value invalid for file size argument!");
1815 }
1816 }
1817}
Misha Brukmanf75c4b42005-03-11 00:00:33 +00001818</pre></div>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001819
Misha Brukman9718e962003-10-24 19:59:21 +00001820<p>This function implements a very simple parser for the kinds of strings we are
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001821interested in. Although it has some holes (it allows "<tt>123KKK</tt>" for
1822example), it is good enough for this example. Note that we use the option
1823itself to print out the error message (the <tt>error</tt> method always returns
1824true) in order to get a nice error message (shown below). Now that we have our
Misha Brukman9718e962003-10-24 19:59:21 +00001825parser class, we can use it like this:</p>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001826
Misha Brukmanf75c4b42005-03-11 00:00:33 +00001827<div class="doc_code"><pre>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001828<b>static</b> <a href="#cl::opt">cl::opt</a>&lt;<b>unsigned</b>, <b>false</b>, FileSizeParser&gt;
1829MFS(<i>"max-file-size"</i>, <a href="#cl::desc">cl::desc</a>(<i>"Maximum file size to accept"</i>),
1830 <a href="#cl::value_desc">cl::value_desc</a>("<i>size</i>"));
Misha Brukmanf75c4b42005-03-11 00:00:33 +00001831</pre></div>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001832
Misha Brukman9718e962003-10-24 19:59:21 +00001833<p>Which adds this to the output of our program:</p>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001834
Misha Brukmanf75c4b42005-03-11 00:00:33 +00001835<div class="doc_code"><pre>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001836OPTIONS:
1837 -help - display available options (--help-hidden for more)
1838 ...
1839 <b>-max-file-size=&lt;size&gt; - Maximum file size to accept</b>
Misha Brukmanf75c4b42005-03-11 00:00:33 +00001840</pre></div>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001841
Misha Brukman9718e962003-10-24 19:59:21 +00001842<p>And we can test that our parse works correctly now (the test program just
1843prints out the max-file-size argument value):</p>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001844
Misha Brukmanf75c4b42005-03-11 00:00:33 +00001845<div class="doc_code"><pre>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001846$ ./test
1847MFS: 0
1848$ ./test -max-file-size=123MB
1849MFS: 128974848
1850$ ./test -max-file-size=3G
1851MFS: 3221225472
1852$ ./test -max-file-size=dog
1853-max-file-size option: 'dog' value invalid for file size argument!
Misha Brukmanf75c4b42005-03-11 00:00:33 +00001854</pre></div>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001855
Misha Brukman9718e962003-10-24 19:59:21 +00001856<p>It looks like it works. The error message that we get is nice and helpful,
1857and we seem to accept reasonable file sizes. This wraps up the "custom parser"
1858tutorial.</p>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001859
Misha Brukman9718e962003-10-24 19:59:21 +00001860</div>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001861
1862<!-- ======================================================================= -->
Misha Brukman9718e962003-10-24 19:59:21 +00001863<div class="doc_subsection">
1864 <a name="explotingexternal">Exploiting external storage</a>
1865</div>
Chris Lattnerc1ae40c2002-08-07 18:27:04 +00001866
Misha Brukman9718e962003-10-24 19:59:21 +00001867<div class="doc_text">
Reid Spencerb993feb2004-08-30 05:56:51 +00001868 <p>Several of the LLVM libraries define static <tt>cl::opt</tt> instances that
1869 will automatically be included in any program that links with that library.
1870 This is a feature. However, sometimes it is necessary to know the value of the
1871 command line option outside of the library. In these cases the library does or
1872 should provide an external storage location that is accessible to users of the
1873 library. Examples of this include the <tt>llvm::DebugFlag</tt> exported by the
1874 <tt>lib/Support/Debug.cpp</tt> file and the <tt>llvm::TimePassesIsEnabled</tt>
1875 flag exported by the <tt>lib/VMCore/Pass.cpp</tt> file.</p>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001876
Reid Spencerb993feb2004-08-30 05:56:51 +00001877<p>TODO: complete this section</p>
Misha Brukman9718e962003-10-24 19:59:21 +00001878
1879</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001880
1881<!-- ======================================================================= -->
Misha Brukman9718e962003-10-24 19:59:21 +00001882<div class="doc_subsection">
1883 <a name="dynamicopts">Dynamically adding command line options</a>
1884</div>
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001885
Misha Brukman9718e962003-10-24 19:59:21 +00001886<div class="doc_text">
Chris Lattnere76d4ab2002-08-06 19:36:06 +00001887
Misha Brukman9718e962003-10-24 19:59:21 +00001888<p>TODO: fill in this section</p>
Chris Lattner209c7f42001-07-23 23:03:12 +00001889
Misha Brukman9718e962003-10-24 19:59:21 +00001890</div>
Chris Lattner209c7f42001-07-23 23:03:12 +00001891
Chris Lattner209c7f42001-07-23 23:03:12 +00001892<!-- *********************************************************************** -->
1893
1894<hr>
Misha Brukmanc53aefb2004-05-12 18:42:35 +00001895<address>
1896 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
1897 src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"></a>
1898 <a href="http://validator.w3.org/check/referer"><img
1899 src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!"></a>
1900
1901 <a href="mailto:sabre@nondot.org">Chris Lattner</a><br>
1902 <a href="http://llvm.cs.uiuc.edu">LLVM Compiler Infrastructure</a><br>
Misha Brukman3c299112003-11-07 18:11:14 +00001903 Last modified: $Date$
Misha Brukmanc53aefb2004-05-12 18:42:35 +00001904</address>
Misha Brukman9718e962003-10-24 19:59:21 +00001905
1906</body>
1907</html>