Re: case-independent character range match bug, flex 2.5.25

[Bruce Lilly]

Bruce Lilly wrote:
> When given the -i option, flex not only treats upper- and
> lower-case letters identically as individual characters,
> it botches ranges if a specific alphabetic character is
> used in specifying a range:
[...]
> dtext   ([\001-\010\013\014\016-\037!-Z^-\177])
[...]

I can work around this with
dtext   (address@hidden)
but the current flex behavior is counter-intuitive.
Ideally, -i should cause character equivalence only
for A-Z vs. a-z within the first 128 characters. True
case-independence for all 8-bit characters might well
be either horribly expensive (run-time ctype tests of
each input byte) or impossible (mapping of 8-bit bytes
> 128 may vary with locale at run-time, which may well
be different from the locale when flex is run to create
the .c file).