<p><a href="https://github.com/ankitpati" class="user-mention">@ankitpati</a>, these are some useful docs for adding parsers from Exuberant CTags project (which Universal CTags is a fork of), I presume they mostly still apply:</p>
<p><a href="http://ctags.sourceforge.net/parser.html">http://ctags.sourceforge.net/parser.html</a><br>
<a href="http://ctags.sourceforge.net/EXTENDING.html">http://ctags.sourceforge.net/EXTENDING.html</a></p>
<p>There's this VIM config file which shows the command-line based custom Swift regex parser some people use (no idea how well it works), which could be ported to a compiled regexp parser as per above docs:</p>
<p><a href="https://github.com/keith/swift.vim/commit/5d5f81483d1ecc611c0dcd2846aab872f02ab074" class="commit-link">keith/swift.vim@<tt>5d5f814</tt></a></p>
<p>According to <a href="https://github.com/b4n" class="user-mention">@b4n</a> the main limitation with a regexp-based parser is that it can't handle stuff like scope information, while a character-based parser can support this since it can maintain own state during the parse, if I understood correctly.</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/pull/1323#issuecomment-269708499">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJ9182Wcu64ZexJo8HMFg_lfabMjoks5rND8SgaJpZM4K85cR">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABDrJ_jLpT09vANU7yXNO8WxsnJRKJlOks5rND8SgaJpZM4K85cR.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/geany/geany/pull/1323#issuecomment-269708499"></link>
  <meta itemprop="name" content="View Pull Request"></meta>
</div>
<meta itemprop="description" content="View this Pull Request on GitHub"></meta>
</div>

<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://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/geany/geany"}},"updates":{"snippets":[{"icon":"PERSON","message":"@codebrainz in #1323: @ankitpati, these are some useful docs for adding parsers from Exuberant CTags project (which Universal CTags is a fork of), I presume they mostly still apply:\r\n\r\nhttp://ctags.sourceforge.net/parser.html\r\nhttp://ctags.sourceforge.net/EXTENDING.html\r\n\r\nThere's this VIM config file which shows the command-line based custom Swift regex parser some people use (no idea how well it works), which could be ported to a compiled regexp parser as per above docs:\r\n\r\nhttps://github.com/keith/swift.vim/commit/5d5f81483d1ecc611c0dcd2846aab872f02ab074\r\n\r\nAccording to @b4n the main limitation with a regexp-based parser is that it can't handle stuff like scope information, while a character-based parser can support this since it can maintain own state during the parse, if I understood correctly."}],"action":{"name":"View Pull Request","url":"https://github.com/geany/geany/pull/1323#issuecomment-269708499"}}}</script>