[Zlib-devel] zlib version #define's

[Mark Adler]

On May 15, 2006, at 8:40 PM, William A. Rowe, Jr. wrote:
> If it's specific one-off's later on as the FAQ implies, then it  
> should be
> the fourth segment of the version number in both the .rc and  
> version tags.
> Just because as a win32-developer you are used to the fourth  
> segment being
> a rolling 'build' number (at least, that's how MS uses it) there is no
> reason it cannot correspond to the sub-subversion number in the .h  
> file.

To the extent reasonable, all four parts of the zlib version number  
should be propagated in order to assure that versions are  
distinguishable.  Per the FAQ, the fourth version number  
distinguishes official vs. altered versions.

>> #define ZLIB_VERSION        "1.2.4"
>> #define ZLIB_VERNUM         0x1240
>> #define ZLIB_VER_MAJOR      1
>> #define ZLIB_VER_MINOR      2
>> #define ZLIB_VER_REVISION   4

I much prefer the above to constructing the version id's with complex  
macros.  I believe that I can keep the #define's consistent with  
relatively high probability.

mark