X-Git-Url: http://g0dil.de/git?a=blobdiff_plain;f=senf%2FUtils%2FLogger%2FMainpage.dox;h=35c865134c8728c7ff22af69b8d237e42ffee4ff;hb=9cb871b939efe93e35dd96808d25089399acfc46;hp=7a5509d6599d071c910cbc40c474ce24888f1269;hpb=3a43b572a2c0028b353d47e86fa7546633d6e2cf;p=senf.git

diff --git a/senf/Utils/Logger/Mainpage.dox b/senf/Utils/Logger/Mainpage.dox
index 7a5509d..35c8651 100644
--- a/senf/Utils/Logger/Mainpage.dox
+++ b/senf/Utils/Logger/Mainpage.dox
@@ -63,8 +63,8 @@
         <em>disabled</em> at compile time. senf::log::VERBOSE message will therefore only appear,
         if you explictly enable the messages for the area in question using (here for the area
         <code>some::Area</code>)
-        <pre> 
-        g++ ... -DSENF_LOG_CONF="(( (senf)(log)(Debug), (some)(Area), VERBOSE ))" 
+        <pre>
+        g++ ... -DSENF_LOG_CONF="(( (senf)(log)(Debug), (some)(Area), VERBOSE ))"
         </pre>
         in addition to routing the messages at runtime. For more, see \ref config.
 
@@ -72,7 +72,7 @@
     any number of \e targets. A \e target receives messages and using it's routing information
     decides, wether the message is output or not. A message may be routed to multiple targets
     simultaneously or may not be output by any target at all. (see: \ref targets)
-    
+
     \section logging_tutorial Tutorial introduction
 
     Using the logging library mostly concerns using \ref SENF_LOG statements in your code. There are
@@ -81,7 +81,7 @@
     \code
     namespace foo {
 
-        // Define a new log stream with default level, runtime limit and compile time limit 
+        // Define a new log stream with default level, runtime limit and compile time limit
         // set to senf::log::MESSAGE
         SENF_LOG_DEFINE_STREAM( UserLog, senf::log::MESSAGE, senf::log::MESSAGE, senf::log::MESSAGE );
 
@@ -140,7 +140,7 @@
         design goals
         \li Flexible configuration at compile and runtime
         \li Concise usage and simple interface
-        \li Zero overhead for compile-time disabled log messages 
+        \li Zero overhead for compile-time disabled log messages
 
         I did not find any non-mcaro implementation which was not either completely convoluted,
         unusable or slow. So I turned to a macro based implementation which can provide all the