On Wed, 2005-07-20 at 16:00 -0700, Ned Freed wrote:
On an unrelated point, the [SIEVE] reference needs to be changed to the
replacement I-D to dodge the "no side-effects in tests" restriction.
well, 3028bis must be published first, anyway, so I'll update the
reference when its done?
Might as well update it now as it is likely that the variables draft
will be approved before 3028bis comes out as an RFC. The RFC Editor
understands how to handle such dependencies and will update the
reference for you.
okay, but I don't know what such a reference should look like. my best
guess:
[SIEVE]
Guenther, P., "Sieve: An Email Filtering Language", Work in Progress
I have one additional suggestion. Thinking about it, I don't like the name
choices here. Specifically, ":quotewildcard" refers to the characters being
quoted and not the context they are being quoted for, while ":quoteregex"
refers to the context they are being quoted for and not the characters being
quoted. How about changing ":quotewildcard" to ":quotematches" so both
names refer to the context?
:quotematches was the original suggested name, and it seems logical in
tandem with :quoteregex, but it sounds awfully misleading on its own.
SET :quotematches "address" "[${1}]"
it's tempting to think that the modifier will only affect the match
variable, IMHO.
the argument to :regex _is_ a "regexp"
the argument to :matches isn't a "match", that's the result, but it
_contains_ wildcards.
one alternative is :quotepattern, but I don't think that's any
clearer. :quotematchespattern is too long...
--
Kjetil T.