summaryrefslogtreecommitdiff
path: root/src/README.UPDATING
diff options
context:
space:
mode:
authorPhilip Hazel <ph10@hermes.cam.ac.uk>2006-09-26 14:51:02 +0000
committerPhilip Hazel <ph10@hermes.cam.ac.uk>2006-09-26 14:51:02 +0000
commitebc9d865f30116e3acef10e7c25b02bf5cd5cc2c (patch)
treeccecf13fc7b1f6fa03f895584a922923e292b752 /src/README.UPDATING
parentcc2ed8f707b018166d8a778d4c48b6d90a638d1c (diff)
Add comment about {} now being an error in numerical expansion
comparisons. The bug that caused it to be treated as {0} has been fixed.
Diffstat (limited to 'src/README.UPDATING')
-rw-r--r--src/README.UPDATING9
1 files changed, 8 insertions, 1 deletions
diff --git a/src/README.UPDATING b/src/README.UPDATING
index 45822fdef..5d6bfda58 100644
--- a/src/README.UPDATING
+++ b/src/README.UPDATING
@@ -1,4 +1,4 @@
-$Cambridge: exim/src/README.UPDATING,v 1.13 2006/09/25 11:25:37 ph10 Exp $
+$Cambridge: exim/src/README.UPDATING,v 1.14 2006/09/26 14:51:02 ph10 Exp $
This document contains detailed information about incompatibilities that might
be encountered when upgrading from one release of Exim to another. The
@@ -41,6 +41,13 @@ there is no remote transport (possible with a router that sets up host
addresses), $smtp_active_hostname is used. This change is mentioned here in
case somebody is relying on the use of $smtp_active_hostname.
+2. A bug has been fixed that might just possibly be something that is relied on
+in some configurations. In expansion items such as ${if >{xxx}{yyy}...} an
+empty string (that is {}) was being interpreted as if it was {0} and therefore
+treated as the number zero. From release 4.64, such strings cause an error
+because a decimal number, possibly followed by K or M, is required (as has
+always been documented).
+
Exim version 4.63
-----------------