Could this different behaviour be related to the compiler?
Conceivably, yes. I suggest you try an experiment with OWLNext 6.36, as this version supports both Borland C++ 5.5 as well as Visual C++ 2015. That will clarify whether it is a compiler issue.
Also, if the exception is generated within a callback, have a look at the changes regarding exception transport (see [bugs:#230]).
Conceivably, yes. I suggest you try an experiment with OWLNext 6.36, as this version supports both Borland C++ 5.5 as well as Visual C++ 2015. That will clarify whether it is a compiler issue.
Also, if the exception is generated within a callback, have a look at the changes regarding exception transport (see [bugs:#230]).
Related
Bugs:
#230