[cfe-dev] Status/Future of libclang

[Jonathan Müller via cfe-dev]

On 09.07.2016 17:27, Jonathan Coe via cfe-dev wrote:
>
> I've written small extensions to libclang and to the python bindings to
> get a code generator I wrote working. If there is a small number of
> missing features maybe you could do the same?

Yes, I should start doing that.

On 09.07.2016 18:13, Reece Dunn via cfe-dev wrote:
 >
 > When I was writing by own libclang python bindings
 > (https://github.com/rhdunn/libclangpy) I had to write custom logic on
 > top of the direct bindings to fix bugs in libclang (e.g.
 > CursorKind_LinkageSpec is not mapped to the API, so `extern "C" ...`
 > does not work) and some support for the newer APIs on older versions of
 > libclang.

Did that as well.


 > I also wrote my own tests for the binding to make sure the APIs worked
 > consistently on the target and later versions of libclang.

Any documentation on how to do that?

 > My verdict was that it was a second class citizen to the unstable C++ 
API.

Seems like it.