mirror of
https://github.com/triqs/dft_tools
synced 2024-11-01 03:33:50 +01:00
34 lines
964 B
ReStructuredText
34 lines
964 B
ReStructuredText
|
|
.. highlight:: c
|
|
|
|
.. _util_exceptions:
|
|
|
|
Exceptions
|
|
=============
|
|
|
|
|
|
TRIQS defines special exceptions, with the following characteristics :
|
|
|
|
* they derives from std::exceptions
|
|
* their method .what() returns :
|
|
|
|
* the date and time of the exception (useful in long QMC computations...).
|
|
* the file and line where the exception occurred
|
|
* an additionnal error message (see example below). The error behaves like a std::stringstream, one can accumulate any message
|
|
|
|
* their method .what() returns :
|
|
* a complete stack strace of the C++ code at the exception point, with demangling of the function name (on gcc and clang).
|
|
|
|
In addition, we provide a TRIQS_RUNTIME_ERROR macro to throw exception easily, Cf example below.
|
|
|
|
.. warning::
|
|
|
|
For uniformity, it is highly recommended to use these macros when developing for TRIQS.
|
|
|
|
Example:
|
|
|
|
.. triqs_example:: ./exceptions_0.cpp
|
|
The exception can of course be caught :
|
|
|
|
.. triqs_example:: ./exceptions_1.cpp
|