[Insight-users] Getting PyObject* through to wrapped C++ code

[Bill Hoffman]

We have integrated the PATCH-SET 1 with some minor modifications
that allow it to work with the std::exception and not be an ITK specific
solution, and also we added the code for tcl wrapping as well.  So,
we catch all std::exceptions which ITK exceptions are a sub-class of.

Could you take a look at re-working PATCH2 with SwigExtras.i in mind?
I would like to avoid putting ITK specific code into CableSwig.

Thanks.

-Bill


At 12:26 PM 7/22/2003, Charl P. Botha wrote:
>Hi Bill,
>
>On Tue, 2003-07-22 at 18:10, Bill Hoffman wrote:
>> You may want to look at Wrapping/CSwig/Common/SwigExtras.i.
>> This is a traditional swig input file that is used in the 
>> build of CSwig wrapped ITK.   You may be able to add your typemap
>> code there, or do something similar.
>
>Please see a later mail by me with the subject "[PATCH-SET #2]
>itkPyCommand - a working observer mechanism for ITK Python" where all of
>this has been resolved.
>
>I hope that you can integrate itkPyCommand!
>
>Embarrassingly enough, I didn't run into SwigExtras.i during my analysis
>of the wrapping code and solved the problem differently.  Maybe my
>PREVIOUS patch (the one adding the exception handling for
>itk::ExceptionObject) can be moved here, which would be much cleaner. 
>I'm interested to hear your opinion.
>
>Thanks,
>Charl
>
>-- 
>charl p. botha http://cpbotha . net/ http://visualisation . tudelft . nl/