From: Phil Pennock <pdp@exim.org>
Date: Tue, 3 Jan 2012 07:41:57 +0000 (-0500)
Subject: bool{} is false for empty strings
X-Git-Tag: exim-4_80_RC1~95
X-Git-Url: https://vcs.fsf.org/?a=commitdiff_plain;h=8ebb1c9ea93eb27500756a578640d890b53264d3;p=exim.git

bool{} is false for empty strings

fixes bug 1193
reported by Jasen Betts.
---

diff --git a/doc/doc-docbook/spec.xfpt b/doc/doc-docbook/spec.xfpt
index 951cd5286..12d813781 100644
--- a/doc/doc-docbook/spec.xfpt
+++ b/doc/doc-docbook/spec.xfpt
@@ -9871,7 +9871,10 @@ zero.
 This condition turns a string holding a true or false representation into
 a boolean state.  It parses &"true"&, &"false"&, &"yes"& and &"no"&
 (case-insensitively); also positive integer numbers map to true if non-zero,
-false if zero.  Leading and trailing whitespace is ignored.
+false if zero.
+An empty string is treated as false.
+Leading and trailing whitespace is ignored;
+thus a string consisting only of whitespace is false.
 All other string values will result in expansion failure.
 
 When combined with ACL variables, this expansion condition will let you