Clang API

I have started working recently on a tool to create cross-reference information using clang's libindex instead of using gcc as before. The original API I used can be found at <https://developer.mozilla.org/En/Dehydra/Object_Reference> (it's only a partial documentation; there is a link on that page to a tool which provides a complete dump for any snippet of source code).

Since I have found some of the C API cumbersome to use, I will be using a wrapper internally to provide an API similar to Dehydra's API; I was wondering if you would be interested in accepting this kind of wrapper as a higher-level API than what clang-c currently exposes.

[just one small-time user's comments]

I have started working recently on a tool to create cross-reference
information using clang's libindex instead of using gcc as before. The
original API I used can be found at
<https://developer.mozilla.org/En/Dehydra/Object_Reference> (it's only a
partial documentation; there is a link on that page to a tool which
provides a complete dump for any snippet of source code).

Since I have found some of the C API cumbersome to use, I will be using
a wrapper internally to provide an API similar to Dehydra's API; I was
wondering if you would be interested in accepting this kind of wrapper
as a higher-level API than what clang-c currently exposes.

The Clang-c API isn't perfect, but it seems more "bare bones" than Dehydra's API. For my purposes, that is a good thing, but I understand why others may prefer Dehydra.

Is there a need to put a Dehydra-like API in Clang, or would it suffice
for Clang's documentation to mention your binding? You are planning to keep maintaining Dehydra as a separate project, right?

- Daniel