Re: regex, signed chars and 0x80 to 0xFF

2024-12-22 Thread tlaronde
On Sun, Dec 22, 2024 at 12:38:38AM +0100, Roland Illig wrote: > Am 21.12.2024 um 20:21 schrieb tlaro...@kergis.com: > > Problem found: NetBSD's flex doesn't understand the idiom but is used, > > while (pkgsrc) flex-2.6.4 is able to interpret such regex. > > > > Nonetheless, has someone information

Re: regex, signed chars and 0x80 to 0xFF

2024-12-21 Thread Roland Illig
Am 21.12.2024 um 20:21 schrieb tlaro...@kergis.com: > Problem found: NetBSD's flex doesn't understand the idiom but is used, > while (pkgsrc) flex-2.6.4 is able to interpret such regex. > > Nonetheless, has someone information about the handling of negative > chars in a regex (there are discussions

Re: regex, signed chars and 0x80 to 0xFF

2024-12-21 Thread tlaronde
Problem found: NetBSD's flex doesn't understand the idiom but is used, while (pkgsrc) flex-2.6.4 is able to interpret such regex. Nonetheless, has someone information about the handling of negative chars in a regex (there are discussions, here and there, about problems caused by a character as '-1

regex, signed chars and 0x80 to 0xFF

2024-12-21 Thread tlaronde
When trying to compile emulators/wine (pkgsrc), flex chokes with negative range in character class because (BTW, the line reported is incorrect; it reports the line _after_ the error) the regex are like this: NCNameStartChar ([A-Za-z_]|[\xc0-\xd6\xd8-\xf6\xf8-\xff]) Is the problem with signed c