Alexey Melnikov wrote:
Alexey Melnikov wrote:
Folks,
This is your last chance to review that the document is correct and
complete. No new issues can be raised at this stage unless they are
very serious.
I actually do have one issue with a recent change in -10 which I
consider to be serious, because it broke my Sieve implementation (as
well as CMU's)
> 8.1. Lexical Tokens
>
> Sieve scripts are encoded in UTF-8. The following assumes a valid
> UTF-8 encoding; special characters in Sieve scripts are all US-ASCII.
>
> The following are tokens in Sieve:
>
> - identifiers
> - tags
> - numbers
> - quoted strings
> - multi-line strings
> - other separators
>
> Identifiers, tags, and numbers are case-insensitive, while quoted
> strings and multi-line strings are case-sensitive.
I actually have a problem with *numbers* being case-insensitive. Cyrus
Sieve doesn't accept "k", "m" and "g" prefixes in numbers.
So I would like to poll the WG regarding this issue. Do people want to
make to make number case-insensitive, or should this change be undone?
(In the latter case there is one example in 3028bis-10 which uses
lowercase 'k' now, which has to change)
Obviously, digits are case-insensitive, but by stating "number" this
also includes QUANTIFIER, which only allows uppercase per the ABNF.
I think we should move "numbers" from the case-insensitive list to the
case-sensitive list in order to maintain backwards compatibility.
--
Kenneth Murchison
Project Cyrus Developer/Maintainer
Carnegie Mellon University