Class option_description

boost::program_options::option_description —

Synopsis

class option_description {
public:
  // construct/copy/destruct
  option_description();
  option_description(const char *, const value_semantic *);
  option_description(const char *, const value_semantic *, const char *);
  ~option_description();

  // public member functions
  bool match(const std::string &, bool) const;
  const std::string & key(const std::string &) const;
  const std::string & long_name() const;
  const std::string & description() const;
  shared_ptr< const value_semantic > semantic() const;
  std::string format_name() const;
  std::string format_parameter() const;

  // private member functions
  option_description & set_name(const char *) ;
};

Description

Describes one possible command line/config file option. There are two kinds of properties of an option. First describe it syntactically and are used only to validate input. Second affect interpretation of the option, for example default value for it or function that should be called when the value is finally known. Routines which perform parsing never use second kind of properties -- they are side effect free.

options_description

`option_description` construct/copy/destruct

```
option_description();
```
```
option_description(const char * name, const value_semantic * s);
```
Initializes the object with the passed data.

Note: it would be nice to make the second parameter auto_ptr, to explicitly pass ownership. Unfortunately, it's often needed to create objects of types derived from 'value_semantic': options_description d; d.add_options()("a", parameter<int>("n")->default_value(1)); Here, the static type returned by 'parameter' should be derived from value_semantic.

Alas, derived->base conversion for auto_ptr does not really work, see http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/papers/2000/n1232.pdf http://std.dkuug.dk/jtc1/sc22/wg21/docs/cwg_defects.html#84

So, we have to use plain old pointers. Besides, users are not expected to use the constructor directly.

The 'name' parameter is interpreted by the following rules:
- if there's no "," character in 'name', it specifies long name
- otherwise, the part before "," specifies long name and the part after -- long name.

option_description(const char * name, const value_semantic * s, 
                   const char * description);

Initializes the class with the passed data.

```
~option_description();
```

`option_description` public member functions

```
bool match(const std::string & option, bool approx) const;
```
Given 'option', specified in the input source, return 'true' is 'option' specifies *this.
```
const std::string & key(const std::string & option) const;
```
Return the key that should identify the option, in particular in the variables_map class. The 'option' parameter is the option spelling from the input source. If option name contains '*', returns 'option'. If long name was specified, it's the long name, otherwise it's a short name with prepended '-'.
```
const std::string & long_name() const;
```

const std::string & description() const;

shared_ptr< const value_semantic > semantic() const;

```
std::string format_name() const;
```
```
std::string format_parameter() const;
```
Return the parameter name and properties, formatted suitably for usage message.

`option_description` private member functions

option_description & set_name(const char * name) ;