[exim-cvs] Two clarifications.

Gitweb: http://git.exim.org/exim.git/commitdiff/a39409651d6f823248380812dd7d01361a3b0169

Commit:     a39409651d6f823248380812dd7d01361a3b0169
Parent:     3b4f55a3467f3c0dc52711f14fb3a593daa93f36
Author:     Phil Pennock <pdp@???>
AuthorDate: Thu Apr 12 01:41:44 2012 -0700
Committer:  Phil Pennock <pdp@???>
CommitDate: Thu Apr 12 01:41:44 2012 -0700

    Two clarifications.

    String expansion, draw more attention to † marking.

    Document the order in which parameters are supplied to relative comparators.
---
 doc/doc-docbook/spec.xfpt |   11 +++++++++++
 1 files changed, 11 insertions(+), 0 deletions(-)

diff --git a/doc/doc-docbook/spec.xfpt b/doc/doc-docbook/spec.xfpt
index ed9b0d7..c1f845e 100644
--- a/doc/doc-docbook/spec.xfpt
+++ b/doc/doc-docbook/spec.xfpt
@@ -8536,6 +8536,13 @@ start of a portion of the string that is interpreted and replaced as described
below in section &<<SECTexpansionitems>>& onwards. Backslash is used as an
escape character, as described in the following section.

+Whether a string is expanded depends upon the context. Usually this is solely
+dependent upon the option for which a value is sought; in this documentation,
+options for which string expansion is performed are marked with &dagger; after
+the data type. ACL rules always expand strings. A couple of expansion
+conditions do not expand some of the brace-delimited branches, for security
+reasons.
+


.section "Literal text in expanded strings" "SECTlittext"
@@ -9917,6 +9924,10 @@ lower case), signifying multiplication by 1024 or 1024*1024, respectively.
As a special case, the numerical value of an empty string is taken as
zero.

+In all cases, a relative comparator OP is testing if <&'string1'&> OP
+<&'string2'&>; the above example is checking if &$message_size$& is larger than
+10M, not if 10M is larger than &$message_size$&.
+

.vitem &*bool&~{*&<&'string'&>&*}*&
.cindex "expansion" "boolean parsing"