Lines Matching refs:CommandLine
2 CommandLine 2.0 Library Manual
11 This document describes the CommandLine argument processing library. It will
12 show you how to use it, and what it can do. The CommandLine library uses a
20 CommandLine library to have the following features:
22 #. Speed: The CommandLine library is very quick and uses little resources. The
29 #. Type Safe: As a user of CommandLine, you don't have to worry about
34 #. No subclasses required: To use CommandLine, you instantiate variables that
45 #. Cleaner: CommandLine supports enum and other types directly, meaning that
50 #. Powerful: The CommandLine library supports many different types of arguments,
53 possible because CommandLine is...
55 #. Extensible: It is very simple to add a new argument type to CommandLine.
59 #. Labor Saving: The CommandLine library cuts down on the amount of grunt work
64 #. Capable: The CommandLine library can handle lots of different forms of
70 This document will hopefully let you jump in and start using CommandLine in your
77 This section of the manual runs through a simple CommandLine'ification of a
79 CommandLine library in your own program, and show you some of the cool things it
82 To start out, you need to include the CommandLine header file into your program:
86 #include "llvm/Support/CommandLine.h"
100 system which ones we want, and what type of arguments they are. The CommandLine
106 where to put the output. With the CommandLine library, this is represented like
119 "``cl::list``" template), and tell the CommandLine library that the data
157 argument, the CommandLine library allows for `positional`_ arguments to be
179 Again, the CommandLine library does not require the options to be specified in
186 By simply adding the `cl::Required`_ flag, the CommandLine library will
225 The CommandLine library uses a `different parser`_ for different data types.
273 the CommandLine library also provides primitives to support CommandLine option
323 So far we have seen how the CommandLine library handles builtin types like
338 "``compiler -O3 -O2``". The CommandLine library would not be able to catch
346 To cope with these problems, we can use an enum value, and have the CommandLine
368 are listed in the declaration. The CommandLine library enforces that
467 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
589 program does. To add this to your CommandLine program, simply pass a third
597 cl::ParseCommandLineOptions(argc, argv, " CommandLine compiler example\n\n"
606 **OVERVIEW: CommandLine compiler example
642 OVERVIEW: This is a small program to demo the LLVM CommandLine API
671 Now that you know the basics of how to use the CommandLine library, this section
690 CommandLine library, this would be specified as:
824 CommandLine library, we would specify this as:
871 clients (requiring lots of .cpp files to ``#include CommandLine.h``).
1046 category. The CommandLine library specifies defaults for all of these settings
1079 value for this setting allows the CommandLine library to do error checking for
1121 value to be present. In the case of the CommandLine library, a value is either
1191 modifier added to allow the CommandLine library to recognize them. Note that
1211 The CommandLine library does not restrict how you use the **cl::Prefix** or
1216 To do this, the CommandLine library uses a greedy algorithm to parse the input
1304 Despite all of the built-in flexibility, the CommandLine option library really
1354 …cl::ParseCommandLineOptions(argc, argv, "This is a small program to demo the LLVM CommandLine API"…
1378 option instead of having the ``CommandLine`` library print out the usual version
1380 to use the ``CommandLine`` facilities. Such programs should just define a small
1534 CommandLine library uses an instance of ``parser<type>`` if the command line
1539 The CommandLine library provides the following builtin parser specializations,
1550 values, which allows you to use the CommandLine library for all of the error
1597 Although the CommandLine library has a lot of functionality built into it
1599 extensibility. This section discusses how the CommandLine library works under
1610 As `discussed previously`_, parsers are the portion of the CommandLine library