diff options
author | Craig Scott <craig.scott@crascit.com> | 2019-06-23 11:10:16 (GMT) |
---|---|---|
committer | Craig Scott <craig.scott@crascit.com> | 2019-06-23 11:10:16 (GMT) |
commit | 264612c0135cdd6dbab7dcbe979bc0bbe22191d9 (patch) | |
tree | 4e64432f99d3950dc621d79817eb96711eeb2da7 /Help | |
parent | 5c7880956f9b3daea561c7bf817b27aa47b53dd0 (diff) | |
download | CMake-264612c0135cdd6dbab7dcbe979bc0bbe22191d9.zip CMake-264612c0135cdd6dbab7dcbe979bc0bbe22191d9.tar.gz CMake-264612c0135cdd6dbab7dcbe979bc0bbe22191d9.tar.bz2 |
Help: Typo and grammar fixes in cmake_parse_arguments() docs
Diffstat (limited to 'Help')
-rw-r--r-- | Help/command/cmake_parse_arguments.rst | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/Help/command/cmake_parse_arguments.rst b/Help/command/cmake_parse_arguments.rst index 196d90f..fcd36d0 100644 --- a/Help/command/cmake_parse_arguments.rst +++ b/Help/command/cmake_parse_arguments.rst @@ -55,17 +55,17 @@ For the ``<options>`` keywords, these will always be defined, to ``TRUE`` or ``FALSE``, whether the option is in the argument list or not. All remaining arguments are collected in a variable -``<prefix>_UNPARSED_ARGUMENTS`` that will be undefined if all argument -where recognized. This can be checked afterwards to see +``<prefix>_UNPARSED_ARGUMENTS`` that will be undefined if all arguments +were recognized. This can be checked afterwards to see whether your macro was called with unrecognized parameters. -``<one_value_keywords>`` and ``<multi_value_keywords>`` that where given no +``<one_value_keywords>`` and ``<multi_value_keywords>`` that were given no values at all are collected in a variable ``<prefix>_KEYWORDS_MISSING_VALUES`` that will be undefined if all keywords received values. This can be checked -to see if there where keywords without any values given. +to see if there were keywords without any values given. -As an example here a ``my_install()`` macro, which takes similar arguments -as the real :command:`install` command: +Consider the following example macro, ``my_install()``, which takes similar +arguments to the real :command:`install` command: .. code-block:: cmake @@ -99,8 +99,8 @@ the following variables:: You can then continue and process these variables. -Keywords terminate lists of values, e.g. if directly after a -one_value_keyword another recognized keyword follows, this is +Keywords terminate lists of values, e.g. if directly after a +``one_value_keyword`` another recognized keyword follows, this is interpreted as the beginning of the new option. E.g. ``my_install(TARGETS foo DESTINATION OPTIONAL)`` would result in ``MY_INSTALL_DESTINATION`` set to ``"OPTIONAL"``, but as ``OPTIONAL`` |