Autor: Pat Lashley Data: Para: Christoph Kliemt, exim-users Assunto: Re: [Exim] improvments to exim
--On Friday, December 19, 2003 11:03:39 +0100 Christoph Kliemt <christoph.kliemt@???> wrote:
>>> You know what I'd like to see on conditions? Looping.
>>>
>>> condition = for i in {1 2 3 4 5} { match {$int_spam_score}{$i}
>>> {yes}{no} }
First off, this probably wouldn't do what you expect, since it
would match anything with a '1', '2', '3', '4', or '5' in it.
So '6' would fail; but '10' and '53' would match.
Second, others have posted ways to do that with existing
>> If Exim configurations are going to get that complicated, I think Tony
>> Finch's suggestion of using an existing language (Tcl)
>
> *argl* tcl... have mercy...
Indeed. Exim already has a compile-time option to include the
perl interpreter, why not just use that? If you want the code
to be visible at the point of use instead of in a perl definition
block; at most you'd need to tweak Exim to allow the use of
anonymous code references ( sub{...} ) instead of subroutine
names in the ${perl ...} string expansions so that the code is
visible at the point of use. (That may already work - I haven't
tested it or looked in the code.)