Lines Matching full:commandline
2 CommandLine 2.0 Library Manual
8 This document describes the CommandLine argument processing library. It will
9 show you how to use it, and what it can do. The CommandLine library uses a
17 CommandLine library to have the following features:
19 #. Speed: The CommandLine library is very quick and uses little resources. The
26 #. Type Safe: As a user of CommandLine, you don't have to worry about
31 #. No subclasses required: To use CommandLine, you instantiate variables that
42 #. Cleaner: CommandLine supports enum and other types directly, meaning that
47 #. Powerful: The CommandLine library supports many different types of arguments,
50 possible because CommandLine is...
52 #. Extensible: It is very simple to add a new argument type to CommandLine.
56 #. Labor Saving: The CommandLine library cuts down on the amount of grunt work
61 #. Capable: The CommandLine library can handle lots of different forms of
67 This document will hopefully let you jump in and start using CommandLine in your
74 This section of the manual runs through a simple CommandLine'ification of a
76 CommandLine library in your own program, and show you some of the cool things it
79 To start out, you need to include the CommandLine header file into your program:
83 #include "llvm/Support/CommandLine.h"
97 system which ones we want, and what type of arguments they are. The CommandLine
103 where to put the output. With the CommandLine library, this is represented like
116 "``cl::list``" template), and tell the CommandLine library that the data
153 argument, the CommandLine library allows for `positional`_ arguments to be
175 Again, the CommandLine library does not require the options to be specified in
182 By simply adding the `cl::Required`_ flag, the CommandLine library will
220 The CommandLine library uses a `different parser`_ for different data types.
268 the CommandLine library also provides primitives to support CommandLine option
318 So far we have seen how the CommandLine library handles builtin types like
333 "``compiler -O3 -O2``". The CommandLine library would not be able to catch
341 To cope with these problems, we can use an enum value, and have the CommandLine
365 with the "``clEnumValEnd``" argument!). The CommandLine library enforces that
466 processes the argument. The CommandLine library supports both forms so that you
528 `cl::OneOrMore`_ modifier to inform the CommandLine library that it is an error
590 program does. To add this to your CommandLine program, simply pass a third
598 cl::ParseCommandLineOptions(argc, argv, " CommandLine compiler example\n\n"
607 **OVERVIEW: CommandLine compiler example
623 Now that you know the basics of how to use the CommandLine library, this section
642 CommandLine library, this would be specified as:
776 CommandLine library, we would specify this as:
823 clients (requiring lots of .cpp files to ``#include CommandLine.h``).
968 category. The CommandLine library specifies defaults for all of these settings
1001 value for this setting allows the CommandLine library to do error checking for
1043 value to be present. In the case of the CommandLine library, a value is either
1113 modifier added to allow the CommandLine library to recognize them. Note that
1126 The CommandLine library does not restrict how you use the **cl::Prefix** or
1131 To do this, the CommandLine library uses a greedy algorithm to parse the input
1210 Despite all of the built-in flexibility, the CommandLine option library really
1259 option instead of having the ``CommandLine`` library print out the usual version
1261 to use the ``CommandLine`` facilities. Such programs should just define a small
1393 CommandLine library uses an instance of ``parser<type>`` if the command line
1398 The CommandLine library provides the following builtin parser specializations,
1409 values, which allows you to use the CommandLine library for all of the error
1456 Although the CommandLine library has a lot of functionality built into it
1458 extensibility. This section discusses how the CommandLine library works under
1469 As `discussed previously`_, parsers are the portion of the CommandLine library
