On Wed, 2003-10-01 at 13:20, Courier User wrote:
> There are some functions that I would like to see in maildrop's
> filtering language, and I'm wondering how you folks feel about me
> writing these functions and then supplying patches for maildrop?
>
> If there is enough interest in this, I will start work on this right
> away in my spare time. I would then have a prototype ready within a
> week or so.
>
> The following group of functions are intended to replace the
> following type of construct:
>
> INVOKE=`/bin/test -f $FILE 1>/dev/null 2>&1`
> if ( $RETURNCODE != 0 )
> {
> ... etc. ...
> }
>
> The following alternative functions avoid the overhead of forking a
> subprocess, setting up a pipe to capture its output, and then
> discarding the output once the command finishes ... all to simply
> query the process's return code for a true/false value that could be
> gotten much more quickly and easily via a system library function,
> and in some cases, to get a simple side-effect.
>
> isfile(item)
> returns 1 if the named item is an existing file;
> otherwise returns 0
OK for me. Ask Sam if he will include these changes in mainstream
maildrop.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
