Comments on: Better MEX error messages https://undocumentedmatlab.com/articles/better-mex-error-messages?utm_source=rss&utm_medium=rss&utm_campaign=better-mex-error-messages Professional Matlab consulting, development and training Fri, 26 Feb 2016 11:42:29 +0000 hourly 1 https://wordpress.org/?v=6.7.3 By: Pavel Holoborodko https://undocumentedmatlab.com/articles/better-mex-error-messages#comment-370568 Fri, 26 Feb 2016 11:42:29 +0000 http://undocumentedmatlab.com/?p=6287#comment-370568 In reply to Yaroslav.

I guess it will come down to compatibility of setjmp/longjmp used in LIBC, that you compile your MEX against.
(C++ exceptions are implemented through these low-level functions with all the additional things for calling class destructors, etc.)

Cannot say about Fortran though – but probably the situation is similar there.

]]> By: Yaroslav https://undocumentedmatlab.com/articles/better-mex-error-messages#comment-370525 Thu, 25 Feb 2016 18:17:05 +0000 http://undocumentedmatlab.com/?p=6287#comment-370525 A very interesting post. Is this problem persists for compiling MEX with c or Fortran, or is there another behaviour altogether?

]]>