Hi Neal--
nice find! it's rather ugly, though.
the most straightforward way to resolve it seems to be to say that
sequences in a [] must be non-empty.
This means we don't get to say "[]", but that's ok because we already
have ".", which will handily replace it with the same semantics. We
also don't get to say "[^]". While i don't know how to replicate the
"no match" semantics, i'm also unclear where it could possibly be
useful.
Seems like a sufficient clarification would be:
-A range is a sequence of characters enclosed in '[]'.
+A range is a non-empty sequence of characters enclosed in '[]'.
Are there any implementers or users of the regex spec who see this as a
problem?
Neal, perhaps you want to formally file this as an erratum on rfc4880?
--dkg
signature.asc
Description: PGP signature
_______________________________________________
openpgp mailing list
openpgp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/openpgp