core.timer: Inhibit debug messages #958
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Print debug messages only when enabled by editing the source file, not when _G.developer_debug is enabled. The debug mode prints a message every time a timer is executed. This could easily produce thousands of messages per second in reasonable applications. This seems appropriate when specifically debugging the timer module but not when enabling a more general debug mode.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Print debug messages only when enabled by editing the
core/timer.luasource file, not when _G.developer_debug is enabled.The debug mode prints a message every time a timer is executed. This could easily produce thousands of messages per second in reasonable applications. This seems appropriate when specifically debugging the timer module but not when enabling a more general debug mode.