[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: When to bump library api version (current)

From: Ralf Wildenhues
Subject: Re: When to bump library api version (current)
Date: Thu, 20 May 2010 20:37:29 +0200
User-agent: Mutt/1.5.20 (2009-10-28)


* Adam Mercer wrote on Thu, May 20, 2010 at 06:43:38AM CEST:
> On Wed, May 19, 2010 at 23:36, Daniel Herring wrote:
> > ISTM that this is not an ABI change; the addition of const only affects the
> > code being called, and in a manner compatible with the non-const version
> > (assuming calling code did not expect this parameter to be changed).
> This was my thinking as well, I just wanted to double check as I don't
> want to have an incompatible library api bump unless I really need
> one.

For what it's worth, I wouldn't treat this as an incompatible API bump.
I would mention it to my users though, because when they use function
pointers and assign your library function, the change will show up.

> > That said, C++ compilers do change the name mangling based on constness; so
> > the above argument depends on your code being plain C.
> This code is plain C. Although code written in C++ will link against
> this library but AFAIK that won't be an issue?

No, it won't.  You have to use 'extern "C"' in the headers of course.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]