2021-04-25: Debug Prints
If you compile a YSI mode with ?_DEBUG? set, you get a load of information in the compiler window. This macro means that the prints are ONLY included at the correct level and not any other time, so using ?_DEBUG 0? (or none at all) will strip all the print statements from the mode for the best performance.
The number after _DEBUG is the debug level (default 0) and there are 8 levels:
I will warn you - use level 7 VERY rarely, even I try to avoid it as it generates several Mb of log data just for STARTING your server!
To output your own debug prints use P:<number>(message)
If you compile a YSI mode with ?_DEBUG? set, you get a load of information in the compiler window. This macro means that the prints are ONLY included at the correct level and not any other time, so using ?_DEBUG 0? (or none at all) will strip all the print statements from the mode for the best performance.
Quote:
#define _DEBUG 3
#include <YSI_Library\y_whatever>
The number after _DEBUG is the debug level (default 0) and there are 8 levels:
- 0 - No debugging.
- 1 - Show public function calls (callbacks and timers).
- 2 - Show API function calls (main YSI functions).
- 3 - Show stock function calls (secondary YSI functions).
- 4 - Show internal function calls.
- 5 - Show function branches (extra debug information within functions).
- 6 - Show loop repeats (prints within loops).
- 7 - Show extra loops (even more prints in loops).
I will warn you - use level 7 VERY rarely, even I try to avoid it as it generates several Mb of log data just for STARTING your server!
To output your own debug prints use P:<number>(message)
Quote:
P:5("This will be printed at debug levels 5 and higher.");