summaryrefslogtreecommitdiffstats
path: root/Help
diff options
context:
space:
mode:
authorBrad King <brad.king@kitware.com>2020-02-18 16:25:46 (GMT)
committerKitware Robot <kwrobot@kitware.com>2020-02-18 16:25:52 (GMT)
commit200e81ae1b8858a604caba3cda72155050e35a2e (patch)
treead2829d7607d0257afd2cce033b5bb64cacbc00f /Help
parenta0318e8fc8f65c4c5ee8ffd3e2d886dbe5a2f795 (diff)
parent466b138ea211fc9187965bd52ec68c65da4e9490 (diff)
downloadCMake-200e81ae1b8858a604caba3cda72155050e35a2e.zip
CMake-200e81ae1b8858a604caba3cda72155050e35a2e.tar.gz
CMake-200e81ae1b8858a604caba3cda72155050e35a2e.tar.bz2
Merge topic 'doc-string'
466b138ea2 Help: string: regex match and replace is a subcase of Search&Replace Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4368
Diffstat (limited to 'Help')
-rw-r--r--Help/command/string.rst10
1 files changed, 6 insertions, 4 deletions
diff --git a/Help/command/string.rst b/Help/command/string.rst
index 81a2061..ba7c656 100644
--- a/Help/command/string.rst
+++ b/Help/command/string.rst
@@ -11,8 +11,6 @@ Synopsis
`Search and Replace`_
string(`FIND`_ <string> <substring> <out-var> [...])
string(`REPLACE`_ <match-string> <replace-string> <out-var> <input>...)
-
- `Regular Expressions`_
string(`REGEX MATCH`_ <match-regex> <out-var> <input>...)
string(`REGEX MATCHALL`_ <match-regex> <out-var> <input>...)
string(`REGEX REPLACE`_ <match-regex> <replace-expr> <out-var> <input>...)
@@ -47,6 +45,9 @@ Synopsis
Search and Replace
^^^^^^^^^^^^^^^^^^
+Search and Replace With Plain Strings
+"""""""""""""""""""""""""""""""""""""
+
.. _FIND:
.. code-block:: cmake
@@ -74,8 +75,8 @@ so strings containing multi-byte characters may lead to unexpected results.
Replace all occurrences of ``<match_string>`` in the ``<input>``
with ``<replace_string>`` and store the result in the ``<output_variable>``.
-Regular Expressions
-^^^^^^^^^^^^^^^^^^^
+Search and Replace With Regular Expressions
+"""""""""""""""""""""""""""""""""""""""""""
.. _`REGEX MATCH`:
@@ -87,6 +88,7 @@ Regular Expressions
Match the ``<regular_expression>`` once and store the match in the
``<output_variable>``.
All ``<input>`` arguments are concatenated before matching.
+Regular expressions are specified in the subsection just below.
.. _`REGEX MATCHALL`: