1 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
3 %% Purpose: wxCmdLineParser documentation
4 %% Author: Vadim Zeitlin
8 %% Copyright: (c) Vadim Zeitlin
9 %% License: wxWindows license
10 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
12 \section{\class{wxCmdLineParser
}}\label{wxcmdlineparser
}
14 wxCmdLineParser is a class for parsing the command line.
16 It has the following features:
18 \begin{enumerate
}\itemsep=
0pt
19 \item distinguishes options, switches and parameters; allows option grouping
20 \item allows both short and long options
21 \item automatically generates the usage message from the command line description
22 \item does type checks on the options values (number, date, $
\ldots$).
25 To use it you should follow these steps:
27 \begin{enumerate
}\itemsep=
0pt
28 \item \helpref{construct
}{wxcmdlineparserconstruction
} an object of this class
29 giving it the command line to parse and optionally its description or use
30 {\tt AddXXX()
} functions later
31 \item call
{\tt Parse()
}
32 \item use
{\tt Found()
} to retrieve the results
35 In the documentation below the following terminology is used:
37 \begin{twocollist
}\itemsep=
0pt
38 \twocolitem{switch
}{This is a boolean option which can be given or not, but
39 which doesn't have any value. We use the word switch to distinguish such boolean
40 options from more generic options like those described below. For example,
41 {\tt -v
} might be a switch meaning "enable verbose mode".
}
42 \twocolitem{option
}{Option for us here is something which comes with a value
0
43 unlike a switch. For example,
{\tt -o:filename
} might be an option which allows
44 to specify the name of the output file.
}
45 \twocolitem{parameter
}{This is a required program argument.
}
48 \wxheading{Derived from
}
52 \wxheading{Include files
}
58 \helpref{wxBase
}{librarieslist
}
62 The structure wxCmdLineEntryDesc is used to describe the one command
63 line switch, option or parameter. An array of such structures should be passed
64 to
\helpref{SetDesc()
}{wxcmdlineparsersetdesc
}. Also, the meanings of parameters
65 of the
{\tt AddXXX()
} functions are the same as of the corresponding fields in
69 struct wxCmdLineEntryDesc
71 wxCmdLineEntryType kind;
72 const wxChar *shortName;
73 const wxChar *longName;
74 const wxChar *description;
75 wxCmdLineParamType type;
80 The type of a command line entity is in the
{\tt kind
} field and may be one of
81 the following constants:
85 enum wxCmdLineEntryType
90 wxCMD_LINE_NONE // use this to terminate the list
95 The field
{\tt shortName
} is the usual, short, name of the switch or the option.
96 {\tt longName
} is the corresponding long name or NULL if the option has no long
97 name. Both of these fields are unused for the parameters. Both the short and
98 long option names can contain only letters, digits and the underscores.
100 {\tt description
} is used by the
\helpref{Usage()
}{wxcmdlineparserusage
} method
101 to construct a help message explaining the syntax of the program.
103 The possible values of
{\tt type
} which specifies the type of the value accepted
104 by an option or parameter are:
108 enum wxCmdLineParamType
110 wxCMD_LINE_VAL_STRING, // default
111 wxCMD_LINE_VAL_NUMBER,
118 Finally, the
{\tt flags
} field is a combination of the following bit masks:
124 wxCMD_LINE_OPTION_MANDATORY =
0x01, // this option must be given
125 wxCMD_LINE_PARAM_OPTIONAL =
0x02, // the parameter may be omitted
126 wxCMD_LINE_PARAM_MULTIPLE =
0x04, // the parameter may be repeated
127 wxCMD_LINE_OPTION_HELP =
0x08, // this option is a help request
128 wxCMD_LINE_NEEDS_SEPARATOR =
0x10, // must have sep before the value
133 Notice that by default (i.e. if flags are just $
0$), options are optional (sic)
134 and each call to
\helpref{AddParam()
}{wxcmdlineparseraddparam
} allows one more
135 parameter - this may be changed by giving non-default flags to it, i.e. use
136 {\tt wxCMD
\_LINE\_OPTION\_MANDATORY} to require that the option is given and
137 {\tt wxCMD
\_LINE\_PARAM\_OPTIONAL} to make a parameter optional. Also,
138 {\tt wxCMD
\_LINE\_PARAM\_MULTIPLE} may be specified if the programs accepts a
139 variable number of parameters - but it only can be given for the last parameter
140 in the command line description. If you use this flag, you will probably need to
141 use
\helpref{GetParamCount
}{wxcmdlineparsergetparamcount
} to retrieve the number
142 of parameters effectively specified after calling
143 \helpref{Parse
}{wxcmdlineparserparse
}.
145 The last flag
{\tt wxCMD
\_LINE\_NEEDS\_SEPARATOR} can be specified to require a
146 separator (either a colon, an equal sign or white space) between the option
147 name and its value. By default, no separator is required.
151 \helpref{wxApp::argc
}{wxappargc
} and
\helpref{wxApp::argv
}{wxappargv
}\\
154 %%%%%%%%%%%%% Methods by group %%%%%%%%%%%%%
155 \latexignore{\rtfignore{\wxheading{Function groups
}}}
158 \membersection{Construction
}\label{wxcmdlineparserconstruction
}
160 Before
\helpref{Parse
}{wxcmdlineparserparse
} can be called, the command line
161 parser object must have the command line to parse and also the rules saying
162 which switches, options and parameters are valid - this is called command line
163 description in what follows.
165 You have complete freedom of choice as to when specify the required information,
166 the only restriction is that it must be done before calling
167 \helpref{Parse
}{wxcmdlineparserparse
}.
169 To specify the command line to parse you may use either one of constructors
170 accepting it (
\tt{wxCmdLineParser(argc, argv)
} or
\tt{wxCmdLineParser(const wxString&)
} usually)
171 or, if you use the default constructor, you can do it later by calling
172 \helpref{SetCmdLine
}{wxcmdlineparsersetcmdline
}.
174 The same holds for command line description: it can be specified either in
175 the constructor (
\helpref{without\ command\ line
}{wxcmdlineparserwxcmdlineparser
} or
176 \helpref{together\ with\ it
}{wxcmdlineparserwxcmdlineparserdescargc
}) or
177 constructed later using either
\helpref{SetDesc
}{wxcmdlineparsersetdesc
} or
178 combination of
\helpref{AddSwitch
}{wxcmdlineparseraddswitch
},
179 \helpref{AddOption
}{wxcmdlineparseraddoption
} and
180 \helpref{AddParam
}{wxcmdlineparseraddparam
} methods.
182 Using constructors or
\helpref{SetDesc
}{wxcmdlineparsersetdesc
} uses a (usually
183 {\tt const static
}) table containing the command line description. If you want
184 to decide which options to accept during the run-time, using one of the
185 {\tt AddXXX()
} functions above might be preferable.
188 \membersection{Customization
}\label{wxcmdlineparsercustomization
}
190 wxCmdLineParser has several global options which may be changed by the
191 application. All of the functions described in this section should be called
192 before
\helpref{Parse
}{wxcmdlineparserparse
}.
194 First global option is the support for long (also known as GNU-style) options.
195 The long options are the ones which start with two dashes (
{\tt "--"
}) and look
196 like this:
{\tt --verbose
}, i.e. they generally are complete words and not some
197 abbreviations of them. As long options are used by more and more applications,
198 they are enabled by default, but may be disabled with
199 \helpref{DisableLongOptions
}{wxcmdlineparserdisablelongoptions
}.
201 Another global option is the set of characters which may be used to start an
202 option (otherwise, the word on the command line is assumed to be a parameter).
203 Under Unix,
{\tt '-'
} is always used, but Windows has at least two common
204 choices for this:
{\tt '-'
} and
{\tt '/'
}. Some programs also use
{\tt '+'
}.
205 The default is to use what suits most the current platform, but may be changed
206 with
\helpref{SetSwitchChars
}{wxcmdlineparsersetswitchchars
} method.
208 Finally,
\helpref{SetLogo
}{wxcmdlineparsersetlogo
} can be used to show some
209 application-specific text before the explanation given by
210 \helpref{Usage
}{wxcmdlineparserusage
} function.
213 \membersection{Parsing command line
}\label{wxcmdlineparserparsing
}
215 After the command line description was constructed and the desired options were
216 set, you can finally call
\helpref{Parse
}{wxcmdlineparserparse
} method.
217 It returns $
0$ if the command line was correct and was parsed, $-
1$ if the help
218 option was specified (this is a separate case as, normally, the program will
219 terminate after this) or a positive number if there was an error during the
220 command line parsing.
222 In the latter case, the appropriate error message and usage information are
223 logged by wxCmdLineParser itself using the standard wxWidgets logging functions.
226 \membersection{Getting results
}\label{wxcmdlineparsergettingresults
}
228 After calling
\helpref{Parse
}{wxcmdlineparserparse
} (and if it returned $
0$),
229 you may access the results of parsing using one of overloaded
{\tt Found()
}
232 For a simple switch, you will simply call
233 \helpref{Found
}{wxcmdlineparserfound
} to determine if the switch was given
234 or not, for an option or a parameter, you will call a version of
{\tt Found()
}
235 which also returns the associated value in the provided variable. All
236 {\tt Found()
} functions return true if the switch or option were found in the
237 command line or false if they were not specified.
239 %%%%%%%%%%%%% Methods in alphabetic order %%%%%%%%%%%%%
240 \helponly{\insertatlevel{2}{
247 \membersection{wxCmdLineParser::wxCmdLineParser
}\label{wxcmdlineparserwxcmdlineparserctor
}
249 \func{}{wxCmdLineParser
}{\void}
251 Default constructor. You must use
252 \helpref{SetCmdLine
}{wxcmdlineparsersetcmdline
} later.
254 \func{}{wxCmdLineParser
}{\param{int
}{argc
},
\param{char**
}{argv
}}
256 \func{}{wxCmdLineParser
}{\param{int
}{argc
},
\param{wchar
\_t**
}{argv
}}
258 Constructors which specify the command line to parse. This is the traditional
259 (Unix) command line format. The parameters
{\it argc
} and
{\it argv
} have the
260 same meaning as for
{\tt main()
} function.
262 The second overloaded constructor is only available in Unicode build. The
263 first one is available in both ANSI and Unicode modes because under some
264 platforms the command line arguments are passed as ASCII strings even to
267 \func{}{wxCmdLineParser
}{\param{const wxString\&
}{cmdline
}}
269 Constructor which specify the command line to parse in Windows format. The parameter
270 {\it cmdline
} has the same meaning as the corresponding parameter of
273 \func{}{wxCmdLineParser
}{\param{const wxCmdLineEntryDesc*
}{desc
}}
275 Specifies the
\helpref{command line description
}{wxcmdlineparsersetdesc
} but not the
276 command line. You must use
\helpref{SetCmdLine
}{wxcmdlineparsersetcmdline
} later.
278 \func{}{wxCmdLineParser
}{\param{const wxCmdLineEntryDesc*
}{desc
},
\param{int
}{argc
},
\param{char**
}{argv
}}
280 Specifies both the command line (in Unix format) and the
281 \helpref{command line description
}{wxcmdlineparsersetdesc
}.
283 \func{}{wxCmdLineParser
}{\param{const wxCmdLineEntryDesc*
}{desc
},
\param{const wxString\&
}{cmdline
}}
285 Specifies both the command line (in Windows format) and the
286 \helpref{command line description
}{wxcmdlineparsersetdesc
}.
288 \membersection{wxCmdLineParser::ConvertStringToArgs
}\label{wxcmdlineparserconvertstringtoargs
}
290 \func{static wxArrayString
}{ConvertStringToArgs
}{\param{const wxChar
}{*cmdline
}}
292 Breaks down the string containing the full command line in words. The words are
293 separated by whitespace. The quotes can be used in the input string to quote
294 the white space and the back slashes can be used to quote the quotes.
297 \membersection{wxCmdLineParser::SetCmdLine
}\label{wxcmdlineparsersetcmdline
}
299 \func{void
}{SetCmdLine
}{\param{int
}{argc
},
\param{char**
}{argv
}}
301 \func{void
}{SetCmdLine
}{\param{int
}{argc
},
\param{wchar
\_t**
}{argv
}}
303 Set command line to parse after using one of the constructors which don't do it.
304 The second overload of this function is only available in Unicode build.
306 \func{void
}{SetCmdLine
}{\param{const wxString\&
}{cmdline
}}
308 Set command line to parse after using one of the constructors which don't do it.
312 \membersection{wxCmdLineParser::
\destruct{wxCmdLineParser
}}\label{wxcmdlineparserdtor
}
314 \func{}{\destruct{wxCmdLineParser
}}{\void}
316 Frees resources allocated by the object.
318 {\bf NB:
} destructor is not virtual, don't use this class polymorphically.
321 \membersection{wxCmdLineParser::SetSwitchChars
}\label{wxcmdlineparsersetswitchchars
}
323 \func{void
}{SetSwitchChars
}{\param{const wxString\&
}{switchChars
}}
325 {\it switchChars
} contains all characters with which an option or switch may
326 start. Default is
{\tt "-"
} for Unix,
{\tt "-/"
} for Windows.
329 \membersection{wxCmdLineParser::EnableLongOptions
}\label{wxcmdlineparserenablelongoptions
}
331 \func{void
}{EnableLongOptions
}{\param{bool
}{enable = true
}}
333 Enable or disable support for the long options.
335 As long options are not (yet) POSIX-compliant, this option allows to disable
340 \helpref{Customization
}{wxcmdlineparsercustomization
} and
\helpref{AreLongOptionsEnabled
}{wxcmdlineparserarelongoptionsenabled
}
343 \membersection{wxCmdLineParser::DisableLongOptions
}\label{wxcmdlineparserdisablelongoptions
}
345 \func{void
}{DisableLongOptions
}{\void}
347 Identical to
\helpref{EnableLongOptions(false)
}{wxcmdlineparserenablelongoptions
}.
350 \membersection{wxCmdLineParser::AreLongOptionsEnabled
}\label{wxcmdlineparserarelongoptionsenabled
}
352 \func{bool
}{AreLongOptionsEnabled
}{\void}
354 Returns true if long options are enabled, otherwise false.
358 \helpref{EnableLongOptions
}{wxcmdlineparserenablelongoptions
}
361 \membersection{wxCmdLineParser::SetLogo
}\label{wxcmdlineparsersetlogo
}
363 \func{void
}{SetLogo
}{\param{const wxString\&
}{logo
}}
365 {\it logo
} is some extra text which will be shown by
366 \helpref{Usage
}{wxcmdlineparserusage
} method.
369 \membersection{wxCmdLineParser::SetDesc
}\label{wxcmdlineparsersetdesc
}
371 \func{void
}{SetDesc
}{\param{const wxCmdLineEntryDesc*
}{desc
}}
373 Construct the command line description
375 Take the command line description from the wxCMD
\_LINE\_NONE terminated table.
380 static const wxCmdLineEntryDesc cmdLineDesc
[] =
382 { wxCMD_LINE_SWITCH, "v", "verbose", "be verbose"
},
383 { wxCMD_LINE_SWITCH, "q", "quiet", "be quiet"
},
385 { wxCMD_LINE_OPTION, "o", "output", "output file"
},
386 { wxCMD_LINE_OPTION, "i", "input", "input dir"
},
387 { wxCMD_LINE_OPTION, "s", "size", "output block size", wxCMD_LINE_VAL_NUMBER
},
388 { wxCMD_LINE_OPTION, "d", "date", "output file date", wxCMD_LINE_VAL_DATE
},
390 { wxCMD_LINE_PARAM, NULL, NULL, "input file", wxCMD_LINE_VAL_STRING, wxCMD_LINE_PARAM_MULTIPLE
},
395 wxCmdLineParser parser;
397 parser.SetDesc(cmdLineDesc);
401 \membersection{wxCmdLineParser::AddSwitch
}\label{wxcmdlineparseraddswitch
}
403 \func{void
}{AddSwitch
}{\param{const wxString\&
}{name
},
\param{const wxString\&
}{lng = wxEmptyString
},
\param{const wxString\&
}{desc = wxEmptyString
},
\param{int
}{flags =
0}}
405 Add a switch
{\it name
} with an optional long name
{\it lng
} (no long name if it
406 is empty, which is default), description
{\it desc
} and flags
{\it flags
} to the
407 command line description.
410 \membersection{wxCmdLineParser::AddOption
}\label{wxcmdlineparseraddoption
}
412 \func{void
}{AddOption
}{\param{const wxString\&
}{name
},
\param{const wxString\&
}{lng = wxEmptyString
},
\param{const wxString\&
}{desc = wxEmptyString
},
\param{wxCmdLineParamType
}{type = wxCMD
\_LINE\_VAL\_STRING},
\param{int
}{flags =
0}}
414 Add an option
{\it name
} with an optional long name
{\it lng
} (no long name if
415 it is empty, which is default) taking a value of the given type (string by
416 default) to the command line description.
419 \membersection{wxCmdLineParser::AddParam
}\label{wxcmdlineparseraddparam
}
421 \func{void
}{AddParam
}{\param{const wxString\&
}{desc = wxEmptyString
},
\param{wxCmdLineParamType
}{type = wxCMD
\_LINE\_VAL\_STRING},
\param{int
}{flags =
0}}
423 Add a parameter of the given
{\it type
} to the command line description.
426 \membersection{wxCmdLineParser::Parse
}\label{wxcmdlineparserparse
}
428 \func{int
}{Parse
}{\param{bool
}{giveUsage =
{\tt true
}}}
430 Parse the command line, return $
0$ if ok, $-
1$ if
{\tt "-h"
} or
{\tt "--help"
}
431 option was encountered and the help message was given or a positive value if a
432 syntax error occurred.
434 \wxheading{Parameters
}
436 \docparam{giveUsage
}{If
{\tt true
} (default), the usage message is given if a
437 syntax error was encountered while parsing the command line or if help was
438 requested. If
{\tt false
}, only error messages about possible syntax errors
439 are given, use
\helpref{Usage
}{wxcmdlineparserusage
} to show the usage message
440 from the caller if needed.
}
443 \membersection{wxCmdLineParser::Usage
}\label{wxcmdlineparserusage
}
445 \func{void
}{Usage
}{\void}
447 Give the standard usage message describing all program options. It will use the
448 options and parameters descriptions specified earlier, so the resulting message
449 will not be helpful to the user unless the descriptions were indeed specified.
453 \helpref{SetLogo
}{wxcmdlineparsersetlogo
}
456 \membersection{wxCmdLineParser::Found
}\label{wxcmdlineparserfound
}
458 \constfunc{bool
}{Found
}{\param{const wxString\&
}{name
}}
460 Returns
\true if the given switch was found, false otherwise.
462 \constfunc{bool
}{Found
}{\param{const wxString\&
}{name
},
\param{wxString*
}{value
}}
464 Returns
\true if an option taking a string value was found and stores the
465 value in the provided pointer (which should not be NULL).
467 \constfunc{bool
}{Found
}{\param{const wxString\&
}{name
},
\param{long*
}{value
}}
469 Returns
\true if an option taking an integer value was found and stores
470 the value in the provided pointer (which should not be NULL).
472 \constfunc{bool
}{Found
}{\param{const wxString\&
}{name
},
\param{wxDateTime*
}{value
}}
474 Returns
\true if an option taking a date value was found and stores the
475 value in the provided pointer (which should not be NULL).
478 \membersection{wxCmdLineParser::GetParamCount
}\label{wxcmdlineparsergetparamcount
}
480 \constfunc{size
\_t}{GetParamCount
}{\void}
482 Returns the number of parameters found. This function makes sense mostly if you
483 had used
{\tt wxCMD
\_LINE\_PARAM\_MULTIPLE} flag.
486 \membersection{wxCmdLineParser::GetParam
}\label{wxcmdlineparsergetparam
}
488 \constfunc{wxString
}{GetParam
}{\param{size
\_t }{n =
0u}}
490 Returns the value of Nth parameter (as string only).
494 \helpref{GetParamCount
}{wxcmdlineparsergetparamcount
}