Discussion:
[omniORB] Preprocessor check for value type support
Peter S. Housel
2007-03-22 08:39:26 UTC
Permalink
Unless I missed it, there doesn't seem to be a preprocessor #define that
would allow determining whether or not value types are supported, i.e.,
that would distinguish between omniORB 4.0.x and 4.1.x. Such a #define
would be useful for things such as the CORBA::omniORB Perl module, to
determine whether or not the bindings are able to support value types
while allowing compilation on both 4.0.x and 4.1.x.
--
Peter S. Housel <***@acm.org>
Duncan Grisby
2007-04-05 21:41:34 UTC
Permalink
Post by Peter S. Housel
Unless I missed it, there doesn't seem to be a preprocessor #define that
would allow determining whether or not value types are supported, i.e.,
that would distinguish between omniORB 4.0.x and 4.1.x. Such a #define
would be useful for things such as the CORBA::omniORB Perl module, to
determine whether or not the bindings are able to support value types
while allowing compilation on both 4.0.x and 4.1.x.
There isn't a preprocessor #define, but there are two functions defined
in the omniORB namespace in include/omniORB4/omniORB.h that return the
version as a string or as a hex encoding of the version. You can write a
program that outputs them if you need it.

Cheers,

Duncan.
--
-- Duncan Grisby --
-- ***@grisby.org --
-- http://www.grisby.org --
Loading...