debug-log

You can use a DEBUG_LOG macro guarded by a DEBUG flag to add printf-style debug logging that compiles to a no-op in release builds. This provides real-time visibility during development with zero overhead in production code.

The best way to ensure zero overhead is wrapping log statements in a DEBUG_LOG macro that compiles to a no-op when the DEBUG macro is not defined. This completely removes trace points from release builds, eliminating performance penalties.

To initialize printf-style trace points, call the ik_debug_log_init initializer function during setup, then sprinkle DEBUG_LOG statements across your code to emit runtime trace messages while the DEBUG macro is enabled.

Yes, this lightweight debug logging approach works with standard C compilers by relying on compile-time macros. Because it uses a DEBUG guard, it integrates easily into existing C build systems without requiring external dependencies.

You should not use compile-time debug macros if you need runtime-configurable log levels or persistent production logging. The DEBUG_LOG macro is designed exclusively for dev builds and compiles away entirely when DEBUG is undefined.

Yes, you can use DEBUG_LOG macros to gain real-time visibility into program state during execution. By sprinkling these statements across your code, you emit immediate trace messages that help monitor execution flow in dev builds.