[omniORB] SuSE Linux 9.0 - gcc 3.3.1 compile problem - "False" not defined in omniORB 4.0.1/2

[Duncan Grisby]

On Sunday 16 November, Anthony Schlemmer wrote:

> I went back and looked at a RedHat Enterprise ES 2.1 system and the 
> generated C++ code has a "0" (zero) rather than "False" in it. I guess 
> this progblem may be related to the version of Python being used? On 
> the RedHat box we have Python 1.5.2 and on the SuSE system we have 
> Python 2.3+ running.

The problem was introduced by changes in Python 2.3.

> I also get some warnings when "omniidl" is run as well:
> 
> /opt/omniORB-4.0.2/lib/python2.3/site-packages/omniidl_be/cxx/
> descriptor.py:156: FutureWarning: x<<y losing bits or changing sign 
> will return a long in Python 2.4 and up
>   return x << distance
> /opt/omniORB-4.0.2/lib/python2.3/site-packages/omniidl_be/cxx/
> descriptor.py:218: FutureWarning: %u/%o/%x/%X of negative int will 
> return a signed string in Python 2.4 and up
>   return "%08x" % x

Those are also due to Python 2.3 changes.

Both issues are fixed in CVS, and will be in the imminent 4.0.3
release.

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --