You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
logger.cpp is a simple utility that writes events to a file or console. When code is not working right one of the fastest ways to locate the issue is logging.
Ideally logging statements would be removed once code is working but practically there is good reason to leave them in place and control their use with a compiler variable. Currently USE_LOGGING is defined for that purpose. When it is set all logging statements for all of VCC become active and the log becomes flooded with messages that are not of current interest to the developer. I think we shoud add an enhancenent that assigns a value to USE_LOGGING to classify which logging messages that are activated.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
logger.cpp is a simple utility that writes events to a file or console. When code is not working right one of the fastest ways to locate the issue is logging.
Ideally logging statements would be removed once code is working but practically there is good reason to leave them in place and control their use with a compiler variable. Currently USE_LOGGING is defined for that purpose. When it is set all logging statements for all of VCC become active and the log becomes flooded with messages that are not of current interest to the developer. I think we shoud add an enhancenent that assigns a value to USE_LOGGING to classify which logging messages that are activated.
Beta Was this translation helpful? Give feedback.
All reactions