summaryrefslogtreecommitdiff
path: root/Help
diff options
context:
space:
mode:
authorJuuso "Linda" Lapinlampi <linda@lindalap.fi>2019-02-11 19:06:02 +0000
committerBrad King <brad.king@kitware.com>2019-02-11 14:41:51 -0500
commit572b4fd85b5987858ee6ce6fd7381c3cfd6720e9 (patch)
tree927768c499ae021eb8c226df5c997856d2fe7271 /Help
parent6f23321d405930241fa431cfda7650f2993f0c19 (diff)
downloadcmake-572b4fd85b5987858ee6ce6fd7381c3cfd6720e9.tar.gz
Help: Fix elseif/endif typo
In CMake 3.13.x, we had this evaluation for if() conditions: if(a) elseif(b) else(a) endif(a) The sensible intention of the change in commit c2efb3efcd (Help: Revise docs on Scripting Commands, 2018-10-16, v3.14.0-rc1~505^2) was: > "endif", "endfunction" etc: Explain that the argument is optional and > maintained for compatibility only Instead of "endif", it ended up being written to the documentation as "elseif" by the commit author (oops) to if()'s page. if(a) elseif(a!?) else() endif(a?) Truthfully, endif()'s parameter should be an optional verbatim repeat and not elseif()'s. If it wasn't, elseif() would be described to be the same as if(). The rightful intended description is: if(a) elseif(b) else() endif() Fix that typo.
Diffstat (limited to 'Help')
-rw-r--r--Help/command/if.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Help/command/if.rst b/Help/command/if.rst
index a682c83b1a..a48a0faac6 100644
--- a/Help/command/if.rst
+++ b/Help/command/if.rst
@@ -23,7 +23,7 @@ Otherwise, optional ``elseif`` blocks are processed in the same way.
Finally, if no ``condition`` is true, ``commands`` in the optional ``else``
block are executed.
-Per legacy, the :command:`else` and :command:`elseif` commands admit
+Per legacy, the :command:`else` and :command:`endif` commands admit
an optional ``<condition>`` argument.
If used, it must be a verbatim
repeat of the argument of the opening