* No concept of a message severity or level (suggested to use different Log instances)
It is worth pointing out that this is a feature - not an omission.
Indeed so!
* Logs must be declared in a header, defined in a different TU. Helper macros provided to assist with this [this is the one feature I most dislike]
* But 1.3 included scoped logs, so if you want to create logs dynamically at runtime you can. These logs don't need the declare/define.
Yup
[...] * For what it is worth, I think the fatal handler (or other interesting behaviours triggered by particular logs being written to) can be implemented by making an appender that is fatal, and directing "fatal" logs to it (as well as to other appenders, of course the fatal appender must be the last one).
Again, true. Many thanks for pointing these out! Best, John -- John Torjo, Contributing editor, C/C++ Users Journal -- "Win32 GUI Generics" -- generics & GUI do mix, after all -- http://www.torjo.com/win32gui/ -- http://www.torjo.com/cb/ - Click, Build, Run!