Re: KDevelop syntax parser is barely usable
Sven Brauch <mail-ITmcY+a7/[email protected]>
| Newsgroups | gmane.comp.kde.users.kdevelop |
|---|---|
| Message-ID | <1695315.Rolv6Nc01N@schnitzel> |
Hi, On Wednesday, 7 November 2018 12:11:12 CET Steve the Fiddle wrote: > The problem may be in part, due to > Audacity now making more use of C++11, and a little C++14, with more > templates and broader use of "modern" C++ idioms. FWIW, this is almost always a setup problem, usually include paths and/or preprocessor defines not being set up correctly. For CMake, KDevelop is very good at setting this up automatically, for automake much less so. If include paths, compiler flags and definitions are set correctly, KDevelop's parser will be very close to perfect, since it uses clang behind the scenes. It doesn't matter how complex your template code is. Performance is a different topic, but correctness is very good these days. Best, Sven
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEESmKXmTK7vOXjlWrPaMqOOMS7P0sFAlvi0w4ACgkQaMqOOMS7 P0tISA//Y7OHgDbZHu7VDppWHX4y++0T6dCjq5RMHjAvUXn/wbJyTGmiud+1JIzd Oc3iQlq+m61xivCtLn4wY4IfnQGDqiPP1CKVLWU2fdxi8YwOZsATMWrM84Bm9WBd hAjo/4WhM4E76EQ/0JIzLScJ5lrFT68d0bSjtWsXhrq29BNAeu0UHd/qPytE+2Vv 6KTC2yqk/WOO8Rm95OiyO61YIfXKTvJsAhoKAcTQwPKfRgASS/PXLoGPUOVxndDH VTMxhOxv7/P8lkNyLnVwDvb6Ngv62RraGH5Sqm4VdnD3VV7nxwVj/vXtQCu45cIs mBh2rLiot/7QqsCp08xrNk6vcekPjSAwAXKFkzSKKpl/7NCV/xP6u6Su2U1OC4Cv kmSi/Dm6Yf+xFwSaJ7govZ9SffdKxu6bGS2ftqp+ALnLp/VLhS24+esSpW4YXKDC ZbRUBX18DjRc47Y4OGiRo5J7OboxBVa90XZDZe4YWBgZWulmLYLFj5MRBof9dpa3 vliZcVJvPkvnDXO8o+p/ojKH58p18FxKtWNgVcOhNo19v1EVzQWEgU55auX37bgV qi6+91oCzDMQ999H8SJHiPOudnHaZgxM8N8cJX8rFy3DxFCAprZnrATbbK7TNwLc 9Us4fCf948rU/LPrAikJS0NkoM3+O7z0Jre2PSs3n/QGvbmGoM0= =/hG/ -----END PGP SIGNATURE-----