Make component loggers inherit settings from global logger #218
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
rplzzz
approved these changes
Jan 17, 2018
| void open( const std::string& logName, const bool echoToScreen, | ||
| LogLevel minLogLevel, const bool echoToFile = true) throw ( h_exception ); | ||
| void open( const std::string& logName, bool echoToScreen, | ||
| bool echoToFile, LogLevel minLogLevel ) throw ( h_exception ); |
There was a problem hiding this comment.
I don't love this scheme for configuring the logger. I've opened issue #221 to fix it up, but it can wait until after this next release.
bpbond
approved these changes
Jan 17, 2018
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.
Until component loggers can be setup using configuration ini-files, this makes it much easier to turn off logging, e.g. in Pyhector. Hector logging output should be unchanged.