[PATCH] D12685: Document the stability policy for LLVM-C APIs.

[Eric Christopher via llvm-commits]

>
> What we HAVE now is the LLVM-C API -- and it's actually pretty damn good.
> What it needs is the ability to continue to evolve alongside changes in the
> underlying LLVM library, without being held back (and without threats of
> deletion) due to concerns of exposing "too much" functionality.
>
> That's what this proposal is about.
>
> The minimal effect of a policy here needs to be that LLVM developers are
> comfortable enough to allow new APIs to be added to the LLVM-C API set,
> without objecting each time.
>
>
A specific issue I have with this proposal for what it's worth is the
explosion of functions in the C API. Not the surface area, but the number.
I see a future (perhaps jaded) that looks like a walk through the history
of evolving C++ API as more and more things are wrapped and changed and
rewrapped and changed. That said, I might be picturing it wrong?

-eric
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20150918/b91c6136/attachment.html>