Date: Sun, 10 Feb 2002 17:20:03 -0800
From: Erik Steffl <[EMAIL PROTECTED]>
[...]
> We currently use yacc (or bison) to parse Sieve scripts; the bytecode
> work isn't currently expected to change this. We basically report the
> parse errors that Yacc gives us.
it often does report it but not always. and test program ignores them!
The test program ignores what?
[...]
2. if sieve does not have good error reporting then how do you debug
the programs that generate sieve files?
Sieve's formal grammar is not particularly difficult; it really isn't
very hard to write a program that correctly generates scripts.
getting the information from cyrus (what's going on, errors etc.) is
the worst part of cyrus, that's not only my opinion, all other people
that I discussed the configuration of cyrus had the same problems.
I agree error reporting could be improved. It's all a matter of time.
note that this is NOT a documentation problem, docs could be better as
well but they are generally fairly OK, this is the problem of programs
reporting their status.
I'd be willing to add some error messages at least in sieve (that's
were it's needed most, IMO), how's the policy on accepting patches?
You send 'em to [EMAIL PROTECTED], we usually apply them or
at least try to communicate what we don't like.
Major features can take some time or might be shunted to the contrib
directory (like drac-auth).
Larry
