[Boost-commit] svn:boost r41061 - sandbox/logging/boost/logging/detail/raw_doc

From: john.groups_at_[hidden]
Date: 2007-11-13 10:23:05

Author: jtorjo
Date: 2007-11-13 10:23:05 EST (Tue, 13 Nov 2007)
New Revision: 41061
URL: http://svn.boost.org/trac/boost/changeset/41061

Log:
[logging]
modified requirements.hpp help
Text files modified: 
   sandbox/logging/boost/logging/detail/raw_doc/requirements.hpp |    23 ++++++++++++++++++++++-                 
   1 files changed, 22 insertions(+), 1 deletions(-)

Modified: sandbox/logging/boost/logging/detail/raw_doc/requirements.hpp
==============================================================================
--- sandbox/logging/boost/logging/detail/raw_doc/requirements.hpp	(original)
+++ sandbox/logging/boost/logging/detail/raw_doc/requirements.hpp	2007-11-13 10:23:05 EST (Tue, 13 Nov 2007)
@@ -57,7 +57,11 @@
 
 @subsection bl_requirements_eliminate Eliminate log statemets from generated code (Michael Lacher)
 
-I have not tested this thoroughly, but just in case you want to fully eliminate statements from your code,
+"Requirement: It should be possible to prevent all or a specified subset of log messages from generating any code, symbols or strings in the object file."
+
+<b>About code/symbols:</b>
+
+I have not tested this extensively, but just in case you want to fully eliminate statements from your code,
 you should use filter::always_disabled.
 
 Most likely, you'd have something like this:
@@ -70,6 +74,23 @@
 #endif
 @endcode
 
+<b>About strings in the object file: </b>
+
+I assume you mean strings like file name, function name, etc.
+
+Note that these are added @b only if you use @ref tag "tags". So, just don't use these tags when you want this information stripped.
+Example:
+
+@code
+#ifndef ELIMINATE_LOG_STATEMENTS
+#define L_ BOOST_LOG_USE_LOG_IF_FILTER(g_l, g_log_filter->is_enabled() ) .set_tag( BOOST_LOG_TAG_FILELINE)
+#else
+#define L_ BOOST_LOG_USE_LOG_IF_FILTER(g_l, g_log_filter->is_enabled() ) 
+#endif
+@endcode
+
+
+
 @subsection bl_requirements_lazy Full lazy evaluation (Michael Lacher)
 
 Yup, done.