It would be useful to provide a public API for demangler::demangle. It can demangle typeid names, so it would be handy for debugging and logging even without a stack trace. And it's already portable unlike directly using other demangling APIs.
Ideally the API would be a simple function: std::string backward::demangle(const char *name) (with the returned std::string owning it's char buffer). However that may not work due to memory management issues. So just providing a public name for demangler so that users could construct one would be fine.
It would be useful to provide a public API for
demangler::demangle
. It can demangletypeid
names, so it would be handy for debugging and logging even without a stack trace. And it's already portable unlike directly using other demangling APIs.Ideally the API would be a simple function:
std::string backward::demangle(const char *name)
(with the returnedstd::string
owning it'schar
buffer). However that may not work due to memory management issues. So just providing a public name fordemangler
so that users could construct one would be fine.