AnotherFoxGuy/polyvox
1
0
Fork 0
Code Issues Pull Requests Activity

More stripping down of logging macros.

Browse Source
This commit is contained in:
David Williams
2014-01-30 23:18:41 +01:00
parent 906d685f5f
commit f2dd852bd2
1 changed files with 24 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

36
library/PolyVoxCore/include/PolyVoxCore/Impl/Logging.h
View File

@@ -112,9 +112,11 @@ namespace PolyVox
#else
// We don't bother with the do...while(0) construct here as we're not executing multiple statements
// We also don't bother with forcing variables to be 'used'. If this causes a problem then calling
// code can just force them to be used itself in addition to calling the logging macro. Basically
// we just want to reduce the chance of extra code being generated.
#define POLYVOX_LOG_TRACE(message)
#define POLYVOX_LOG_TRACE_IF(condition, message) \
POLYVOX_UNUSED(condition)
#define POLYVOX_LOG_TRACE_IF(condition, message)
#endif
@@ -154,9 +156,11 @@ namespace PolyVox
#else
// We don't bother with the do...while(0) construct here as we're not executing multiple statements
// We also don't bother with forcing variables to be 'used'. If this causes a problem then calling
// code can just force them to be used itself in addition to calling the logging macro. Basically
// we just want to reduce the chance of extra code being generated.
#define POLYVOX_LOG_DEBUG(message)
#define POLYVOX_LOG_DEBUG_IF(condition, message) \
POLYVOX_UNUSED(condition)
#define POLYVOX_LOG_DEBUG_IF(condition, message)
#endif
@@ -196,9 +200,11 @@ namespace PolyVox
#else
// We don't bother with the do...while(0) construct here as we're not executing multiple statements
// We also don't bother with forcing variables to be 'used'. If this causes a problem then calling
// code can just force them to be used itself in addition to calling the logging macro. Basically
// we just want to reduce the chance of extra code being generated.
#define POLYVOX_LOG_INFO(message)
#define POLYVOX_LOG_INFO_IF(condition, message) \
POLYVOX_UNUSED(condition)
#define POLYVOX_LOG_INFO_IF(condition, message)
#endif
@@ -238,9 +244,11 @@ namespace PolyVox
#else
// We don't bother with the do...while(0) construct here as we're not executing multiple statements
// We also don't bother with forcing variables to be 'used'. If this causes a problem then calling
// code can just force them to be used itself in addition to calling the logging macro. Basically
// we just want to reduce the chance of extra code being generated.
#define POLYVOX_LOG_WARNING(message)
#define POLYVOX_LOG_WARNING_IF(condition, message) \
POLYVOX_UNUSED(condition)
#define POLYVOX_LOG_WARNING_IF(condition, message)
#endif
@@ -280,9 +288,11 @@ namespace PolyVox
#else
// We don't bother with the do...while(0) construct here as we're not executing multiple statements
// We also don't bother with forcing variables to be 'used'. If this causes a problem then calling
// code can just force them to be used itself in addition to calling the logging macro. Basically
// we just want to reduce the chance of extra code being generated.
#define POLYVOX_LOG_ERROR(message)
#define POLYVOX_LOG_ERROR_IF(condition, message) \
POLYVOX_UNUSED(condition)
#define POLYVOX_LOG_ERROR_IF(condition, message)
#endif
@@ -322,9 +332,11 @@ namespace PolyVox
#else
// We don't bother with the do...while(0) construct here as we're not executing multiple statements
// We also don't bother with forcing variables to be 'used'. If this causes a problem then calling
// code can just force them to be used itself in addition to calling the logging macro. Basically
// we just want to reduce the chance of extra code being generated.
#define POLYVOX_LOG_FATAL(message)
#define POLYVOX_LOG_FATAL_IF(condition, message) \
POLYVOX_UNUSED(condition)
#define POLYVOX_LOG_FATAL_IF(condition, message)
#endif