<p>parsing function parameters was bad idea, i have removed this part, but now if geany know class, then object initialization will not highlighted.</p>

<p>there is C style (class is unknown), it looks like C prototype<br>
<a href="https://cloud.githubusercontent.com/assets/1043873/18670060/000177d0-7f4f-11e6-83c5-d9226cb3e986.png" target="_blank"><img src="https://cloud.githubusercontent.com/assets/1043873/18670060/000177d0-7f4f-11e6-83c5-d9226cb3e986.png" alt="class_unknown" style="max-width:100%;"></a></p>

<p>and this is C++ style (class is known)<br>
<a href="https://cloud.githubusercontent.com/assets/1043873/18670073/11824958-7f4f-11e6-9894-4cc798d6b9ae.png" target="_blank"><img src="https://cloud.githubusercontent.com/assets/1043873/18670073/11824958-7f4f-11e6-9894-4cc798d6b9ae.png" alt="class_known" style="max-width:100%;"></a></p>

<p>there is another idea, if file type GEANY_FILETYPES_CPP or GEANY_FILETYPES_C will be available on Scintilla lexer side , then lexer may change highlighting behavior, for example don't highlight C-style prototypes at all, because they are looks like object initialization, which is used in C++ very often.</p>

<p>for example, don't highlight 'spaceText' part</p>

<div class="highlight highlight-source-c++"><pre>std::string <span class="pl-en">spaceText</span>(virtualSpace, <span class="pl-s"><span class="pl-pds">'</span> <span class="pl-pds">'</span></span>);</pre></div>

<p>what do you think?</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/1231#issuecomment-248289398">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJ2v6W-3K-dFA4NRWEbbb5vdGGyA2ks5qr9RPgaJpZM4J8sOE">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABDrJ6ZaydhEoJvguwqc-ajkaJ9BZew4ks5qr9RPgaJpZM4J8sOE.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-248289398"></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":"@linvinus in #1231: parsing function parameters was bad idea, i have removed this part, but now if geany know class, then object initialization will not highlighted.\r\n\r\nthere is C style (class is unknown), it looks like C prototype\r\n\r\n\r\nand this is C++ style (class is known)\r\n\r\n\r\nthere is another idea, if file type GEANY_FILETYPES_CPP or GEANY_FILETYPES_C will be available on Scintilla lexer side , then lexer may change highlighting behavior, for example don't highlight C-style prototypes at all, because they are looks like object initialization, which is used in C++ very often.\r\n\r\nfor example, don't highlight 'spaceText' part\r\n```C++\r\nstd::string spaceText(virtualSpace, ' ');\r\n```\r\nwhat do you think?\r\n"}],"action":{"name":"View Issue","url":"https://github.com/geany/geany/issues/1231#issuecomment-248289398"}}}</script>