Minor API changes and version numbers
I just spent several hours testing the build on Solaris 8 with the native
compiler, which squawked about a huge number of signed/unsigned character
pointer mismatch warnings that all other compilers ignore.
Cleaning all this up is pretty much done now, but it meant some (char *)
to (unsigned char *) changes that will be visible in the API once this
stuff is merged into a release.
What's the common wisdom here: Does this sort of change require a major
version number increase in the library, or is this sufficiently minor that
it can be incorporated into the next minor library version change?
-MSK
Received on Thu Oct 28 2010 - 02:46:36 PST
This archive was generated by hypermail 2.3.0
: Mon Oct 29 2012 - 23:32:54 PST