Re: Better runtime error messages from SWIG-wrapped code?

Free-wheeling here, could something like the confess clause in Carp (or the logic that drives it) come in useful here? I know that it is able to produce a call-stack traceback ...

Replies are listed 'Best First'.
Re^2: Better runtime error messages from SWIG-wrapped code? by tod222 (Pilgrim) on Oct 15, 2010 at 14:58 UTC
Yes, although I'm not even looking for a stack backtrace. I think a croak would be sufficient to get it out of the .pm wrapper generated by SWIG to the lowest level of the user's code.	[reply]