jleung51 / exceptional Goto Github PK

After some thought, I believe that a better way to expose the loggers publicly is to call namespaced functions, which will call the logger(s) (locked away in an unnamed namespace in exceptional.hpp. This will allow for easier documentation of the methods actually used to log messages, and more reliable usage of the loggers.

Using CMake will greatly enhance development and testing (especially when Google Test is added).

Currently, both DemangleType() and DemangleStackBacktrace() do work to demangle a string and parse the result. However, the demangling should be placed into a separate method which they both call, to minimize code duplication.

Google Test is a testing framework for C++ and will simplify testing significantly.

The stack backtrace is described in this issue.

Output can be "demangled" using a GNU library; instructions can be found here and documentation for abi::__cxa_demangle() can be found here.

backtrace() is a function from header execinfo.h which returns the currently active function calls.

Man page here.

Right now the only options are Warning and Error; greater versatility would be nice.

Note: Trace is a lengthier call stack trace.