Re: String exceptions in cxx omniidl backend

On Thu, 2010-06-17 at 20:14 +0100, Floris Bruynooghe wrote:

> 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...

As you say, those exceptions are nothing to do with any standards. They
are in fact essentially all assertion failures. If they are ever
encountered, it's because of a bug in the omniidl back-end. I'll
certainly incorporate a patch that removes them, but I'd suggest turning
them into assertions rather than creating exception classes.

Note that some of the ones you list have already been removed in 4.1.4.

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- [email protected]     --
   -- http://www.grisby.org --