- Boost - lists.boost.org

[extension] Check if basic_type_map is empty
by Boris 21 Aug '08

21 Aug '08

When a library is loaded the return type of shared_library::open() or shared_library::is_open() can be used to detect whether the library was loaded successfully. When shared_library::call() is called the return type can be used to detect whether the exported map function could be called. But is there another function like is_open() which could be called afterwards to check if the map function was called successfully? The datatype basic_type_map only provides get() and no empty(). It would be required to call get() first and operate on the returned std::map type to see if it contains any factories? Boris

2 2

[unordered] Compiler warnings in VC++ 9 SP1
by Boris 21 Aug '08

21 Aug '08

I just replaced a std::map with a boost::unordered_map and got many compiler warnings (not only me as it seems like: http://www.boost.org/development/tests/release/developer/output/RW_WinXP_VC…) Is anyone working already on the code to get rid of the warnings? Boris

5 4

[smart_ptr] make_shared usage
by Daniel Frey 21 Aug '08

21 Aug '08

Hi, I have a question on make_shared. Consider a class which intends to force all instances to be handled via a shared_ptr. I used to do this by putting the ctors into the private section and adding static create()-methods in the public section. Example: class X { private: X( int, double ); public: static shared_ptr<X> create( int i, double d ) { return shared_ptr<X>( new X( i, d ) ); } }; Replacing the returned expression with make_shared<X>( i, d ) wouldn't work, since it requires a public ctor. Is there any solution to this or do I have to make a decision between efficiency and a safe interface for X? Regards, Daniel

7 17

[PATCH: MPL] Compiling with gcc 4.4.0 -std=c++0x
by Chris Fairles 21 Aug '08

21 Aug '08

Due to pre-processor changes in gcc 4.4.0, MPL fails to compile given -std=c++0x or -std=gnu++0x on the command line. The attached patch addresses this issue. This is a works-for-me solution, YMMV. Chris

4 7

Where does make_shared.hpp come from?
by Boris 20 Aug '08

20 Aug '08

I stumbled over boost::make_shared() in Andrey's logging library. I checked the smart pointers documentation at http://www.boost.org/doc/libs/1_36_0/libs/smart_ptr/smart_ptr.htm but couldn't find any reference to boost::make_shared(). The header file make_shared.hpp contains the link http://www.boost.org/libs/smart_ptr/make_shared.html but the webpage doesn't exist either. Is boost::make_shared() not yet documented? Boris

2 1

[log] Questions for Andrey
by Boris 20 Aug '08

20 Aug '08

I've been converting a program from John's logging library to Andrey's logging library. I have to continue playing around with Andrey's library but in the moment I prefer it over John's library. I can't say really that this or that is better - it's more the overall handling of Andrey's logging library which feels more natural for me. Maybe it's also Andrey's documentation which is rather good (the definitions and design overview really help to understand the big picture before you dive into all the details). I've some questions though for Andrey: * Where is the connection between a source and a sink? In the basic_usage example there are two sinks registered (console and file). There is then one source created which is used to log a message. The message is then sent to both the console and the file. But what if I want to use for example two sources and want messages from each source to be sent to a different sink? Do I understand correctly that I need to use attributes somehow and filter records based on attribute values? I guess I would need to add an attribute to each source and set a filter in each sink to make sure only messages with a certain attribute are written? * If I want to format a message and add a timestamp why do I need to write boost::log::formatters::date_time("TimeStamp") and can't write boost::log::formatters::attr("TimeStamp")? Doesn't the attribute value know how to be serialized (or isn't it written to a std::ostream)? If I use boost::log::formatters::attr("TimeStamp") nothing is written to the log file. It's not a problem to use boost::log::formatters::date_time("TimeStamp") of course. But I still wonder why the library can't figure out to write the timestamp if I use boost::log::formatters::attr("TimeStamp"). * I've been reading http://boost-log.sourceforge.net/libs/log/doc/html/advanced/advanced.html#a… a few times but still don't understand why I can't (or shouldn't) instantiate a global logger with "boost::log::sources::logger logger;". I actually did this and everything works (or at least seems to work :). Must the macro BOOST_LOG_DECLARE_GLOBAL_LOGGER really be used when a global logger is created? Maybe I better understand if I ask differently: What is so special about a logger that I need to use a macro to define it globally while I can create for example a global std::string instance without a macro? * By default there is a newline appended to every message written? By the way, looking at the TODO list: I would be very much interested in Windows NT event log support. I'm sure it would also convince more developers to use a logging library as writing texts to files in some fancy ways can also be done without a logging library. :) Boris

