[Octave-bug-tracker] [bug #49296] Visual Studio build issue

[Bill Greene]

Follow-up Comment #6, bug #49296 (project octave):

I certainly wouldn't advocate change any across-the-board changes to
how errors are handled in Octave-- now or in the future. But I think of
mex files as basically an "external" C interface to Octave or matlab 
(as opposed to oct files) and so it is worthwhile to provide as much
flexibility as possible to the writers of those.

My thought was just to use the setjmp/longjump (or similar) mechanism only
within the mxErr* functions. I don't know much about the internals of
Octave but I assume there is a place in the code where there is some
data structure conversion and then the mex shared library invoked.
Seems like this would be a good place to set up the setjmp/longjmp
mechanism. Then, once the execution point is no longer in the mex
shared library, a C++ exception can be safely thrown.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?49296>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/