November 2007 - Boost - lists.preview.boost.org

warnings in Boost.Serialization
by Christoph Duelli 27 Nov '07

27 Nov '07

Due to templates warnings in Boost tend to create a lot of noise. As we try to maintain a 'no warnings' policy, it would be great if the following 'issues' could be fixed (otherwise I have to maintain a modified Boost around here) (Boost version 1.34.1) Serialization produces (in release builds) the following warnings (as the variables are only used in asserts or #ifdefs): basic_binary_oprimitive.hpp:87: warning: unused variable 'i' basic_binary_iprimitive.hpp:87: warning: unused variable 'i' shared_ptr.hpp:196: warning: unused variable 'file_version' (a trivial way to fix this would be: (void) i; is that ok? 'cause that is basically what I am using (inside a macro).) Best regards Christoph

1 0

[test] Causing regex regression?
by John Maddock 27 Nov '07

27 Nov '07

Gennadiy, Would you know the likely reason for a boost::system_error being thrown in this test: http://tinyurl.com/yq2yya ? Glancing at the Boost.Test source this appears to be thrown when an internal Boost.Test assertion fails? Any ideas what's going on? Thanks, John.

4 9

Candidate logging library and static initialization/destruction
by Matthew Herrmann 27 Nov '07

27 Nov '07

Hi, I have a question for the author of the logging library on the boost review queue regarding static initialization and destruction. I currently use the logging library that was rejected at the last review, and I noticed some issues with it relating to handling destruction in a static context. Specifically, I'd get occasional segfaults if I declared an item in static scope that logged in its destructor. Once the object was moved to within the main() function, the issue went away. I'm not sure if it was the logging library, or our use of it, but it was a bit of an issue since it made the use of logging less transparent to clients of my library code. I can see from the documentation that you have given quite a bit of thought to multithreading concerns. Have you also considered issues around static initialization and destruction? In particular, a class that performs logging in its constructor and destructor should still behave correctly when instantiated in a static context. I think the problems I had with logging before related to the logging data structures being torn down in the static destruction phase before my own objects. The way I solved that in a (far more limited!) logging library for our own use was the following: - Never destroy the logging data structures -- allow them to leak. No risk of static ordering issues. - In the static initialization case, initialize the logging structures on first access, and if not accessed during the static context, guarantee that they are initialized before main() is called. To do that, I essentially borrowed the implementation of the boost pool singleton, except that I removed the destruction: http://boost.org/libs/pool/doc/implementation/singleton.html Anyway, I would appreciate hearing your thoughts on this area as I'd like to use version 2! Many thanks, Matthew Herrmann

3 3

Re: [boost] Candidate logging library and static initialization/destruction
by Matthew Herrmann 27 Nov '07

27 Nov '07

Hi John, Thanks for getting back to me. > I have encountered this as well - in v1. > [snip] in v2 [snip] > So, within a week - this feature will be present. Ah good sounds like we're thinking on the same lines. No rush, it could be fiddly. > As a side-note - if you could trim down the example and send it to me, > that would make it easier for me to test ;) No problem -- I'll see if I can come up with a couple of tests around that area and forward them onto you. Best Regards, Matthew Herrmann

2 1

Re: [boost] Boost Threads Condition may block forever on clock change
by ak1mbox-boost＠yahoo.ca 26 Nov '07

26 Nov '07

Hi, Thank you to everyone who replied to my question. Its very good that it is now possible to initialize condition with a relative timeout, if I understood the last post correctly. This help to resolve at least part of the problem. One quick note, another cross OS library that implements a lot of threading primitives is APR (Apache Runtime Library). I have been using APR heavily for the last few month and my testing showed that APR does not have this problem of being affected by clock changes. I am not sure about their internal implementation so can't comment on differences between APR and BOOST condition but this might be something interesting to look at. Thank you, Alex

4 3

[Report] 386 failures on trunk (2007-11-26)
by Douglas Gregor 26 Nov '07

26 Nov '07

Boost regression test failures Report time: 2007-11-26T11:10:05Z This report lists all regression test failures on release platforms. Detailed report: http://boost.org/regression/trunk/developer/issues.html 386 failures in 23 libraries asio (1) concept_check (2) conversion (7) date_time (3) dynamic_bitset (3) function_types (36) fusion (2) gil (9) graph (10) interprocess (17) lambda (1) math (1) mpl (2) numeric/interval (19) parameter (2) ptr_container (1) python (138) regex (9) serialization (105) spirit (8) test (5) thread (4) tokenizer (1) |asio| strand_select: darwin-4.0.1 |concept_check| where: intel-linux-9.0 intel-vc8-win-10.0 |conversion| lexical_cast_test: darwin-4.0.1 gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 intel-vc8-win-10.0 msvc-7.1 msvc-8.0 msvc-8.0_64 |date_time| testlocal_time_facet: gcc-4.2.1 testtime_serialize_xml_std_config: darwin-4.0.1 testtz_database: gcc-4.2.1 |dynamic_bitset| dyn_bitset_unit_tests3: gcc-4.2.1 gcc-4.2.1 gcc-4.2.1_linux_x86_64 |function_types| fast_mem_fn_example: msvc-7.1 interface_example: msvc-7.1 member_ccs: darwin-4.0.1 darwin-4.0.1 gcc-4.1.2_sunos_i86pc gcc-4.2.1 gcc-4.2.1 gcc-4.2.1 gcc-4.2.1_linux_x86_64 intel-linux-9.0 intel-vc8-win-10.0 msvc-8.0_64 member_ccs_exact: darwin-4.0.1 darwin-4.0.1 gcc-4.1.2_sunos_i86pc gcc-4.2.1 gcc-4.2.1 gcc-4.2.1 gcc-4.2.1_linux_x86_64 intel-linux-9.0 intel-vc8-win-10.0 msvc-8.0_64 nonmember_ccs: gcc-4.2.1 gcc-4.2.1 gcc-4.2.1 gcc-4.2.1_linux_x86_64 intel-linux-9.0 intel-vc8-win-10.0 msvc-8.0_64 nonmember_ccs_exact: gcc-4.2.1 gcc-4.2.1 gcc-4.2.1 gcc-4.2.1_linux_x86_64 intel-linux-9.0 intel-vc8-win-10.0 msvc-8.0_64 |fusion| deduce_sequence: intel-vc8-win-10.0 repetitive_view: intel-vc8-win-10.0 |gil| channel: intel-vc8-win-10.0 image: gcc-4.1.2_sunos_i86pc intel-vc8-win-10.0 image_io: gcc-4.1.2_sunos_i86pc main: gcc-4.1.2_sunos_i86pc intel-vc8-win-10.0 pixel: gcc-4.1.2_sunos_i86pc intel-vc8-win-10.0 pixel_iterator: gcc-4.1.2_sunos_i86pc |graph| betweenness_centrality_test: gcc-4.2.1_linux_x86_64 csr_graph_test: msvc-8.0_64 cycle_ratio_tests: intel-vc8-win-10.0 msvc-8.0 floyd_warshall_test: gcc-4.2.1_linux_x86_64 graphml_test: intel-vc8-win-10.0 msvc-8.0 graphviz_test: intel-vc8-win-10.0 msvc-8.0 matching_test: gcc-4.2.1_linux_x86_64 |interprocess| condition_test: gcc-4.2.1 doc_anonymous_semaphoreA: gcc-4.2.1 doc_anonymous_semaphoreB: gcc-4.2.1 doc_named_mutex: gcc-4.2.1 file_mapping_test: gcc-4.2.1 mapped_file_test: gcc-4.2.1 message_queue_test: gcc-4.2.1 named_condition_test: gcc-4.2.1 named_mutex_test: gcc-4.2.1 named_recursive_mutex_test: gcc-4.2.1 named_semaphore_test: gcc-4.2.1 named_upgradable_mutex_test: gcc-4.2.1 semaphore_test: gcc-4.2.1 shared_memory_mapping_test: gcc-4.2.1 shared_memory_test: gcc-4.2.1 shared_ptr_test: gcc-4.2.1 upgradable_mutex_test: gcc-4.2.1 |lambda| operator_tests_simple: msvc-7.1 |math| test_igamma_inva_real_concept: gcc-4.2.1_linux_x86_64 |mpl| is_seq: intel-vc8-win-10.0 token_equal: intel-vc8-win-10.0 |numeric/interval| det: gcc-4.2.1 msvc-8.0_64 integer: gcc-4.2.1 mul: darwin-4.0.1 darwin-4.0.1 gcc-4.2.1 msvc-8.0_64 overflow: darwin-4.0.1 darwin-4.0.1 gcc-4.2.1 msvc-8.0_64 pi: darwin-4.0.1 darwin-4.0.1 gcc-4.2.1 msvc-8.0_64 pow: gcc-4.2.1 msvc-8.0_64 test_float: gcc-4.2.1 msvc-8.0_64 |parameter| python_test: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 |ptr_container| serialization: intel-vc8-win-10.0 |python| andreas_beyer: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 args: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 auto_ptr: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 back_reference: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 bases: gcc-4.1.2_sunos_i86pc intel-linux-9.0 ben_scott1: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 bienstman1: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 bienstman2: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 bienstman3: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 builtin_converters: gcc-4.1.2_sunos_i86pc callbacks: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 const_argument: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 crossmod_exception: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 crossmod_opaque: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 data_members: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 defaults: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 dict: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 docstring: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 enum: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 exception_translator: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 exec: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 intel-linux-9.0 exec-dynamic: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 intel-linux-9.0 extract: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 implicit: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 import_: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 intel-linux-9.0 injected: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 iterator: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 keywords: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 list: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 long: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 map_indexing_suite: gcc-4.1.2_sunos_i86pc minimal: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 multi_arg_constructor: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 nested: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 numpy: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 object: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 intel-vc8-win-10.0 opaque: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 operators: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 operators_wrapper: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 pearu1: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 pickle1: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 pickle2: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 pickle3: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 pickle4: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 pointee: gcc-4.1.2_sunos_i86pc intel-linux-9.0 pointer_type_id_test: gcc-4.1.2_sunos_i86pc intel-linux-9.0 pointer_vector: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 polymorphism: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 polymorphism2: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 polymorphism2_auto_ptr: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 properties: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 pytype_function: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 raw_ctor: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 return_arg: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 select_arg_to_python_test: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 shared_ptr: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 slice: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 staticmethod: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 stl_iterator: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 str: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 test_pointer_adoption: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 try: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 tuple: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 upcast: gcc-4.1.2_sunos_i86pc intel-linux-9.0 vector_indexing_suite: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 virtual_functions: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 voidptr: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 wrapper_held_type: gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 |regex| regex_regress_threaded: gcc-4.2.1_linux_x86_64 intel-vc8-win-10.0 regex_timer: darwin-4.0.1 gcc-4.1.2_sunos_i86pc gcc-4.2.1_linux_x86_64 intel-vc8-win-10.0 msvc-7.1 msvc-8.0 msvc-8.0_64 |serialization| test_demo_portable_archive: gcc-4.2.1 test_demo_portable_archive_dll: gcc-4.2.1 test_diamond_binary_archive: intel-vc8-win-10.0 test_diamond_binary_archive_dll: intel-vc8-win-10.0 test_diamond_text_archive: intel-vc8-win-10.0 test_diamond_text_archive_dll: intel-vc8-win-10.0 test_diamond_text_warchive: intel-vc8-win-10.0 test_diamond_text_warchive_dll: intel-vc8-win-10.0 test_diamond_xml_archive: intel-vc8-win-10.0 test_diamond_xml_archive_dll: intel-vc8-win-10.0 test_diamond_xml_warchive: intel-vc8-win-10.0 test_diamond_xml_warchive_dll: intel-vc8-win-10.0 test_exported_binary_archive: gcc-4.1.2_sunos_i86pc gcc-4.2.1 gcc-4.2.1 gcc-4.2.1 gcc-4.2.1_linux_x86_64 intel-vc8-win-10.0 test_exported_binary_archive_dll: gcc-4.1.2_sunos_i86pc gcc-4.2.1 gcc-4.2.1 gcc-4.2.1 gcc-4.2.1_linux_x86_64 intel-vc8-win-10.0 test_exported_text_archive: gcc-4.1.2_sunos_i86pc gcc-4.2.1 gcc-4.2.1 gcc-4.2.1 gcc-4.2.1_linux_x86_64 intel-vc8-win-10.0 test_exported_text_archive_dll: gcc-4.1.2_sunos_i86pc gcc-4.2.1 gcc-4.2.1 gcc-4.2.1 gcc-4.2.1_linux_x86_64 intel-vc8-win-10.0 test_exported_text_warchive: gcc-4.1.2_sunos_i86pc gcc-4.2.1 gcc-4.2.1 gcc-4.2.1 gcc-4.2.1_linux_x86_64 intel-vc8-win-10.0 test_exported_text_warchive_dll: gcc-4.1.2_sunos_i86pc gcc-4.2.1 gcc-4.2.1 gcc-4.2.1 gcc-4.2.1_linux_x86_64 intel-vc8-win-10.0 test_exported_xml_archive: gcc-4.1.2_sunos_i86pc gcc-4.2.1 gcc-4.2.1 gcc-4.2.1 gcc-4.2.1_linux_x86_64 intel-vc8-win-10.0 test_exported_xml_archive_dll: gcc-4.1.2_sunos_i86pc gcc-4.2.1 gcc-4.2.1 gcc-4.2.1 gcc-4.2.1_linux_x86_64 intel-vc8-win-10.0 test_exported_xml_warchive: gcc-4.1.2_sunos_i86pc gcc-4.2.1 gcc-4.2.1 gcc-4.2.1 gcc-4.2.1_linux_x86_64 intel-vc8-win-10.0 test_exported_xml_warchive_dll: gcc-4.1.2_sunos_i86pc gcc-4.2.1 gcc-4.2.1 gcc-4.2.1 gcc-4.2.1_linux_x86_64 intel-vc8-win-10.0 test_inclusion: intel-vc8-win-10.0 test_mult_archive_types: intel-vc8-win-10.0 test_mult_archive_types_dll: intel-vc8-win-10.0 test_no_rtti_binary_archive: intel-vc8-win-10.0 test_no_rtti_binary_archive_dll: intel-vc8-win-10.0 test_no_rtti_text_archive: intel-vc8-win-10.0 test_no_rtti_text_archive_dll: intel-vc8-win-10.0 test_no_rtti_text_warchive: intel-vc8-win-10.0 test_no_rtti_text_warchive_dll: intel-vc8-win-10.0 test_no_rtti_xml_archive: intel-vc8-win-10.0 test_no_rtti_xml_archive_dll: intel-vc8-win-10.0 test_no_rtti_xml_warchive: intel-vc8-win-10.0 test_no_rtti_xml_warchive_dll: intel-vc8-win-10.0 test_shared_ptr_132_binary_archive: intel-vc8-win-10.0 test_shared_ptr_132_binary_archive_dll: intel-vc8-win-10.0 test_shared_ptr_132_text_archive: intel-vc8-win-10.0 test_shared_ptr_132_text_archive_dll: intel-vc8-win-10.0 test_shared_ptr_132_text_warchive: intel-vc8-win-10.0 test_shared_ptr_132_text_warchive_dll: intel-vc8-win-10.0 test_shared_ptr_132_xml_archive: intel-vc8-win-10.0 test_shared_ptr_132_xml_archive_dll: intel-vc8-win-10.0 test_shared_ptr_132_xml_warchive: intel-vc8-win-10.0 test_shared_ptr_132_xml_warchive_dll: intel-vc8-win-10.0 test_shared_ptr_binary_archive: intel-vc8-win-10.0 test_shared_ptr_binary_archive_dll: intel-vc8-win-10.0 test_shared_ptr_text_archive: intel-vc8-win-10.0 test_shared_ptr_text_archive_dll: intel-vc8-win-10.0 test_shared_ptr_text_warchive: intel-vc8-win-10.0 test_shared_ptr_text_warchive_dll: intel-vc8-win-10.0 test_shared_ptr_xml_archive: intel-vc8-win-10.0 test_shared_ptr_xml_archive_dll: intel-vc8-win-10.0 test_shared_ptr_xml_warchive: intel-vc8-win-10.0 test_shared_ptr_xml_warchive_dll: intel-vc8-win-10.0 |spirit| grammar_mt_tests: darwin-4.0.1 owi_mt_tests: intel-vc8-win-10.0 scanner_value_type_tests: gcc-4.2.1 gcc-4.2.1 gcc-4.2.1_linux_x86_64 scanner_value_type_tests_debug: gcc-4.2.1 gcc-4.2.1 gcc-4.2.1_linux_x86_64 |test| prg_exec_fail3: gcc-4.1.2_sunos_i86pc gcc-4.2.1 gcc-4.2.1 gcc-4.2.1_linux_x86_64 intel-linux-9.0 |thread| test_condition: gcc-4.2.1_linux_x86_64 test_condition_lib: gcc-4.2.1_linux_x86_64 test_shared_mutex: gcc-4.2.1_linux_x86_64 test_shared_mutex_lib: gcc-4.2.1_linux_x86_64 |tokenizer| simple_example_5: gcc-4.2.1

1 0

Boost Logging v2
by John Torjo 26 Nov '07

26 Nov '07

Boost Loogging v2 Hi all, It's been a while - I admit, and I apologize for it. Well, finally, I'm working on version 2 of Boost Logging, taking into account your suggestions when the first version was rejected. The extra short version: It's in alpha stage. Get it from here: http://torjo.com/log2/ Without further ado, I'll present you Boost Logging Library v2, with - a much nicer separation of concepts and - a much more flexible interface. - you don't pay for what you don't use. - fits a lot of scenarios: from very simple (dumping all to one log) to very complex (multiple logs, some enabled/some not, levels, etc). - you can now define your own LOG_ macros Here are 2 small examples to show you a bit of v2's power: ----------------- Example 1: struct write_to_cout_and_file { ... }; // defining the logs logger<write_to_cout_and_file, manage_enabled_no_ts> g_single_log("out.txt"); #define L_(x) if ( g_single_log) g_single_log.process_msg()(x) // code L_("reading word " + word); ----------------- Example 2: struct write_to_file { ... }; struct write_to_cout { ... }; struct write_to_dbg { ... }; // defining the logs typedef process_msg< ostream_like_return_str<>, write_to_cout> processor_cout; typedef process_msg< ostream_like_return_str<>, write_to_file> processor_file; typedef process_msg< ostream_like_return_str<>, write_to_dbg> processor_dbg; logger<processor_cout, manage_enabled_no_ts> g_log_app; logger<processor_file, manage_enabled_no_ts> g_log_err("err.txt"); logger<processor_dbg, manage_enabled_no_ts> g_log_dbg; #define LAPP_ if ( !g_log_app) ; else g_log_app->read_msg().gather().out() #define LERR_ if ( !g_log_err) ; else g_log_err->read_msg().gather().out() #define LDBG_ if ( !g_log_dbg) ; else g_log_dbg->read_msg().gather().out() // code LAPP_ << idx << " : reading word " << word; LERR_ << "error at " << idx << ", while reading " << word; LDBG_ << "debug info: " << idx << ", reading " << word; ----------------- The above was the short version. You can also look at the test_*.cpp files, to see some more examples of how you can use the library. Download it here : http://torjo.com/log2/ Long version follows: First, a bit about the workflow: Step 1: Filtering the message Step 2: Gathering the message Step 3: Writing the message Step 1: Filtering the message In order to be efficient, before anything happens to the message, we see if the log it's written to, is enabled. If so, we process the message. If not, we ignore all of the message. This is rather easy, with constructs like this: #define L_(x) if ( g_single_log) g_single_log.process_msg()(x) #define L_ if ( !g_log_app) ; else g_log_app->read_msg().gather().out() Step 2: Gathering the message Now, that we know the log is enabled, all the message is gathered. This depends on how you write the message. For instance, you can gather it in one step, if you want to offer a syntax like this: L_("this is my message"); Or, you can offer syntactic sugar: i = 100; L_ << "this is " << i << " times better that the average bear... "; In this case, you'll gather all info in a stream of some kind. Or, you can have more data besides the message string, like: module name, severity of message, category, etc: L_(fatal,"chart","Can't find the ChartX control"); Step 3: Writing the message Now all info about the message is gathered. You can write it to its destination(s). What you wanna do with a message, is completely up to you. The library will offer you possibilities. You can go for the extremely easy way, and just have a functor which dumps the message somewhere, like this: struct write_to_cout { void operator()(const std::string & msg) const { std::cout << msg << std::endl ; } }; Or: struct write_to_file { typedef boost::shared_ptr<std::ofstream> ptr; write_to_file(const std::string & filename) : m_out(new std::ofstream(filename.c_str())) {} void operator()(const std::string & msg) const { (*m_out) << msg << std::endl ; } mutable ptr m_out; }; Or, you can choose to Format and/or write your message to Destinations (these will be explained later) Download it here : http://torjo.com/log2/ ------------------------------------------------------ Logger objects For each log you want, you'll have a logger object. Note that "log" is a concept - several logs can write to the same file and/or one log can write to multiple destinations. I use the term "log" to identify a type of log message you want to write -- for example, you can have a "debug log" for writing debug messages; an "info" log, for writing informations, and so on. The fact that they might end up writing to the same destinations, is completely transparent to the user, as it should. A logger object contains 2 things: - a filter: an is_enabled() function - to find out if it's enabled. - a process_msg() object - this contains the logic of what to do with the message, if the log is enabled. The 2 concepts are orthogonal - Andrei would call them "policies" ;) The process_msg() is the object that will process the message if the log is enabled - it executes steps 2 and 3. How this happens, is completely up to you - when you define your macros (more on this later). ------------------------------------------------------ Filtering and Log Levels I have implented several filters: see filter.hpp file: - manage_enabled_no_ts - filter (not thread-safe) - always_enabled - enable logs at compile time - always_disabled - disable logs at compile time - debug_enabled, release_enabled - manage_enabled_ts - thread-safe filter - etc. Using v2, you don't really have to use Log Levels, if you don't wish (see examples above) A logged message can have an associated Log Level. By default we have these levels: info (smallest level), warning , debug , error , fatal (highest level) Depending on which level is enabled for your application, some messages will reach the log: those messages having at least that level. For instance, if info level is enabled, all logged messages will reach the log. If warning level is enabled, all messages are logged, but the warnings. If debug level is enabled, messages that have levels debug, error, fatal will be logged. Note that there's an example of using Log Levels provided with the code. ------------------------------------------------------ Usage syntax / Macros Once you've set up what each of your logs does (writes to), it's a must to have an easy and straightforward way to write to your logs - logging can be fun. While you can write directly to your logs, like this: if ( !g_log_app) ; else g_log_app->read_msg().gather().out() << "coolio!" << std::endl; Usually you'll prefer to have some macros to help you write less and especially avoid being error-prone. In the previous version, you've asked to be able to write your own macros - well, you are. And it's waaaay easier than before: If you have a logger object, to test if it's enabled, call its operator bool(). To see if it's not enabled, call its operator! I will provide some helpers in the future - they're not there yet. ------------------------------------------------------ Logger objects and macros So, to define a log macro, you'll say something like this: logger<some_processor, some_filter_class> g_log; #define L_ if ( !g_log) ; else g_log->... Note that "g_log->" is equivalent to "g_log.process_msg()->" (syntactic sugar) What follows after "..." is all up to you. For example, you can just get the message, and call a functor: struct write_to_cout { void operator()(const std::string & msg) const { std::cout << msg << std::endl ; } }; logger<write_to_cout, manage_enabled_no_ts> g_single_log; #define L_(x) if ( g_single_log) g_single_log.process_msg()(x) And in code you'll say things like L_("some great message"); Or, you can use something a bit more complex, which will gather a message written using "<<", and then call a functor. I've already implemented this class: typedef process_msg< ostream_like_return_str<>, write_to_cout> processor_cout; logger<processor_cout, manage_enabled_no_ts> g_log; #define L_ if ( !g_log) ; else g_log->read_msg().gather().out() And in code you'll say things like: L_ << "this" << " is " << "cool"; Or you can implement your own process message class. ------------------------------------------------------ Using process_msg() Your process_msg class can hold context. And you can also manipulate logs in code: logger<...> g_log; g_log->my_great_log_manipulator(); Thus, you can create your own process message handler classes. ------------------------------------------------------ Formatters and/or destinations In my previous version, they were called modifiers and appenders. So, after the message has been gathered (step 2), we do the writing (step 3). In step 3, if you use the "format_write" class, you can choose to add formatters and/or destinations. A formatter is a functor that formats the message - for instance, it can prepend the current time, it can prepend the index, or thread ID, or append an Enter. A destination is a location where a message can be written, like: console, a file, a socket, etc. Dealing with formatters/destinations is easy: once you have a format_write object, just use: void add_formatter(formatter fmt) void del_formatter(formatter fmt) void add_destination(destination dest) void del_destination(destination dest) In the previous version, the formatters were called first, and destinations last. Now you have more control. However, this is not thoroughly tested - need to work more on this. ------------------------------------------------------ Examples. I've provided a few examples - you'll find them in the "tests" directory. The code compiles and was tested on VC8. Am still working on formatters and destinations. I'm planning to host it on sf.net. Feedback and comments are welcome. Again, you'll find the library here: http://torjo.com/log2/ -- http://John.Torjo.com -- C++ expert ... call me only if you want things done right

3 5

[asio] async_close ? async_shutdown ?
by Roland Schwarz 26 Nov '07

26 Nov '07

Hi! I find the asio docs a little terse about what it has to say about close / shutdown. Will close always block? Will shutdown block? What puzzles me is that the doc say that close will cancel outstanding async calls. I assume this means calls from where I did not have received a callback handler, yes? May I conclude from this, that when I invoke close from the last callback (I know there are no more pending callbacks) that close will do a graceful shutdown, i.e. deliver all buffered data to the receiver? Is there an example showing how to do a graceful shutdown? Is there an example that demonstrates shutdown? Why are there no asyn_ versions of these operations available? Thank you Roland aka speedsnail

1 0

Trac open bugs - by assignee
by Marshall Clow 26 Nov '07

26 Nov '07

[ 216 open bugs today, 217 Friday ] If you are maintaining a library, and have not logged into the trac system at <http://svn.boost.org/trac/boost/>, please do so ASAP. Until you do that, no tickets can be assigned to you, and will remain under "None". Instructions on working with tickets can be found at: <http://svn.boost.org/trac/boost/wiki/TicketWorkflow> and a mapping of user names to "real names" can be found at: <http://svn.boost.org/trac/boost/report/16> Bug summary 20 ramey 19 dgregor 17 az_sw_dude 14 djowel 12 grafik 12 doug_gregor 11 turkanis 10 None 9 johnmaddock 9 dave 9 agurtovoy 7 anthonyw 6 vladimir_prus 6 jsiek 5 witt 5 nesotto 5 igaztanaga 4 pdimov 4 bemandawes 3 jmaurer 3 danielw 2 urzuga 2 t_schwinger 2 pavol_droba 2 nasonov 2 matias 2 ebf 2 burbelgruff 1 speedsnail 1 shammah 1 samuel_krempp 1 rogeeff 1 niels_dekker 1 marshall 1 kaalus 1 hkaiser 1 eric_niebler 1 dlwalker 1 aaron_windsor 1 <Blank> <Blank> 1307 [lambda] invalid boostbook None 1048 Spirit returns full = false in 1.34 if there is trailing spaces in input None 1068 Mersenne twister disables streaming for Visual C++ None 1094 Finding the correct library to link (feature request for pkg-config support)h None 1222 lambda::ret<T> should declare result_type. None 1247 Typos in "boost/random/additive_combine.hpp"_ lines 68-69 None 1270 uniform_smallint doesn't compile with lagged_fibonacci random number generators None 1342 dylib library names broken in Mac OS X None 1407 Boost is doesn't install on MacPorts using Leopard None 1423 MSVC uniform int workaround not required for VC++ 2008 None 1473 VC++ 2009 does not need workaround aaron_windsor 778 top-level configure is broken agurtovoy 1001 gcc 4.1.2 segfaults on mpl/test/apply.cpp agurtovoy 1051 MPL header ordering triggers bug agurtovoy 1099 unable to iterate through a "non-explicitly-declared" mpl::set agurtovoy 1215 Boost 1.34.1_ mpl: Wrong workaround detection using MinGW32 (or.hpp_ line #33) agurtovoy 1317 has_xxx randomly broken in msvc agurtovoy 1469 [mpl] nested typedef of set has two different meanings agurtovoy 1476 always<> is not nullary. agurtovoy 588 mpl::remove compile error with gcc 4.1.0 agurtovoy 640 documentation mistake anthonyw 1154 tss destruction segfaults in conjunction with dlopen/dlclose anthonyw 1168 [thread] tss crashes randomly anthonyw 1268 xtime_cmp changes to deal with overflow were reverted anthonyw 1449 jrp anthonyw 1470 Boost.Thread: Compilation errors with non-__cdecl calling convention anthonyw 876 xtime documentation incomplete anthonyw 881 errors when build with Apache stdcxx az_sw_dude 1028 typo in boost header: date_time/time_defs.hpp az_sw_dude 1078 from_iso_string cannot read the output from to_iso_string az_sw_dude 1098 Urgent libboost-date-time1.33.1 : bugs on ia64 ? az_sw_dude 1147 date_time library contains global #define ERROR az_sw_dude 1160 warning: month_format shadows a member of this az_sw_dude 1162 warning: ticks shadows a member of this az_sw_dude 1289 posix_time::time_facet forgets to pass a_ref argument to base class az_sw_dude 1299 change in typedef stringstream_type in format_date_parser.hpp causing compilation error az_sw_dude 1306 invalid docbook in date_period.xml az_sw_dude 1384 Linking problem with date_time library on Visual C++ 2008 Express az_sw_dude 1386 date_time documentation Jamfile breaks building of boost docs az_sw_dude 287 wrong usage of ios_base::narrow az_sw_dude 316 date_time type conversion warning az_sw_dude 604 from_ftime incorrectly processes FILETIME filled with zeros az_sw_dude 642 operator<< for gregorian::date_duration not found az_sw_dude 889 Insane Dependencies az_sw_dude 890 date_time library supports only the current dst rule bemandawes 1378 filesystem path invalid name for hidden files (LINUX) bemandawes 1389 filesystem::ostream << boost::format generates operator ambigious error (in MSVC++) bemandawes 1458 Darwin Tiger throws std::runtime_error: locale::facet::_S_create_c_locale name not valid bemandawes 752 directory_iterator doesn't work with catch burbelgruff 1468 [typeof] Problems with VC8/VC9 when using code analysis burbelgruff 1475 VC++ 2008 not configured correcly danielw 1044 Argument pack inaccessable in a functions return type danielw 1054 Parameter takes an "infinite" amount of time to compile with the Intel compiler. danielw 1097 keyword.hpp generates many warnings C4180: qualifier applied to function type has no meaning; ignored dave 1010 linking boost.python on freebsd dave 1019 iterator_facade::pointer should be the return type of operator-> (DR 445) dave 1085 Python rules for compiling in Mac OS X dave 1179 [boost.python] can not export a union in VC2005sp1 dave 1181 [boost.python] can modify enum value dave 1387 Review / update docs to reflect changes dave 1460 Python classes with multiple bases are convertible only to the first class in the lists dave 865 Use of C++0x keyword as identifier dave 910 gcc strict-aliasing problems with python dgregor 1002 [iostreams] close_impl<closable_tag> does not comply with spec dgregor 1003 [iostreams] copy-paste error in typedefs for wchar multichar_filters dgregor 1139 [iostreams] Regex filter segfaults when zero matches found dgregor 1140 boost::iostreams linked_streambuf bug dgregor 1149 Minor doc error in basic_null_device dgregor 1164 Floyd Warshall broken with unsigned edge weights dgregor 1185 iostreams::direct_streambuf<T_Tr>::is_open always returns false if output iterator is not null dgregor 1192 [boostbook] problem when two files have the same name dgregor 1199 configure doesn't work with path containing whitespaces (MacOS X) dgregor 1232 mapped_file_source::is_open() is broken under windows dgregor 1310 [result_of] const-qualified function pointer doesn't work dgregor 1326 Unable to check graph isomorphism using LEDA adapter dgregor 1391 dominator_tree_test on Borland/CodeGear outputs overly long line dgregor 1394 Translate libs/graph/build/python/Jamfile to BBv2 dgregor 1395 Write Tests for Python Bindings dgregor 1416 Warnings from Boost.Function need suppression. dgregor 556 Bundled graph properties dgregor 732 Johnson All-Pairs needs better "no path" information dgregor 736 Const correctness violation djowel 1096 Tutorial needs updating for BBv2 djowel 1170 Emit Warnings instead of # symbols in the syntax highlighter djowel 1171 Quickbook title output djowel 1172 non-utf djowel 1176 Space after inline code djowel 1206 Escaping from within code? djowel 1273 CR+LF newlines in position_iterator djowel 1276 spirit problem with _GLIBCXX_DEBUG djowel 1277 Closing section like [pre with } causes Quickbok to crash djowel 1280 sections in imported source files get put inside <para> elements in docbook output djowel 1281 Quickbook produces invalid BoostBook/DocBook XML djowel 1324 tuple should have a swap() that operates element-by-element djowel 1396 wrong result_of invocation around transform_view djowel 1436 [quickbook] inline code inside headings dlwalker 613 boost/crc.hpp uses non-standard conforming syntax doug_gregor 1021 [Graph][reverse_graph] Problem using reverse_graph adapter with an adapted user defined graph doug_gregor 1076 compile error: disconnecting struct with operator()() doesn't work in VS2005 SP1 doug_gregor 375 LEDA graph adaptors do not handle hidden nodes properly doug_gregor 402 random_vertex/random_edge are unnecessarily inefficient doug_gregor 403 Document copy_component doug_gregor 447 reverse_graph and constness of property maps doug_gregor 708 Dijkstra no_init version should not require VertexListGraph doug_gregor 733 Numbered headers don't work with "preferred" syntax doug_gregor 735 Fruchterman-Reingold grid performance can be improved doug_gregor 738 Memory leaks with signal::connect? doug_gregor 829 Implicit graph not implement doug_gregor 852 Problem with Boost and GCC 4.1 ebf 965 [doc] boost::variant tutorial - final example uses v1_v2 should be seq1_seq2 ebf 993 Variant should use least common multiple of alignments_ rather than maximum eric_niebler 1472 foreach test breaks VC++2009 grafik 1041 Cygwin requires PATH setting. grafik 1062 Cygwin install stage fails with combination of patches grafik 1322 trac rejects patch attachment as spam grafik 1417 Regresson tests hang in Darwin (Tiger) grafik 1430 Regression fails under Cygwin grafik 1433 Trac's spam detection rejects too many valid messages grafik 1445 Document @() bjam feature. grafik 1447 Document `__TIMING_RULE__` grafik 1448 Document `__ACTION_RULE__` grafik 616 Boost Jam_ and non english directorys grafik 959 linking fails when Boost is compiled with STLport 5.1.* on Linux (names mismatch) grafik 986 Problem building Python modules on boost 1.34.0 hkaiser 1079 boost-1.34.0 fails to compile. concept checks not satisfied. igaztanaga 1080 boost::interprocess win32 global file mapping issue igaztanaga 1210 interprocess::barrier hangs during second use under linux (boost 1.33.1) igaztanaga 1231 interprocess_condition (emulated) hangs after notify_all(). igaztanaga 1390 Interpocess: managed shared memory failing completely under OS X igaztanaga 1453 gcc 4.3.0 seems to need a <cstring> to pull in the necessary std:: functions jmaurer 351 Diff in state of mersenne_twister gen between GCC3.41 & CW9 jmaurer 599 uniform_01 copies engine instead of using a reference jmaurer 819 uniform_int<> with type's maximum availaible range error johnmaddock 1081 Empty string rejected as perl-style regex johnmaddock 1083 boost_regex 1.34.0 uses ICU library without linking to it johnmaddock 1314 Using SSE-intrinsics in VC8 causes static assert in type_with_alignment.hpp johnmaddock 1411 Fix BOOST_PARTIAL_SPECIALIZATION_EXPLICT_ARGS johnmaddock 1440 libs/config/test/link/Jamfile.v2 confuses process_jam_log johnmaddock 1446 POSIX API doesn't use C locale johnmaddock 1451 error: use of C99 long long integer constant johnmaddock 1455 gcc 4.3.0 requires main to take 0 or 2 arguments johnmaddock 1474 VC++ 2008 seems to trigger multiple inclusion of boost::hash jsiek 416 Spelling of Edmonds-Karp-Algorithm jsiek 575 Calling subgraph::global_to_local on a root graph jsiek 636 strange compiling problem for transitive_closure jsiek 815 remove_edge core dumps on self-circle jsiek 875 No iterator based constructor for adjacency_matrix jsiek 900 graphml reader namespace handling is broken kaalus 1184 property_tree assignment (operator) bug marshall 1252 [pool] severe overhead with unaligned sizes. matias 1406 Understanding the Tables outdated matias 1434 Boost.Preprocessor_ small fix for the documentation nasonov 1220 lexical_cast requires RTTI nasonov 754 boost::any - typeid comparison across shared boundaries nesotto 1284 [range] sub_range assignment issue nesotto 1464 boost_range_array unused in several array_size() functions nesotto 1467 [ptr_container] VC8 compiler warning nesotto 1477 boost::sizer declaration ill-formed nesotto 723 local_time_facet error in VS2005 Win2003 niels_dekker 1459 value_initialized leaves data uninitialized_ when using Borland pavol_droba 1152 rle_example fails pavol_droba 1385 begin must be boost-qualified pdimov 1106 shared_ptr<T> should not convert to shared_ptr<U> when T* doesn't convert to U* pdimov 1108 shared_ptr does not compile under g++ with -fno-rtti pdimov 1444 scoped_ptr::operator== should be equivalent to a.get()==b.get()_ but is currently !!a==!!b pdimov 997 error in boost::bind doc ramey 1036 assert failure in oserializer.hpp:418 ramey 1038 "<" and ">" should be excaped in xml_oarchive ramey 1086 Serialization of weak_ptr produces invalid XML ramey 1089 missing boost::serialization::make_nvp in pointer container library ramey 1121 xml_archive_exception is missing seperate header file_ and documentation mismatch ramey 1137 Virtual destructor is missing ramey 1141 Dangerious operator<< for wostream ramey 1142 boost/serialization/optional doesn't include necessary header ramey 1223 boost::serialization chokes on correcly formatted empty XML element ramey 1267 Assertion `new_cid == cid' failed in basic_iarchive ramey 1285 [serialization] problem when including shared_ptr_132.hpp ramey 1286 Missing/Incorrect dllimport/dllexport directives prevent Windows DLLs from building ramey 1290 Serialization export.hpp (or type_info_implementation.hpp) is NOT self-contained and causes compile error ramey 1382 Missing #pragma warning(pop) in void_cast.hpp ramey 1443 deserialization from text_iarchive is not thread-safe ramey 1457 boost/serialization/complex.hpp: double & should be double? ramey 757 xml serialization fails when using namespace ramey 961 boost::basic_binary_oprimitive not instantiated correctly ramey 968 xml_grammar - incorrect define char ramey 969 basic_binary_iprimitive::load_binary bug rogeeff 1383 signal.h features not found on Mac OS samuel_krempp 859 boost::format ignores a user defined locale shammah 386 boost::pool_allocator breaks with vector of vectors speedsnail 1138 Problems with TSS and static thread library t_schwinger 1100 Building boost.function_types fails cvs rev-1.1_ no chdir command in bash t_schwinger 1332 Inclusion of non existing file boost/fusion/sequence/utility/unpack_args.hpp in boost/fusion/sequence/utility.hpp turkanis 1033 iostreams::restrict doesn't work on an iostreams::file_source turkanis 1070 [iostreams]boost\iostreams\copy.hpp line80 copy_impl turkanis 525 problem with boost::iostreams when compiled with Visual C++ turkanis 699 Changing size of memory-mapped file on Windows turkanis 786 bug in iostreams/copy.hpp line 81 turkanis 791 iostreams::tee_filter is for output only turkanis 817 Performance problem in iostreams turkanis 822 Incorrect usage of bad_write()_ bad_seek() etc. turkanis 823 Seekable file_descriptor_source /sink? turkanis 824 BOOST_IOSTREAMS_HAS_LSEEK64 on Mac OS X turkanis 856 iostreams file_descriptor::write fails under Win32 urzuga 574 [boost::lambda] Compile error with libstdc++ debug mode urzuga 781 Lambda: (_1 + "y")(string("x")) Doesn't Compile vladimir_prus 1165 more quoting problems vladimir_prus 1274 Useless error message vladimir_prus 1275 boost::program_options::validation_error::what() is private vladimir_prus 1321 invalid docbook in tool documentation vladimir_prus 469 multitoken broken vladimir_prus 689 [program_options] Endless loop with long default arguments witt 1046 Boost.Python quickstart instructions mention nonexistent target witt 583 Fixes for build on IBM pSeries for AIX and Linux witt 834 Homepage regression links witt 957 The "Getting Started" page does not mention the stdlib option witt 973 zip_iterator has value_type == reference -- -- Marshall Marshall Clow Qualcomm, Inc. <mailto:mclow@qualcomm.com> The famous British scientist, Lord Kelvin, said: "When you measure what you are speaking about and express it in numbers, you know something about it, but when you cannot (or do not) measure it, when you cannot (or do not) express it in numbers, then your knowledge is of a meagre and unsatisfactory kind."

1 0

[result_of] vs decltype
by shunsuke 26 Nov '07

26 Nov '07

Hi, What happens if result_of is not consistent with decltype? struct my_fun_t { template<class Sig> struct result; template<class This> struct result<This(int)> { typedef int type; // avoid dangling. }; template<class This> struct result<This(int const &)> { typedef int const & type; }; int const & operator()(int const &i) const { return i; } }; my_fun_t const my_fun = {}; int main() { boost::result_of<my_fun_t const(int)>::type x = my_fun(10); // ok in C++98. decltype(my_fun(10)) x_ = my_fun(10); // dangling in C++0x. } BTW, result_of implementation of my_fun_t is allowed in C++98? Regards, -- Shunsuke Sogame

3 2