Enclose code in documentation in backticks
This commit is contained in:
parent
930f7790fb
commit
d798e00337
1 changed files with 5 additions and 5 deletions
|
|
@ -10,11 +10,11 @@
|
|||
|
||||
//! Simple getopt alternative.
|
||||
//!
|
||||
//! Construct a vector of options, either by using reqopt, optopt, and optflag
|
||||
//! or by building them from components yourself, and pass them to getopts,
|
||||
//! along with a vector of actual arguments (not including argv[0]). You'll
|
||||
//! Construct a vector of options, either by using `reqopt`, `optopt`, and `optflag`
|
||||
//! or by building them from components yourself, and pass them to `getopts`,
|
||||
//! along with a vector of actual arguments (not including `argv[0]`). You'll
|
||||
//! either get a failure code back, or a match. You'll have to verify whether
|
||||
//! the amount of 'free' arguments in the match is what you expect. Use opt_*
|
||||
//! the amount of 'free' arguments in the match is what you expect. Use `opt_*`
|
||||
//! accessors to get argument values out of the matches object.
|
||||
//!
|
||||
//! Single-character options are expected to appear on the command line with a
|
||||
|
|
@ -27,7 +27,7 @@
|
|||
//!
|
||||
//! The following example shows simple command line parsing for an application
|
||||
//! that requires an input file to be specified, accepts an optional output
|
||||
//! file name following -o, and accepts both -h and --help as optional flags.
|
||||
//! file name following `-o`, and accepts both `-h` and `--help` as optional flags.
|
||||
//!
|
||||
//! ~~~{.rust}
|
||||
//! exter mod extra;
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue