3 ms·
I'm not sure what you're saying, when would that be different from what we have today? I don't see why that would be beneficial. You also might want ranges as
by raverbashing 8y ago
I'm not sure what you're saying, when would that be different from what we have today?
I don't see why that would be beneficial. You also might want ranges as [a-fk-z] (for example)
- tzs 8y ago> I'm not sure what you're saying, when would that be different from what we have today? The situation today is that "[a-z]" is undefined by POSIX if you are not in the POSIX locale. I'm suggesting that it, and similar cases, should be made defined in all locales that include a, b, c, d, e, f, g, h, i, j, k, l, m, n, o, p, q, r, s, t, u, v, w, x, y, and z. > You also might want ranges as [a-fk-z] (for example) Looking back, I wrote unclearly. Where I wrote 'overload items of the form "x-y" in ranges' it would have been better to write 'overload items of the form "x-y" inside bracket expressions'. In "[a-fk-z]" there are two items of that form. Under my suggestions, "a-f" would be replaced with "abcdef" in all locales, and "k-z" would be replaced with "klmnopqrstuvwxyz", giving "[abcdefklmnopqrstuvwxyz]".
- bonzini 8y agoBut would a-z also include for example à and ä, or should 0-9 include ½? (The solution that glibc will implement is to un-interleave lowercase and uppercase characters whenever the collation order is like aàAÀbBcC...).