[omniORB-dev] String exceptions in cxx omniidl backend

Floris Bruynooghe flub at devork.be
Thu Jun 17 21:14:04 BST 2010


Hi

The cxx backend of omniidl still uses string exceptions, which no
longer work in Python 2.6 (that was a mistake, they where supposed to
work till 3.x but it's too late now).  These exceptions now raise a
TypeError, which for all practical purposes leaves most code working
since to catch string exceptions you pretty much have to catch all
exceptions anyway.  However it would still be good to get rid of them.

Before I prepare a patch I'd like to know if any of these exceptions
are governed by the OMG standards.  My guess is they aren't since they
only occur in the IDL backend, but I'm not an expert and don't feel
like reading the standards...

Cheers
Floris


PS: The execeptions (with slight offset due to previous version) are:

omniidl_4.1.3-1 E string-literal-exception /usr/share/pyshared/omniidl_be/cxx/ast.py:355
omniidl_4.1.3-1 E string-literal-exception /usr/share/pyshared/omniidl_be/cxx/cxx.py:139
omniidl_4.1.3-1 E string-literal-exception /usr/share/pyshared/omniidl_be/cxx/cxx.py:142
omniidl_4.1.3-1 E string-literal-exception /usr/share/pyshared/omniidl_be/cxx/dynskel/typecode.py:375
omniidl_4.1.3-1 E string-literal-exception /usr/share/pyshared/omniidl_be/cxx/impl/main.py:247
omniidl_4.1.3-1 E string-literal-exception /usr/share/pyshared/omniidl_be/cxx/types.py:786
omniidl_4.1.3-1 E string-literal-exception /usr/share/pyshared/omniidl_be/cxx/types.py:788
omniidl_4.1.3-1 E string-literal-exception /usr/share/pyshared/omniidl_be/cxx/types.py:821
omniidl_4.1.3-1 E string-literal-exception /usr/share/pyshared/omniidl_be/cxx/types.py:856
omniidl_4.1.3-1 E string-literal-exception /usr/share/pyshared/omniidl_be/cxx/util.py:248

-- 
Debian GNU/Linux -- The Power of Freedom
www.debian.org | www.gnu.org | www.kernel.org



More information about the omniORB-dev mailing list