2 5

[log] More questions for Andrey (how to add function signature to messages)
by Boris 20 Aug '08

20 Aug '08

Currently I'm writing messages to a file with: BOOST_LOG(mylogger) << __FUNCSIG__ << " message text"; I'd prefer if the function signature (let's assume for now that the macro is supported by all compilers) is written automatically without me having to add __FUNCSIG__ everywhere. From what I understand I can't simply add an attribute to the logger as __FUNCSIG__ would then be used in another function (and thus a different function signature would be written). Looking around in the documentation I found BOOST_LOG_WITH_PARAMS (see http://boost-log.sourceforge.net/libs/log/doc/html/BOOST_LOG_WITH_PARAMS.ht…) It makes me think that I could define my own BOOST_LOG macro somehow like this: #define BOOST_LOG_FUNCSIG(logger)\ BOOST_LOG_WITH_PARAMS((logger), (::boost::log::sources::keywords::funcsignature = (__FUNCSIG__))) I see that the macro BOOST_LOG_SEV is defined similarly in severity_logger.hpp. However I also see that some more code has to be added to the logger to make the logger understand what to do with the keyword. For example in the severity logger in open_record() the appropriate attribute is set if the severity keyword is found. That means I would need to create a new logger and check for my new funcsignature attribute in open_record() if I want the function signature to be written automatically? Is there another way to do this more easily? Boris

2 3

[exception] missing workarounds for msvc 4265 warning
by Jürgen Hunold 20 Aug '08

20 Aug '08

Hi ! My coworkers found some more annoying msv 4265 warnings. (missing virtual destructor. The attached patch adds the necessary workaround (analog to gcc). Okay to commit ? Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! Ingenieurgesellschaft für * voice: ++49 511 262926 57 ! Verkehrs- und Eisenbahnwesen mbH * fax : ++49 511 262926 99 ! Lister Straße 15 * juergen.hunold(a)ivembh.de ! www.ivembh.de * * Geschäftsführer: ! Sitz des Unternehmens: Hannover * Prof. Dr.-Ing. Thomas Siefer ! Amtsgericht Hannover, HRB 56965 * PD Dr.-Ing. Alfons Radtke !

4 5

[config] disabling hash_map/set by #define BOOST_NO_HASH
by Juergen Hunold 20 Aug '08

20 Aug '08

Hi ! After upgrading to gcc-4.3 I got annoyed by the myriads of deprecated warnings about "hash_map" and "hash_set" especially from the BGL code. I tried to get rid of those by simply adding #define BOOST_NO_HASH to the command line and it worked. Unfortunately, it seems that trunk config does not detect hash support with msvc-8.0 and this compiler then bailed out with a macro redefinition error at config/suffix.hpp :-(( Patch to add a check for an already defined BOOST_NO_HASH (and for BOOST_NO_SLIST) attached. Comments ? Ok to commit ? Better ideas to disable hash support ? Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! Ingenieurgesellschaft für * voice: ++49 511 262926 57 ! Verkehrs- und Eisenbahnwesen mbH * fax : ++49 511 262926 99 ! Lister Straße 15 * juergen.hunold(a)ivembh.de ! www.ivembh.de * * Geschäftsführer: ! Sitz des Unternehmens: Hannover * Prof. Dr.-Ing. Thomas Siefer ! Amtsgericht Hannover, HRB 56965 * PD Dr.-Ing. Alfons Radtke !

2 2

[integer] Recent changes introduced failures on many platforms
by Markus Schöpflin 20 Aug '08

20 Aug '08

The two tests integer_mask_test and integer_test have been broken by the recent commits to integer on nearly all platforms. (Probably all but Windows) The error message is: In file included from ../libs/integer/test/integer_test.cpp:29: ../boost/integer.hpp:154:39: error: invalid suffix "ui64" on integer constant ../libs/integer/test/integer_test.cpp:115:39: error: invalid suffix "ui64" on integer constant ../libs/integer/test/integer_test.cpp:215:39: error: invalid suffix "ui64" on integer constant Regards, Markus

8 27