Re: Do opaque struct changes break C library ABIs
On Fri, May 17, 2013 at 2:35 AM, Russ Allbery <rra@debian.org> wrote:
> I have a C shared library that takes a pointer to an opaque struct as the
> first argument to most of its API calls. The internal layout of that
> opaque struct is changing (to add new members). The only way to create
> the opaque state struct is via a call to remctl_new(), which returns a
> pointer to it. Nothing else about the ABI is changing, and client
> programs cannot see or manipulate the struct members directly (at least
> without poking about in memory, of course).
>
> Is that an ABI break that requires an SONAME change?
No, and in case previous answers were not convincing enough, you can
still give a-c-c a try:
http://packages.qa.debian.org/a/abi-compliance-checker.html
2cts
Reply to: