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?
You may have different calling conventions in two libraries implementing the same API if that answers your first question.
: , . . , API ( , A, B ).
: " API" , , .
: , , .
Source: https://habr.com/ru/post/1543517/More articles:Difference between Xaml System.Xaml and System.Windows.Markup readers? - c #git rebase: "Unable to apply (hash)". I'm lost - gitHow the java compiler resolves an unimported name - javasqlite3.OperationalError: next to "WHERE": syntax error (Python 2, sqlite3) - pythonКак отправить электронное письмо со стилем в Python3? - pythonHow to catch exceptions in the Units initialization section in Delphi - exception-handlingfor (in) loop index is a string instead of an integer - javascriptHow to git merge squash in Eclipse - gitBlock the presentation of a card management card in a Windows 8.1 phone. - c #Culture-specific resource files not created in Visual Studio 2013 SP2 - visual-studio-2013All Articles