News for hackers. Stuff that matters.
Re:Glibc: [0-9] matches ¼ ١ 2 〣 and others, but not 9 (and o... by js2 on Wednesday July 18, 2018 @01:50PM (#17560515)
It may not be clear till you read all the comments on the bug that the 9 which isn't matched is a FULLWIDTH DIGIT NINE.

If you're using, e.g., [a-fA-F0-9] in any locale other than C/POSIX, you're going to have a bad time.

This is going to cause problems, and it's a shame the developers note this, but then seem to wash their hands of it. Perhaps glibc should do what the programmer means, not what they say. It's obvious the regex above intends to validate hex digits, so glibc should do that, standards (and locale) be damned, unless the programmer explictly opts in to the technically correct behavior. The documentation even says:

> Therefore, using [a-z] does not make much sense except in the C/POSIX locale.

If that range doesn't make sense except in the C/POSIX locale, then why interpret it in any other locale? Come on glibc... help us out here.

$0.02.

Re:Glibc: [0-9] matches ¼ ١ 2 〣 and others, but not 9 (and o... by iforgotpassword on Wednesday July 18, 2018 @06:00PM (#17562430)
At least make the new behavior optional and off by default. Iirc, some languages do this by requiring a modifier to the regexp, like /[0-9]/u
Re:Glibc: [0-9] matches ¼ ١ 2 〣 and others, but not 9 (and o... by zeroimpl on Thursday July 19, 2018 @10:42AM (#17566727)
This suggests the only safe portable way to represent hex is one of these? [1234567890abcdefABCDEF] or [\dabcdefABCDEF] That sucks. Fortunately I don't use C, but I'm worried about this finding its way into other languages...
Re:Glibc: [0-9] matches ¼ ١ 2 〣 and others, but not 9 (and o... by js2 on Thursday July 19, 2018 @11:12AM (#17567045)
For a POSIX regex, the correct way to match a hex digit is to use is [[:xdigit:]].
Re:Glibc: [0-9] matches ¼ ١ 2 〣 and others, but not 9 (and o... by zeroimpl on Thursday July 19, 2018 @07:59PM (#17571411)
Right - would be great if more languages supported that, specifically Javascript.
Re:Glibc: [0-9] matches ¼ ١ 2 〣 and others, but not 9 (and o... by js2 on Friday July 20, 2018 @11:48AM (#17575987)
Javascript defines regex ranges in terms of UTF-16 code units w/no consideration for locale, so you can use [a-fA-F0-9] and it will work as expected.

The issue discussed in this bug is only relevant to POSIX regular expression ranges.

Perhaps you're lamenting that there are so many different flavors of regular expression. I agree. Just the other day I had to give up on using a regex in a CloudFormation template to validate input because I could not get it to work as documented.

Re:Glibc: [0-9] matches ¼ ١ 2 〣 and others, but not 9 (and o... by js2 on Friday July 20, 2018 @12:52PM (#17576696)
Followup. The glibc developers came up with a solution that meets the standards without violating the principle of least surprise.

See https://sourceware.org/bugzilla/show_bug.cgi?id=23393#c28 and https://www.sourceware.org/ml/libc-alpha/2018-07/msg00620.ht...

Re:Glibc: [0-9] matches ¼ ١ 2 〣 and others, but not 9 (and o... by icedchai on Wednesday July 18, 2018 @03:50PM (#17561549)
I agree. I actually thought this bug report was a late April fools joke.
Re:Glibc: [0-9] matches ¼ ١ 2 〣 and others, but not 9 (and o... by emmelaich on Wednesday July 18, 2018 @11:06PM (#17563690)
Absolutely. Using a 'range' should be an actual range, not a category.