[cable] [PATCH] Getting itk::exceptions through to Python

[Charl P. Botha]

On Mon, 2003-07-21 at 14:56, Brad King wrote:
> > meaning that when the wrapped ITK code throws an exception, the whole
> > calling process is terminated.  For example:
> 
> CABLE and CableSwig are very different.  CABLE will catch exceptions and
> convert them to Tcl errors, and python is not yet supported.  ITK now uses
> CableSwig instead of CABLE.  This is an ITK issue, and a separate answer
> will be posted to that project's list.

Sorry about that!  I was not sure where exactly CableSwig issues were to
be discussed.  In future, I will keep to the ITK mailing list.

Thanks,
Charl

-- 
charl p. botha http://cpbotha.net/ http://visualisation.tudelft.nl/