Shared library: breaking ABI compatibility without breaking API compatibility

Is it possible for a pure C-shared library to break ABI compatibility until the API compatibility is broken?

Also, if you write a library A that provides all the API functions of an existing library B with some additional API functions, is this an ABI library compatible with library B?

+4
source share
2 answers

You may have different calling conventions in two libraries implementing the same API if that answers your first question.

: , . . , API ( , A, B ).

+3

: " API" , , .

: , , .

+1

Source: https://habr.com/ru/post/1543517/


All Articles