From 7a2c3f0c0ec5b542c89456826adeb56c3cbd7df0 Mon Sep 17 00:00:00 2001 From: Brad King Date: Thu, 8 Jan 2015 13:36:11 -0500 Subject: [PATCH] Help: Clarify if() documentation (#15335) When the variable is not defined the signature is actually accepting a string. Also clarify fall-through from if() case. --- Help/command/if.rst | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/Help/command/if.rst b/Help/command/if.rst index 79e5d21c2..d50b14c8a 100644 --- a/Help/command/if.rst +++ b/Help/command/if.rst @@ -42,11 +42,12 @@ Possible expressions are: or a non-zero number. False if the constant is ``0``, ``OFF``, ``NO``, ``FALSE``, ``N``, ``IGNORE``, ``NOTFOUND``, the empty string, or ends in the suffix ``-NOTFOUND``. Named boolean constants are - case-insensitive. If the argument is not one of these constants, it - is treated as a variable. + case-insensitive. If the argument is not one of these specific + constants, it is treated as a variable or string and the following + signature is used. -``if()`` - True if the variable is defined to a value that is not a false +``if()`` + True if given a variable that is defined to a value that is not a false constant. False otherwise. (Note macro arguments are not variables.) ``if(NOT )``