<blockquote>
<p>You know what? I actually changed my mind thinking about this lately, and now agree the best way to go is probably just use whatever upstream does. The goal is to use upstream as if it was a library, and actually target making it one that we could simply use.</p>
</blockquote>
<p>Yeah, this is my thinking too and using GNU regex would simplify things. I can try to prepare a patch to get it working on linux - I don't think it will be that hard (unless I run into some unpredictable issues). For windows I guess it means adding</p>
<p><a href="https://github.com/universal-ctags/ctags/tree/master/gnu_regex">https://github.com/universal-ctags/ctags/tree/master/gnu_regex</a></p>
<p>compiling it and using it for regex parsing, right? I'll leave that to someone with better knowledge of building for windows and autotools.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/geany/geany/issues/2119#issuecomment-481867410">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJwaahuUzF1y9a3ds6pTJLd89k-C2ks5vflPVgaJpZM4cgAf5">mute the thread</a>.<img src="https://github.com/notifications/beacon/ABDrJyjz5C4DmabPQY-l5u9BmUvervyHks5vflPVgaJpZM4cgAf5.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/geany/geany","title":"geany/geany","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/geany/geany"}},"updates":{"snippets":[{"icon":"PERSON","message":"@techee in #2119: \u003e You know what? I actually changed my mind thinking about this lately, and now agree the best way to go is probably just use whatever upstream does. The goal is to use upstream as if it was a library, and actually target making it one that we could simply use.\r\n\r\nYeah, this is my thinking too and using GNU regex would simplify things. I can try to prepare a patch to get it working on linux - I don't think it will be that hard (unless I run into some unpredictable issues). For windows I guess it means adding\r\n\r\nhttps://github.com/universal-ctags/ctags/tree/master/gnu_regex\r\n\r\ncompiling it and using it for regex parsing, right? I'll leave that to someone with better knowledge of building for windows and autotools."}],"action":{"name":"View Issue","url":"https://github.com/geany/geany/issues/2119#issuecomment-481867410"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/geany/geany/issues/2119#issuecomment-481867410",
"url": "https://github.com/geany/geany/issues/2119#issuecomment-481867410",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>