Actually don't see it as a problem. Between the filter language and
expression substitution, exim has a very rich environment that begs for
the type of development I am doing. So far, I have not seen significant
performance problems nor do I expect to. The addition of macros or
variables would greatly help readability. I can fully understand that
the inclusion of the C API and also the ability to use PERL may be
better for some things. But, when working on a small project like mine,
it is often better to proof in a higher level environment and then
solidify to C or PERL once features have become concrete.
I encourage others to chime in. I, for one, am having a wonderful time
working within the exim environment!
-----Original Message-----
From: exim-users-admin@??? [
mailto:exim-users-admin@exim.org] On
Behalf Of Philip Hazel
Sent: Tuesday, August 26, 2003 6:01 AM
To: Keith Goettert
Cc: exim-users@???
Subject: Re: [Exim] Local Variables in Filters
On Sat, 23 Aug 2003, Keith Goettert wrote:
> I have looked for this several times now in the docs. I am pretty
> sure that filters do not support any form of a user defined variable
> and also do not support macros.
>
> 1) Is this true?
Yes.
> 2) Can I add local (scope = filter script) variables to the wish
> list? Even if they are just like the $nx vars. Something that can be
> assigned a string for substitution latter. (Macros would work also)
>
> Why, because my system filter file is getting unreadable with
> repetitions of tests, lookups and expressions. Help!!
You are trying to do things in the filter that were never intended when
the very simple filtering language was designed.
Just adding variables would only fix part of this "problem".
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
Get the Exim 4 book: http://www.uit.co.uk/exim-book
--
## List details at
http://www.exim.org/mailman/listinfo/exim-users Exim
details at
http://www.exim.org/ ##
