On Fri, 1 Jul 2005 17:37:44 +0100
Phil Thompson <[EMAIL PROTECTED]> wrote:
> If we solve the problem of how to specify "..." then you could define
> std::bad_alloc, std::exception, and (somehow) "..." using %Exception and
> then...
>
> void foo() throw (std::bad_alloc, std::exception, ...
On Friday 01 July 2005 7:55 am, Denis S. Otkidach wrote:
> On Thu, 30 Jun 2005 17:24:27 +0100
>
> Phil Thompson <[EMAIL PROTECTED]> wrote:
> > > 4) There are several standard exceptions which I always have to catch.
> > > Now I have a macro for them:
> > >
> > > #define CATCH_STD_EXCEPTIONS \
> > >
On Fri, 1 Jul 2005 08:54:19 +0100
Phil Thompson <[EMAIL PROTECTED]> wrote:
> Whoops. Change the argument to the strstr() call that checks for
> "sipExceptionRef" from...
>
> xd->raisecode
>
> ...to...
>
> xd->raisecode->frag
Now it works fine, thanks.
--
Denis S. Otkidach
http://www.python.
On Friday 01 July 2005 8:34 am, Denis S. Otkidach wrote:
> On Thu, 30 Jun 2005 17:24:27 +0100
>
> Phil Thompson <[EMAIL PROTECTED]> wrote:
> > > 1) If sipExceptionRef is not used in RaiseCode we'll get a warning.
> >
> > Tonight's snapshot will only generate it if it is used.
>
> Now I get no sipEx
On Thu, 30 Jun 2005 17:24:27 +0100
Phil Thompson <[EMAIL PROTECTED]> wrote:
> > 1) If sipExceptionRef is not used in RaiseCode we'll get a warning.
>
> Tonight's snapshot will only generate it if it is used.
Now I get no sipExceptionRef in catch clause even when it's used in
%RaiseCode.
--
Den
On Thu, 30 Jun 2005 17:24:27 +0100
Phil Thompson <[EMAIL PROTECTED]> wrote:
> > 4) There are several standard exceptions which I always have to catch.
> > Now I have a macro for them:
> >
> > #define CATCH_STD_EXCEPTIONS \
> > catch (std::bad_alloc&) {\
> > PyErr_NoMemory(); \
> >
On Thursday 30 June 2005 10:25 am, Denis S. Otkidach wrote:
> On Wed, 29 Jun 2005 15:59:08 +0100
>
> Phil Thompson <[EMAIL PROTECTED]> wrote:
> > > sip command passes without error, but I have an error when linking:
> > > $OFILES in Makefile contains sipMyModuleMyException.o, while there is
> > > n
On Wed, 29 Jun 2005 15:59:08 +0100
Phil Thompson <[EMAIL PROTECTED]> wrote:
> > sip command passes without error, but I have an error when linking:
> > $OFILES in Makefile contains sipMyModuleMyException.o, while there is no
> > corresponding .cpp file generated.
> >
> > BTW, when I use throw spec
On Wednesday 29 June 2005 3:06 pm, Denis S. Otkidach wrote:
> On Sun, 26 Jun 2005 23:05:33 +0100
>
> Phil Thompson <[EMAIL PROTECTED]> wrote:
> > Support for this is in tonight's snapshot - some changes to what I
> > described above, but nothing sigificant.
> >
> > Support for converting Python exc
On Sun, 26 Jun 2005 23:05:33 +0100
Phil Thompson <[EMAIL PROTECTED]> wrote:
> Support for this is in tonight's snapshot - some changes to what I described
> above, but nothing sigificant.
>
> Support for converting Python exceptions to C++ exceptions in Python
> re-implementations of C++ virtua
On Tuesday 07 June 2005 2:15 pm, Denis S. Otkidach wrote:
> On Tue, 7 Jun 2005 13:30:29 +0100 (BST)
>
> "Phil Thompson" <[EMAIL PROTECTED]> wrote:
> > Ok. How about this...
> >
> > %Exception MyException - will be used with an externally defined
> > exception. (Note, you will not be able to specify
On 6/18/05, Denis S. Otkidach <[EMAIL PROTECTED]> wrote:
> 2) You overwrite virtual method of wrapped class in Python, so that
> other methods (implemented in C++) use it instead of base. This is more
> interesting case, but I believe SIP can't handle it too. Please correct
> me if I'm wrong.
Bi
On Thu, 9 Jun 2005 09:33:22 -0700
James Emerton <[EMAIL PROTECTED]> wrote:
> I think there is a need for biderectional conversion of exceptions.
> I'd like to be able to throw them back into the C++.
>
> In fact, a mechanism that could be enable to check the Python error
> state after calling a
On Thursday 09 June 2005 5:33 pm, James Emerton wrote:
> On 6/7/05, Phil Thompson <[EMAIL PROTECTED]> wrote:
> > So if I introduce something like...
> >
> > %ExceptionType MyException
> > %TypeHeaderCode
> > #include
> > %End
> > %ConvertFromTypeCode
> > // C++ code to return a PyObject instan
On 6/7/05, Phil Thompson <[EMAIL PROTECTED]> wrote:
> So if I introduce something like...
>
> %ExceptionType MyException
> %TypeHeaderCode
> #include
> %End
> %ConvertFromTypeCode
> // C++ code to return a PyObject instance of the exception.
> // sipCpp (the C++ poiter) and sipException_M
On Tue, 7 Jun 2005 13:30:29 +0100 (BST)
"Phil Thompson" <[EMAIL PROTECTED]> wrote:
> Ok. How about this...
>
> %Exception MyException - will be used with an externally defined
> exception. (Note, you will not be able to specify a base exception, but
> why would you want to?)
>
> %Exception MyExc
> On Mon, 6 Jun 2005 17:54:43 +0100
> Phil Thompson <[EMAIL PROTECTED]> wrote:
>
>> SIP's exception support was added by a user - I've never used it myself.
>> Suggestions for improvements always welcome.
>
> I see the following scenario. User creates exception class and expose
> it in module name
On Mon, 6 Jun 2005 17:54:43 +0100
Phil Thompson <[EMAIL PROTECTED]> wrote:
> SIP's exception support was added by a user - I've never used it myself.
> Suggestions for improvements always welcome.
I see the following scenario. User creates exception class and expose
it in module namespace (Plea
On Monday 06 June 2005 5:23 pm, Denis S. Otkidach wrote:
> I hope it's correct place to ask general questions about SIP.
>
> Am I correct that automatic exception handling in SIP is useless? I see
> several problems with it. First, the code for method with signature
> "void error() throw (excepti
19 matches
Mail list logo
