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

From: john.groups_at_[hidden]
Date: 2007-12-01 06:14:05

Author: jtorjo
Date: 2007-12-01 06:14:05 EST (Sat, 01 Dec 2007)
New Revision: 41528
URL: http://svn.boost.org/trac/boost/changeset/41528

Log:
[logging]
changed todo
Text files modified: 
   sandbox/logging/boost/logging/detail/raw_doc/changelog.hpp |     1 +                                       
   sandbox/logging/boost/logging/detail/raw_doc/todo.hpp      |     2 +-                                      
   2 files changed, 2 insertions(+), 1 deletions(-)

Modified: sandbox/logging/boost/logging/detail/raw_doc/changelog.hpp
==============================================================================
--- sandbox/logging/boost/logging/detail/raw_doc/changelog.hpp	(original)
+++ sandbox/logging/boost/logging/detail/raw_doc/changelog.hpp	2007-12-01 06:14:05 EST (Sat, 01 Dec 2007)
@@ -3,6 +3,7 @@
 
 @section changelog_cur_ver Current Version: v0.12.8, 1 dec 2007
 - added high precision timer - does not work correctly yet
+- bug: the named_spacer does not compile in gcc 4.1 - TO FIX
 - removed "#define BOOST_LOG_COMPILE_FAST_OFF" from samples - no needed and could be misleading
 - added boost::logging::formatter::named_spacer
 - created lock_resource_finder namespace - with existing resource lockers

Modified: sandbox/logging/boost/logging/detail/raw_doc/todo.hpp
==============================================================================
--- sandbox/logging/boost/logging/detail/raw_doc/todo.hpp	(original)
+++ sandbox/logging/boost/logging/detail/raw_doc/todo.hpp	2007-12-01 06:14:05 EST (Sat, 01 Dec 2007)
@@ -81,7 +81,7 @@
 - @c low    new formatter: limit the text to gives maximal length. It may happend the dump is unexpectedly large and would
   fill disk/overwrite cache/take too much time/be unreadable. Limiting one log size would help here a lot and would relieve end user of doing it manually.
 
-- @c high           quite often I am not interested not in absolute time (2005/12/11 16:33) but in time offset from some event. 
+- @c normal           quite often I am not interested not in absolute time (2005/12/11 16:33) but in time offset from some event. 
   I suggest to add API: \n
   some_formatter.set_time_start_point( bool either_in_all_threads_or_just_in_current_thread); \n
   and escape sequences: \n