RFC: Version information string vs. version number

[Ole Reinhardt <ole dot reinhardt at thermotemp dot de>]

Hi all,

I'm new to this list and hope I don't ask a just answered question
again, but I could not find this toppic in the archive.

I'm just facing the problem, that newlib 1.16.0 implemented "unsetenv"
as a void function, newlib 1.17.0 implements unsetenv returning int, as
defined by posix.

Our project (http://www.ethernut.de) implements it's own version of
unsetenv, but uses the newlib includes. So I'm searching a way to
determine the used version of newlib on compile time to allow two
different implementations of "unsetenv".

newlib.h defines _NEWLIB_VERSION as string, so it can't be checked by
the C preprocessor.

I'd like to vote for a versioning system like the linux kernel uses by
defining a number and macros to request the major / minor versions along
with the string representation.

Regards,

Ole Reinhardt

-- 

Mit freundlichen Grüßen
ThermoTemp GmbH
Ole Reinhardt

Geschäftsstelle Siegen - Steinstraße 67 - D-57072 Siegen - 
tel 0271 5513597, 0271-73681 - fax 0271 736 97

Hauptsitz - Hademarscher Weg 7 - 13503 Berlin
tel 030 4315205 - fax 030 43665002
Geschäftsführer: Jörg Friedrichs, Ole Reinhardt
Handelregister Berlin Charlottenburg HRB 45978 UstID DE 156329280