You couldn't change an API post review and introduce completely new modifiers model. It's a different library that needs different review
I was only talking about changing (optimizing) the implementation.
You couldn't really optimize this without changing modifiers model.
Again, how would you know?
If you want to filter out a specific subsystem, you will disable the logs corresponding to that subsystem.
When a message is about to be written to the log, if the log is disabled, the whole message is ignored.
Ok. I guess you could mimic keywords with use of named logs. But now you have 2 different concepts (named log and log level) to do essentially the same job: filter log entry. And these wouldn't help you a bit if you need to filter based on any other criteria: category, time of day, thread id etc.
Ok, I finally get it. You're right about the filtering concept. It's more powerful that what I have right now. Best, John -- John Torjo, Contributing editor, C/C++ Users Journal -- "Win32 GUI Generics" -- generics & GUI do mix, after all -- http://www.torjo.com/win32gui/surfaces.html - Sky's the limit! -- http://www.torjo.com/cb/ - Click, Build, Run!