[asterisk-dev] [Code Review] Correct ast_api_register/unregister_multiple() API calls

Kevin P. Fleming kpfleming at digium.com
Sun Nov 16 19:49:35 CST 2008

Tzafrir Cohen wrote:

> Just to clarify this point: asterisk 1.6.x is never guaranteed to remain
> compatible (API/ABI) to 1.6.(x-1), right?
> And in practice, chances are that it won't be?

Actually, our plan is for it to be API compatible as long as it can
possibly be maintained. This will require making new versions of
existing published API calls when changes are mandated, something we
never did with previous release branches (we just changed them).

ABI compatibility will probably not be achievable in some areas;
specifically those areas where the 'API' consists of direct structure
access like 'struct ast_channel'. In spite of this, we will make a
reasonable effort to maintain ABI compatibility as well.

In some very specific cases (like the one I've posted the review request
for), we may choose to change an API that was added very recently if it
is clearly deficient (of course, it would be better for deficient APIs
to never become part of a release, but mistakes will happen). If this
happens, we won't do it unless we are fairly comfortable that the number
of users of the new API is small , which will mean it will have to have
been added within the past point release or two, at most.

Kevin P. Fleming
Director of Software Technologies
Digium, Inc. - "The Genuine Asterisk Experience" (TM)

More information about the asterisk-dev mailing list