[PyQt] sip: extend exception support
Phil Thompson
phil at riverbankcomputing.com
Mon Aug 27 19:15:52 BST 2012
On Mon, 27 Aug 2012 10:18:08 -0700, Matt Newell <newellm at blur.com> wrote:
>>
>> In current hg...
>>
>> %VirtualErrorCode is a new sub-directive of the %Module directive.
>>
>> all_throw_cpp_exception replaced by all_use_VirtualErrorCode.
>>
>> /ThrowsCppException/ replaced by /UsesVirtualErrorCode/.
>>
>> /NoThrowsCppException/ replaced by /NoUsesVirtualErrorCode/.
>>
>> Removed SIPPyException.
>>
>> Phil
>> _______________________________________________
>> PyQt mailing list PyQt at riverbankcomputing.com
>> http://www.riverbankcomputing.com/mailman/listinfo/pyqt
>
> I'm coming in a bit late to this discussion, but I have been maintaining
a
> similar patch for a few years in order to solve the same problem.
>
> Below is the documentation that I wrote for my patch.
>
> I don't know enough about the code you just added to compare the
> approaches,
> but hopefully you can read through these docs(i can try to prepare an
> actual
> patch too if you want) and verify that your changes will allow the same
> level
> of functionality. Specifically my code gives access to the c++ and
python
> objects which allows the error to be handled without throwing a c++
> exception,
> since in my case the calling c++ code does not expect an exception.
The difference is the access to the (not necessarily present) objects. How
are you getting these?
Phil
More information about the PyQt
mailing list