From d2b105f216bcebcc02e2d20b74b3726459621c55 Mon Sep 17 00:00:00 2001 From: Alexander Wilms Date: Sun, 14 Jan 2024 13:32:38 +0000 Subject: [PATCH] CLoggerBase: Use IvanSavenko's single-statement macro so that ct100 is not immediately destroyed --- include/vstd/CLoggerBase.h | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/include/vstd/CLoggerBase.h b/include/vstd/CLoggerBase.h index 0012b2dd1..546b3d352 100644 --- a/include/vstd/CLoggerBase.h +++ b/include/vstd/CLoggerBase.h @@ -172,9 +172,10 @@ private: /// Macros for tracing the control flow of the application conveniently. If the LOG_TRACE macro is used it should be /// the first statement in the function. Logging traces via this macro have almost no impact when the trace is disabled. /// -#define RAII_TRACE(logger, onEntry, onLeave) \ - if(logger->isTraceEnabled()) \ - std::unique_ptr ctl00 = std::make_unique(logger, onEntry, onLeave) +#define RAII_TRACE(logger, onEntry, onLeave) \ + std::unique_ptr ctl00 = logger->isTraceEnabled() ? \ + std::make_unique(logger, onEntry, onLeave) : \ + std::unique_ptr() #define LOG_TRACE(logger) RAII_TRACE(logger, \ boost::str(boost::format("Entering %s.") % BOOST_CURRENT_FUNCTION), \