Jutta Degener wrote:
On Sun, Apr 13, 2003 at 05:53:40PM +0200, Kjetil Torgrim Homme wrote:
[Alexey Melnikov]:
In order to move imapflags extension forward I need support for
set/list variables.
I think we might be able to do without this. What if you allow
(and ignore) empty strings in a [...] list?
That way, you could set
set "aflag" "aflag"
["${aflag}", "${bflag}", "${cflag}"]
and have that come out as
["aflag" "" ""]
if bflag and cflag are unset.
There are still things that you can do with a list algebra
that you can't do with this approach -- infinitely many
flags based on the header and body contents of a message --
but I don't think we want to do those things badly enough
to warrant adding three new commands and a variable data type.
Surely three new actions shouldn't scare you :-).
But I understand the complexity of multiple data types.
Ok, I can live with this.
It seems the only thing required to be said is that empty strings are
ignored in a list that specifies flags to be set.
I should also mention that each list member defines a separate flag and
spaces in flag names are not allowed (due to IMAP restriction).
Cheers,
Alexey
__________________________________________
R & D, ACI Worldwide/MessagingDirect
Watford, UK
Work Phone: +44 1923 81 2877
Home Page: http://orthanc.ab.ca/mel
IETF standard
related pages: http://orthanc.ab.ca/mel/devel/Links.html
I speak for myself only, not for my employer.
__________________________________________