[exim-cvs] bool{} is false for empty strings

Top Page

Reply to this message
Author: Exim Git Commits Mailing List
To: exim-cvs
Subject: [exim-cvs] bool{} is false for empty strings
Gitweb: http://git.exim.org/exim.git/commitdiff/8ebb1c9ea93eb27500756a578640d890b53264d3
Commit:     8ebb1c9ea93eb27500756a578640d890b53264d3
Parent:     4a891427d0a3b443ab636fa6c978d2367d077895
Author:     Phil Pennock <pdp@???>
AuthorDate: Tue Jan 3 02:41:57 2012 -0500
Committer:  Phil Pennock <pdp@???>
CommitDate: Tue Jan 3 02:41:57 2012 -0500

    bool{} is false for empty strings

    fixes bug 1193
    reported by Jasen Betts.
 doc/doc-docbook/spec.xfpt |    5 ++++-
 1 files changed, 4 insertions(+), 1 deletions(-)

diff --git a/doc/doc-docbook/spec.xfpt b/doc/doc-docbook/spec.xfpt
index 951cd52..12d8137 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