External/fmt
8
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

FMT_FAST_FAIL

Browse Source 
added [[noreturn]] -- where possible
why is do_throw() used only for MSVC builds?
using fmt::terror for when FTM_THROW was assert(false) before ...
This commit is contained in:
dbj 2019-11-13 07:42:03 +01:00 committed by GitHub
parent 1f918159ed
commit 8d5f9d6d40
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 22 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
include/fmt/format.h
View File

@ -70,29 +70,46 @@
#else
# define FMT_HAS_BUILTIN(x) 0
#endif
FMT_BEGIN_NAMESPACE
// terror == terminating error
[[noreturn]] inline void terror(const char msg_[BUFSIZ]) {
::puts("\n\n\nFast exit on {fmt} error with message: ");
::puts(msg_);
::perror("\nPOSIX error message: ");
std::exit(EXIT_FAILURE);
}
FMT_END_NAMESPACE
#ifndef FMT_THROW
# if FMT_EXCEPTIONS
# if FMT_MSC_VER
//TODO: why is this only for MSVC builds?
FMT_BEGIN_NAMESPACE
namespace internal {
#define FMT_FAST_FAIL 1 /*TODO: remove before relase, here for testing purposes */
#if FMT_FAST_FAIL
template <typename Exception> [[noreturn]] inline void do_throw(const Exception& x) {
terror(x.what());
}
#else
template <typename Exception> inline void do_throw(const Exception& x) {
// Silence unreachable code warnings in MSVC because these are nearly
// impossible to fix in a generic code.
volatile bool b = true;
if (b) throw x;
}
#endif
} // namespace internal
FMT_END_NAMESPACE
# define FMT_THROW(x) fmt::internal::do_throw(x)
//TODO: why is do_throw() only for MSVC builds?
# define FMT_THROW(x) fmt :: internal::do_throw(x)
# else
# define FMT_THROW(x) throw x
# endif
# else
# define FMT_THROW(x) \
do { \
static_cast<void>(sizeof(x)); \
assert(false); \
# define FMT_THROW(x) \
do { \
fmt :: terror(x.what()) \
} while (false)
# endif
#endif