summaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorTor Lillqvist <tml@collabora.com>2016-08-18 16:55:11 +0300
committerTor Lillqvist <tml@collabora.com>2016-08-18 17:02:03 +0300
commit99ee4ebb0e934413bed881a02e4634e4d3f813ea (patch)
treef69a66e39692a2ebe6da76a9d01bc9b4b1d342d9 /include
parent4cd9e45a439b654c8e1ff7983fe7e4bd073b9c92 (diff)
If no WARN in SAL_LOG, use the INFO selection for WARNs, too
Often the choice whether some particular message is displayed with SAL_INFO or SAL_WARN has not necessarily been that well thought through. Many SAL_WARNs are not actually warnings but purely informative. If you want to see the INFOs for an area it makes sense to want to see also the WARNs for it. So make it so, unless a specific WARN selection is specified. Change-Id: I6286c5f856b29e68bedb7f20efadf56953f94b72
Diffstat (limited to 'include')
-rw-r--r--include/sal/log.hxx3
1 files changed, 3 insertions, 0 deletions
diff --git a/include/sal/log.hxx b/include/sal/log.hxx
index e879a2ff71e1..8b4ef0a51962 100644
--- a/include/sal/log.hxx
+++ b/include/sal/log.hxx
@@ -262,6 +262,9 @@ inline char const * unwrapStream(SAL_UNUSED_PARAMETER StreamIgnore const &) {
that has a sense of "+". (That is, if both +INFO.foo and -INFO.foo are
present, +INFO.foo wins.)
+ If no WARN selection is specified, but an INFO selection is, the
+ INFO selection is used for WARN messages, too.
+
For example, if SAL_LOG is "+INFO-INFO.foo+INFO.foo.bar", then calls like
SAL_INFO("foo.bar", ...), SAL_INFO("foo.bar.baz", ...), or
SAL_INFO("other", ...) generate output, while calls like