Merged
Conversation
The reasoning behind this is that this is not needed for debugging. Filename and line number suffice.
This file contains hidden or 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
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.
Resolves #12.
Will make it into v0.3.0.
To do:
__func__logging (rationale is that filename/line number sufficient).UMBER_LVL_FATALmessages for a class? -> Elegant solution inUMBER_LVL_NEVER.LOG_*macros?UMBER_BLACKLIST/UMBER_WHITELISTenvironment variables or just do everything with the newUMBER_LVLsyntax now. ->UMBER_WHITELISTcan be emulated byUMBER_LVL=*=never,class=verboseandUMBER_BLACKLISTcan be emulated byUMBER_LVL=class=never, so we bing chillin.