Hi Akos,
Akos Balazs wrote:
> Hi all,
>
> there's a funny bug in the OSG_VERSION define in the current 1.x CVS: this
> is currently defined as 010800 (for 1.8 I suppose) but as it's beginning
> with a 0 the compiler assumes that it's an octal number and therefore
> can't really have 8 as digit... Maybe we should switch the number to
> 0x010800? How do other projects cope with it? I've only checked Mesa, that
> seems to have MAJOR, MINOR and PATCH numbers and for the main "version
> code" they are bitshifted and added together appropriately so it never
> begins with 0.
There are also these defines (at least in my 1.x tree - its not up to date):
OSG_MAJOR_VERSION 1
OSG_MINOR_VERSION 6
OSG_RELEASE_VERSION 0
> I'm a bit amused though that nobody else seems to have used it for
> checking the current OpenSG version in applications... :)
:)
For 1.x you can delegate the version checking to osgInit (look at its
definition in OSGBaseFunctions.cpp). In 2 this has been stripped away
right now - I'll open a ticket so it can be readded, unless there are
objections against it.
Carsten
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
