Re: regex change

In article , enh wrote: >-=-=-=-=-=- > >ah, thanks for that link. stupidly, although i'd seen that the NetBSD >changes were syncing with FreeBSD, i didn't go to look at the original >FreeBSD commits. > >cool, that sounds like i (a) have a clear "why" argument should anyone ask, >and (b) a ready-m

Re: regex change

On Thu, Nov 10, 2022 at 7:44 AM Christos Zoulas wrote: > In article < > cajgzzorydwzwyur9wggdplocxebjnxepmkbiouyxsxdu-jk...@mail.gmail.com>, > enh wrote: > >-=-=-=-=-=- > > > >i see (having synced the current NetBSD lib/libc/regex to Android) that > >regcomp() no longer allows unescaped `{` and

Re: regex change

In article , enh wrote: >-=-=-=-=-=- > >i see (having synced the current NetBSD lib/libc/regex to Android) that >regcomp() no longer allows unescaped `{` and `}`. this is technically >correct (since POSIX explicitly calls this undefined behavior), but it's a >change from historical NetBSD behavio

regex change

i see (having synced the current NetBSD lib/libc/regex to Android) that regcomp() no longer allows unescaped `{` and `}`. this is technically correct (since POSIX explicitly calls this undefined behavior), but it's a change from historical NetBSD behavior. specifically (since this was the existing