<p>Also, using a list of names can indeed highlight more locations, but OTOH it has many other shortcomings:</p>

<ul>
<li>not syntax-based, which you don't currently like for type names: how would it really be different here?</li>
<li>bound to only highlight <em>known</em> names, so like for typenames it's unreliable as a visual clue as it's inconsistent.</li>
<li>as said, requires a way to feed the lexer with a very large list of names (probably at least a few hundred thousands, each names probably about 16 chars long in an optimistic scenario -- who said currently it means building a 2M string?), and the lexer to use that list, both in an efficient enough manner so it can reasonably be done whenever the list of functions names changes (which can happen on every keystroke).</li>
</ul>

<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/1231#issuecomment-247286305">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJ8uhD1IUKouteOmXz3KxGk5hKGlaks5qqRY6gaJpZM4J8sOE">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABDrJ4iVgC-mKJUO1qPSnvsaobL_0zWUks5qqRY6gaJpZM4J8sOE.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/issues/1231#issuecomment-247286305"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue 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":"@b4n in #1231: Also, using a list of names can indeed highlight more locations, but OTOH it has many other shortcomings:\r\n* not syntax-based, which you don't currently like for type names: how would it really be different here?\r\n* bound to only highlight *known* names, so like for typenames it's unreliable as a visual clue as it's inconsistent.\r\n* as said, requires a way to feed the lexer with a very large list of names (probably at least a few hundred thousands, each names probably about 16 chars long in an optimistic scenario -- who said currently it means building a 2M string?), and the lexer to use that list, both in an efficient enough manner so it can reasonably be done whenever the list of functions names changes (which can happen on every keystroke)."}],"action":{"name":"View Issue","url":"https://github.com/geany/geany/issues/1231#issuecomment-247286305"}}}</script>