Glenn Linderman writes: > 1) simple example for one file programs, include an example of > specifying output severity threshold. I'm with Antoine here on my > expectations. > > 2) example for multi-module, showing how a single logging destination > causes logging to happen in all modules, at the same level (if that is > the case, which I hope it is). > > 3) Maybe a small discussion of log formatting should be next? So the > user realizes he shouldn't do the message formatting himself? As advice, this shouldn't need to be more than a couple of lines, with a two line example, right? But it does deserve a prominent header. > 4) Then rotating logs for long-running programs. > > And then the rest of the more feature-filled stuff. +1 for this agenda.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4