[gecode-users] compile-time testing of gecode version
Christian Schulte
cschulte at kth.se
Tue Oct 25 10:16:00 CEST 2011
Hi Denys,
That's okay, if you send me a patch I'll add it to the trunk.
Cheers
Christian
--
Christian Schulte, www.ict.kth.se/~cschulte/
-----Original Message-----
From: users-bounces at gecode.org [mailto:users-bounces at gecode.org] On Behalf
Of Denys Duchier
Sent: Monday, October 24, 2011 9:26 PM
To: users at gecode.org
Subject: [gecode-users] compile-time testing of gecode version
Hi Guys,
unless I missed it, there doesn't seem to be any simple way for a
gecode-using program to have #if/#ifdef sections conditioned on the
version of gecode it is being built against. That's a pain for
portability.
In gecode-python, I just added the macro GECODE_VERSION_NUMBER
which is constructed in the same way as the boost version number:
For version X.Y.Z, the version number is X*100000+Y*100+Z
Would it be objectionable to add such a macro to gecode itself?
Cheers,
--Denys
_______________________________________________
Gecode users mailing list
users at gecode.org
https://www.gecode.org/mailman/listinfo/gecode-users
More information about the users
mailing list