On 03/15/2010 08:58 PM, Stewart, Robert wrote:
Therefore, it's useful to provide a flexible library with a few most obvious and frequent cases available at hand and a great potential of extension and configurability.
Certainly a good approach. The issue is determining the common use cases you should support.
Right. But I guess, there will always be someone not happy with the choice.
* It appears that out of the box, the proposed library does not address this component/severity style of logging that I've explained above. The proposed solutions at:
http://permalink.gmane.org/gmane.comp.lib.boost.devel/200793
sound relatively complex.
I can't provide logger features for every case. Sometimes users will have to extend the library. Writing a class template with a couple constructors and a trivial method doesn't look very complex to me.
Vladimir's point is that severity/component is a very common use case that you should support out of the box. That's how our logging works, so Vladimir and I would have to recreate the same wheel if you don't provide direct support.
The library supports severity out of the box. Two different severities are unexpected and thus need a little more effort to support.