doc_cpp_exceptions.h

)
{
  try 
  {
    // Retrow the original exception so we can catch it again
    throw;
  }
  catch( std::exception &e )
  {
    // Tell the VM the type of exception that occurred
    ctx->SetException(e.what());
  }
  catch(...)
  {
    // The callback must not allow any exception to be thrown, but it is not necessary 
    // to explicitly set an exception string if the default exception string is sufficient
  }
}
 
// Register the callback with the engine
engine->SetTranslateAppExceptionCallback(asFUNCTION(TranslateException), 0, asCALL_CDECL);
\endcode
 
\see \ref doc_addon_helpers "GetExceptionInfo" helper function
 
\note The ability to catch exceptions can be turned off by compiling the library with the AS_NO_EXCEPTIONS defined. If this is done, the application should not register any functions that may throw exceptions, as the end result will be 
undefined should an exception occur.
 
\section doc_cpp_exceptions_2 longjmp
 
Some applications uses longjmp to do error handling. When performing a longjmp to a previously saved state, there is no chance for the code to do a cleanup of all that happened after the saved state. Because of that the application must not register functions that can perform a longjmp out from the function, as that can leave the virtual machine in an undefined state.
 
*/