>> Aren't minor numbers supposed to be updated when *new* interfaces
>> are added to a library[?]  For example, I'll be adding float
>> versions of most of the math functions to libm soon -- [...]

> I have to srongly disagree here... Major numbers are updated when any
> part of the interface changes, and minor numbers are updated when
> there are "bug fixes" or non-interface enhancements made to the
> library.

> Your math library shouls then become 1.0 since the interface has
> changed.

I thought it was: major version increments when any existing interface
is changed _incompatibly_, such that programs that expect the old
interface won't work with the new interface.  Minor version increments
for all other changes.

Thus, adding new calls would be a minor-version change.  Changing the
semantics of an existing call would be a major-version change.
Depending on how strongly you feel about the subject (and whether you
object to having minor numbers up in the hundreds or thousands :-),
bugfixes could be minor-version changes or could result in no version
number changes.

					der Mouse

			    mouse@collatz.mcrcim.mcgill.edu

------------------------------------------------------------------------------