diff options
author | Philip Hazel <ph10@hermes.cam.ac.uk> | 2006-03-02 15:13:59 +0000 |
---|---|---|
committer | Philip Hazel <ph10@hermes.cam.ac.uk> | 2006-03-02 15:13:59 +0000 |
commit | 9c2819b6d70646e789978d88201c1faacfb77df5 (patch) | |
tree | 61623d5b3483c070cae8c5fa75ae37c4b08da4a8 | |
parent | c46782effbf7f5ecde21a8d29cb22b42fda0fe8e (diff) |
Added some musings to the WishList.
-rw-r--r-- | doc/doc-misc/WishList | 30 |
1 files changed, 29 insertions, 1 deletions
diff --git a/doc/doc-misc/WishList b/doc/doc-misc/WishList index 23a597d8a..572a8d5c1 100644 --- a/doc/doc-misc/WishList +++ b/doc/doc-misc/WishList @@ -1,4 +1,4 @@ -$Cambridge: exim/doc/doc-misc/WishList,v 1.62 2006/03/02 12:25:48 ph10 Exp $ +$Cambridge: exim/doc/doc-misc/WishList,v 1.63 2006/03/02 15:13:59 ph10 Exp $ EXIM 4 WISH LIST ---------------- @@ -1969,6 +1969,34 @@ should also defer, for compatibility with ACLs. The natural syntax for this would be to use a regex, like this: ${lookup regex{/some/file regex}{found-string}{not-found-string}} +However, it would be natural to want to use $1 etc in the found-string; this +would be hard because of the lookup caching (if repeated, the lookup won't +actually be done and therefore the numerical variables won't be set), and in +any case, even without caching (and it could, I suppose, be disabled for this +lookup) those variables are not in the right storage pool even if they were +preserved after the lookup. + +An alternative approach might be to implement something like this: + + ${scanfile{/some/file}{sub-expression}} + +where the sub-expression is expanded for every line in the file, with each line +in turn being put into $value. This is like a conditional ${readfile, and in +fact ${readfile could be written using ${scanfile. It would be nice to find a +way of stopping the scan once something has happened. The only thing I can +think of is to invent a variable that changes when scanning a line generates +some non-null text, and then always to stop on a forced failure. That would +allow expressions like this: + + ${scanfile{/some/file} + { + ${if eq{$generated}{}{${if match{regex}{$value}{something}}} fail} + }} + +It's all rather clumsy. Once a line has matched and generated some text, the +next iteration would stop the scan. Another thought: maybe use $scanline +instead of $value (to save confusion) and have $scantext containing everything +that's been generated so far. That sounds pretty flexible. ------------------------------------------------------------------------------ (344) 10-Oct-05 M Make debug_print work in authenticators |