[Arnt Gulbrandsen]:
Kjetil Torgrim Homme writes:
> good point. most GUI's will only need to understand their own
> Sieve code,
Oh?
sorry, I should say "their own idioms".
When a program is about to parse a sieve script, it cannot know
whether that script was written by itself. Right? That's more or
less a design decision. There's nothing like the postscript
Creator field in sieve.
Because of that, a program cannot enable or disable its 'parse
existing sieve script' command depending on who wrote the sieve
script.
agreed, it must _always_ give a functionally equivalent
representation. if you select "lower case Subject" in one editor, it
may emit
if header :matches "Subject" "*" {
set :lower "_lc" "${1}";
deleteheader "Subject";
addheader "Subject" "${_lc}";
}
it is OK for a different editor to present this differently, say:
lower case content of header Subject and store in variable _lc
delete header Subject
add header Subject with content from variable _lc
I think most users will stick to one editor, or edit the code
directly, so they will be happy even if it lacks advanced code pattern
matching.
--
Kjetil T.