[PATCH] D11740: ABI versioning macros for libc++

[Evgeniy Stepanov via cfe-commits]

eugenis added a comment.

> How long is a major and minor ABI version supported?


We don't want to bump major version too often, and we want to support both +1 and -1 of the current major version, along with all possible minor versions.

> When is the major and minor ABI version bumped?


See Abi.rst for very brief description.

> How will maintaining multiple ABI versions affect code complexity and maintainability?


I'm not sure how to answer this. Depends on the feature in question. The logic of selecting features based on the ABI version number should not cause any maintenance burden by itself.

> Should bumping the ABI major version bump the SO version?

>  Should bumping the ABI major version change the include path from include/c++/v1 to include/c++/v2? What kind of clang support do we need to do this?


I've implemented both. We might not need this support now, but it could be useful at the point of v1->v2 migration.


http://reviews.llvm.org/D11740