diff options
| author | Lang Hames <lhames@gmail.com> | 2016-10-25 22:22:48 +0000 |
|---|---|---|
| committer | Lang Hames <lhames@gmail.com> | 2016-10-25 22:22:48 +0000 |
| commit | c468b9c369a70bd4661c79b811d199ed7d2f0864 (patch) | |
| tree | d8d7a3ea0135bc114e546ff2b6015c53a64d634c /docs | |
| parent | ed5107d663c353fc4eff3359cf1434d1ce8d077b (diff) | |
[docs] Fix a couple of typos in the new Error docs.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@285133 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/ProgrammersManual.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/ProgrammersManual.rst b/docs/ProgrammersManual.rst index cc6d3f84d55..d970f1af04e 100644 --- a/docs/ProgrammersManual.rst +++ b/docs/ProgrammersManual.rst @@ -504,7 +504,7 @@ StringError Many kinds of errors have no recovery strategy, the only action that can be taken is to report them to the user so that the user can attempt to fix the environment. In this case representing the error as a string makes perfect -sense. LLVM provides the ``StringError class for this purpose. It takes two +sense. LLVM provides the ``StringError`` class for this purpose. It takes two arguments: A string error message, and an equivalent ``std::error_code`` for interoperability: @@ -582,7 +582,7 @@ Using ExitOnError to simplify tool code """"""""""""""""""""""""""""""""""""""" Library code should never call ``exit`` for a recoverable error, however in tool -code (especially comamnd line tools) this can be a reasonable approach. Calling +code (especially command line tools) this can be a reasonable approach. Calling ``exit`` upon encountering an error dramatically simplifies control flow as the error no longer needs to be propagated up the stack. This allows code to be written in straight-line style, as long as each fallible call is wrapped in a |