From: Monty Taylor <mordred@in...> - 2007-03-22 08:17:17
I was trolling through the archives to see if a problem I was having had
surfaced. It had, but with no resolution I can see.
I've got a project I'm working on that is building multiple languages
from a single source. I've got the main swig files using SWIG_exception
in places where I need to throw an exception. This is working fine in
the Python and Java code. But apparently, this doesn't actually throw an
exception in Perl, it just sets an error code? And in Perl, you need to
use SWIG_exception_fail? I'd be fine with that, if SWIG_exception_fail
also existed in the other other languages?
Did the patch ever go in for this? Or is development moving down another
path? Suggestions? I'd _really_ prefer not to have to make my own
wrapper macro that calls SWIG_exception unless we're in Perl (or Ruby,
if I read the thread right) in which case we want to call
SWIG_exception_fail... :) )
From: John Lenz <jlenz2@ma...> - 2007-03-25 17:41:22
On 03/22/2007 03:16 AM, Monty Taylor wrote:
> Did the patch ever go in for this? Or is development moving down another
> path? Suggestions? I'd _really_ prefer not to have to make my own
> wrapper macro that calls SWIG_exception unless we're in Perl (or Ruby,
> if I read the thread right) in which case we want to call
> SWIG_exception_fail... :) )
Oops, guess I forgot. I said I was going to change this after the
release, but got tied up in the conversion to subversion...
Notice that you can create an exception.i in your build directory, and
it will automatically overwrite the exception.i in the Lib directory...
But in any case, I just committed a fix to SVN so you don't have to do that.