<html>
<body>
<div style="font-family: Verdana, Arial, Helvetica, Sans-Serif;">
<table bgcolor="#f9f3c9" width="100%" cellpadding="8" style="border: 1px #c9c399 solid;">
<tr>
<td>
This is an automatically generated e-mail. To reply, visit:
<a href="http://git.reviewboard.kde.org/r/103448/">http://git.reviewboard.kde.org/r/103448/</a>
</td>
</tr>
</table>
<br />
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<p style="margin-top: 0;">On December 18th, 2011, 8:41 p.m., <b>Andreas Pakulat</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">How does the parser identify wether the code is C or C++? Currently the parser is C++ only, i.e. it only understands the parts of plain C that are also in C++. If more C support is added there needs to be a way to enable/disable this on a per-file basis so that users do not start using plain-C code that is going through a C++ compiler or vice versa. Otherwise KDevelop would quickly get bugreports about the parser being broken since it does not behave in the same way as the compiler.</pre>
</blockquote>
</blockquote>
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">That's a perfectly valid concern, but then: how does the parser identify whether the code is C++ or C++11? Right now it seems to me that it will gladly parse C++11 initializer lists and lambda functions in C++ code. I agree this issue should be addressed at some point, but we should not push back parser improvements because of that.</pre>
<br />
<p>- Alexandre</p>
<br />
<p>On December 18th, 2011, 12:23 p.m., Alexandre Courbot wrote:</p>
<table bgcolor="#fefadf" width="100%" cellspacing="0" cellpadding="8" style="background-image: url('http://git.reviewboard.kde.org/media/rb/images/review_request_box_top_bg.png'); background-position: left top; background-repeat: repeat-x; border: 1px black solid;">
<tr>
<td>
<div>Review request for KDevelop and Milian Wolff.</div>
<div>By Alexandre Courbot.</div>
<p style="color: grey;"><i>Updated Dec. 18, 2011, 12:23 p.m.</i></p>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Description </h1>
<table width="100%" bgcolor="#ffffff" cellspacing="0" cellpadding="10" style="border: 1px solid #b8b5a0">
<tr>
<td>
<pre style="margin: 0; padding: 0; white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">Parser support for C99 designated initializers
Support C99 initializers in the C++ parser, e.g:
struct foo_t foo = {
.has_cake = true,
.nb_candles = 12,
};
int bar[10] = {
[1] = 15,
[9] = 25,
};</pre>
</td>
</tr>
</table>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Testing </h1>
<table width="100%" bgcolor="#ffffff" cellspacing="0" cellpadding="10" style="border: 1px solid #b8b5a0">
<tr>
<td>
<pre style="margin: 0; padding: 0; white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">Used it for a couple of weeks, ensured the parser tests all pass.</pre>
</td>
</tr>
</table>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Diffs</b> </h1>
<ul style="margin-left: 3em; padding-left: 0;">
<li>languages/cpp/parser/parser.h <span style="color: grey">(ffc3967e9bec09ff56204aab98e8f80ec6b036cf)</span></li>
<li>languages/cpp/parser/parser.cpp <span style="color: grey">(1c9d9e403500f35761ebc6deb737a4a68a53c28d)</span></li>
<li>languages/cpp/parser/tests/test_parser.h <span style="color: grey">(fa92f1ce284df0936724f74f42f9ad6d4b3c97fc)</span></li>
<li>languages/cpp/parser/tests/test_parser.cpp <span style="color: grey">(f747cfa44bdf962be33cf97841fdae739b3e1771)</span></li>
</ul>
<p><a href="http://git.reviewboard.kde.org/r/103448/diff/" style="margin-left: 3em;">View Diff</a></p>
</td>
</tr>
</table>
</div>
</body>
</html>