News for hackers. Stuff that matters.
Re:C++11 and The Long-Term Viability Of GCC Questioned by mpyne on Saturday January 26, 2013 @02:53PM (#5121515)
KDevelop has a very sophisticated C++ parser (duchain I think they call it) which even provides semantic information (e.g. you can syntax highlight pointers differently from objects, non-virtual method calls different from virtual, etc.)

Example overview: http://zwabel.wordpress.com/2009/01/08/c-ide-evolution-from-...

Re:C++11 and The Long-Term Viability Of GCC Questioned by vor_ on Saturday January 26, 2013 @08:13PM (#5122613)
But one of the points of Clang's toolability is that you don't have to write your own parser. You can use the compiler's and see what the compiler will see, avoiding inconsistencies as well as unnecessary work.
Re:C++11 and The Long-Term Viability Of GCC Questioned by mpyne on Saturday January 26, 2013 @11:16PM (#5123031)
DUChain actually might even predate Clang from what I've been able to dig up today, but there's a few other points working against Clang supplanting it:

1. DUChain was designed to support multiple languages (since KDevelop does). E.g. there is work going on now to offer first-class JavaScript support in KDevelop, which libclang wouldn't help with.

2. No one has done the work to verify API/ABI compatibility guarantees, porting libclang into DUChain, etc.

There's interest though:

https://bugs.kde.org/show_bug.cgi?id=253650 https://bugs.kde.org/show_bug.cgi?id=172622