@elextr the annoying part is that it brings an extra bundled copy of GNU Regex for platforms that don't have regcomp() (Windows is the most obvious candidate), yet GLib already does something very similar to provide GRegex. So on some situations we could end with 2 copies of it 😕

Currently we have a GRegex-based version of it, but it's not necessarily 100% compatible, and certainly doesn't have all the new stuff from upstream. The question @techee raises is: is it worth maintaining this for the few parsers that use it? What should we do?
To be fair, the most important use case for upstream is dynamic parser definition (with various command-line switches) allowing to create parsers fairly easily for fairly simple things (although it got more and more powerful lately) -- and we don't have support for this, at least not yet.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.