- Boost-users - lists.boost.org

Problem serializing unsigned int via save/load
by Diane 16 Sep '08

16 Sep '08

Is there a trick or known bug with serializing an unsigned int via the split free functions? I have a structure that contains an unsigned int, and if I serialize with the free serialize function it works as it should. However, if I split the serialization into save/load I get: boost_1_36_0/boost/archive/detail/iserializer.hpp:541: error: conversion from `boost::serialization::is_wrapper<unsigned int>' to non-scalar type `mpl_::bool_< true>' requested Here's my structure and the two pieces of serialization code: typedef struct CCSTRUCT { unsigned int numRtp; } CCSTRUCT; Serialization #1 (works): template<class Archive> void serialize(Archive & ar, CCSTRUCT& it, const unsigned int version) { ar & it.numRtp; } Serialization #2 (doesn't work): BOOST_SERIALIZATION_SPLIT_FREE(CCSTRUCT) template<class Archive> void save(Archive & ar, const CCSTRUCT& d, unsigned int /* version */) { ar << d.numRtp; } template<class Archive> void load(Archive & ar, const CCSTRUCT& d, unsigned int /* version */) { ar >> d.numRtp; } I need to split the serialization because there are other elements in the structure that can't be handled in serialize(), so I would really appreciate some help if anyone has any ideas. Thanks, Diane

2 1

boost::signal performance in boost 1.36 and VS2005
by Hansi 16 Sep '08

16 Sep '08

Hello, I have made now a small test and I don't know if I make something wrong. I have the following performance comparsion between a boost::function and a boost::signal. Okay, I know that boost::signal has a lot of more functionality and for that it is for sure slower than boost::function. But 100times slower? May be I do something wrong? On my pc I have for boost::function a runtime of 728ms and for boost::signals a runtime of 64128ms There is one slot used for signals. Can anyone give me some hint what I do wrong? my test program was: class TestBind { public: int counter; void OnEventReceived(char b) { counter++; } }; class TestSignal { public: int counter; void OnEventReceived(char b) { counter++; } }; int _tmain(int argc, _TCHAR* argv[]) { TestBind testBind; PerformanceCounter timer; boost::function<void (char)> f = boost::bind(&TestBind::OnEventReceived,&testBind,_1); for(int i = 0; i < 100000000; i++) { f('a'); } TestSignal testSignal; boost::signal<void (char)> sig; sig.connect(boost::bind(&TestSignal::OnEventReceived,&testSignal,_1));; for(int i = 0; i < 100000000; i++) { sig('a'); } } Best regards Hansjörg

1 0

[serialization] Crashes after termination of main()
by Ruediger Berlich 16 Sep '08

16 Sep '08

Hi there, I am consistenty getting crashes in line 80 of the file /opt/boost136/include/boost-1_36/boost/serialization/extended_type_info_typeid.hpp , when my program exits. This is the destructor of class extended_type_info_typeid : ~extended_type_info_typeid(){ type_unregister(); } Any idea of what this is ? I'm using several singletons in my program, which according to their nature, only terminate once main() has finished. They refer to several objects which can, in other contexts, also be serialized. This specific program, however, does not make use of this option. I am pretty sure that the singletons do not refer to each other (any more) as, while searching for the problem, I have redesigned larger portions so that they don't. I'm using Boost 1.36 on OpenSUSE 11 / 64 bit (g++ 4.3.1). Thanks in any case and best regards, Ruediger

3 4

overloading on keyword signature
by e r 16 Sep '08

16 Sep '08

hi, i'm following up on an earlier of my posts with a simpler example. in the example below: the overload is on argument-name and type, yet the overload is ambiguous. 1) is there a way around this? and if so, 2) is it also possible to have an overload the on argument-name only (replace string and int below by *). thanks. *.hpp namespace lib{ BOOST_PARAMETER_NAME(name) BOOST_PARAMETER_NAME(index) BOOST_PARAMETER_FUNCTION( (void), f, tag, (required (name,(std::string))) ) { std::cout << name << std::endl; } BOOST_PARAMETER_FUNCTION( (void), f, tag, (required (index,(int))) ) { std::cout << index << std::endl; } } *.cpp lib::f(lib::_name = "jill"); lib::f(lib::_index = 1); /home/er/cpp/libs/testing_names/par_fun.hpp||In function ‘typename lib::boost_param_result_27f<typename boost::parameter::aux::argument_pack<lib::boost_param_params_27f<int>, const ParameterArgumentType0, boost::parameter::void_, boost::parameter::void_, boost::parameter::void_, boost::parameter::void_>::type>::type lib::f(const ParameterArgumentType0&, typename boost::parameter::aux::match<lib::boost_param_params_27f<int>, ParameterArgumentType0, boost::parameter::void_, boost::parameter::void_, boost::parameter::void_, boost::parameter::void_>::type) [with ParameterArgumentType0 = boost::parameter::aux::tagged_argument<lib::tag::index, const int>]’:| /home/er/cpp/libs/testing_names/main.cpp|28|instantiated from here| /home/er/cpp/libs/testing_names/par_fun.hpp|24|error: call of overloaded ‘boost_param_implf(boost::parameter::aux::arg_list<const boost::parameter::aux::tagged_argument<lib::tag::index, const int>, boost::parameter::aux::empty_arg_list>)’ is ambiguous| /home/er/cpp/libs/testing_names/par_fun.hpp|16|note: candidates are: typename lib::boost_param_result_19f<Args>::type lib::boost_param_implf(const Args&) [with Args = boost::parameter::aux::arg_list<const boost::parameter::aux::tagged_argument<lib::tag::index, const int>, boost::parameter::aux::empty_arg_list>]| /home/er/cpp/libs/testing_names/par_fun.hpp|24|note: typename lib::boost_param_result_27f<Args>::type lib::boost_param_implf(const Args&) [with Args = boost::parameter::aux::arg_list<const boost::parameter::aux::tagged_argument<lib::tag::index, const int>, boost::parameter::aux::empty_arg_list>]| /home/er/cpp/libs/testing_names/par_fun.hpp|24|error: return-statement with a value, in function returning 'void'| ||=== Build finished: 2 errors, 0 warnings ===|

3 2

for_each on boost::ptr_map
by Robert Dailey 16 Sep '08

16 Sep '08

Hi, Is there a way I can use std::for_each() on a boost::ptr_map and have the functor object be given the *value* of each item iterated instead of a key/value pair like it does with std::map? Help is appreciated, thank you.

4 6

serialization problems (undefined reference - boost::archive::detail::archive_pointer_oserializer<...>)
by Allan Johns 16 Sep '08

16 Sep '08

Hi, I've written my own archive, which works fine until I try serialising a boost::shared_ptr<X>, in which case I get: undefined reference to `boost::archive::detail::archive_pointer_oserializer<boost::archive::boost_oarchive>::~archive_pointer_oserializer(). (boost::archive::boost_oarchive is my archive class, in case this causes confusion). I'm on gcc4.1.2, ceontos4 x86_64. I'm linking to libboost_serialization-gcc41-mt-1_35.so also. I've hit a bit of a brick wall here so any help would be greatly appreciated. I've searched around but can't seem to find any relevant posts on this subject. cheers A _________________________________________________________________ Get all your favourite content with the slick new MSN Toolbar - FREE http://clk.atdmt.com/UKM/go/111354027/direct/01/

3 5

Error while using asio and xpressive together
by Rohit Sauhta 16 Sep '08

16 Sep '08

I get compiler error with the following code: #include <boost/asio.hpp> #include <boost/xpressive/xpressive.hpp> int main(int argc, char*argv[]) {} If I flip the order of #include, code compiles fine. I am using gcc 4.1.2 compiler on linux. Does this need to be fixed in asio ? thx Rohit

2 1

Problem with date_time facets
by Tavares, Pedro (London) 16 Sep '08

16 Sep '08

Hi all, I'm using boost with stlport 5.1.5 in msvc 7.1. when I try to use date facets, the compiler complains there is not suitable std::locale ctor, although I can see it in the code and all flags seem to be defined correctly (_STLP_MEMBER_TEMPLATES is defined). I'm trying to compile the following excerpt: 1 std::stringstream str(__DATE__); // for example "Sep 16 2008" 2 3 boost::gregorian::date_input_facet facet("%b %d %Y"); 4 std::locale loc(str.getloc(),facet); 5 str.imbue(loc); 6 7 boost::gregorian::date d; 8 str >> d; The error is in line 4 and the message is that the (templated) ctor does not exist. Thanks for your assistance, Pedro -------------------------------------------------------- This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. --------------------------------------------------------

1 0

date-time library and checked iterators
by gast128 16 Sep '08

16 Sep '08

Dear all, last week we switched to vstudio 2008. It has checked iterator support and it already catched two incorrect (but probably also harmless) uses of iterators. Maybe in the date time library there is also such a case. The stream operator on ptime eventually calls date_time::date_facet::do_put_tm () function which probably uses an incorrect way of dereferencing string iterators when empty: // use time_put facet to create final string return std::use_facet<std::time_put<CharT> >(a_ios.getloc()).put(next, a_ios, fill_char, &tm_value, &*a_format.begin(), &*a_format.begin()+a_format.size()); When a_format is empty the begin iterator may not be dereferenced? I do know that the actual code is harmless, but now we get the M$ checked iterator error message, and turning it globally off would be pity, since it cna be an extra potential debugging tool. Wkr, me

1 0

[test] Passing parameters to fixtures
by Markus Schöpflin 16 Sep '08

16 Sep '08

Hello, to set up and tear down database connections for unit tests, I need something like parametrized test fixtures. Up to now (using an old version of Boost.Test) I was creating a customized test suite (by deriving from test_suite) and performed the connection handling during construction/destruction of the customized test suite. As the latest Boost.Test now has explicit support for test fixtures, I was looking at how I could replace my old approach by using a test suite fixture. The fixture would need to look something like this: struct F { F(string db_name) { connect to db_name } ~F() { disconnect from db_name } }; Now, the Boost.Test documentation tells me that a fixture is supposed to be used like this: BOOST_FIXTURE_TEST_SUITE( s, F ) So there doesn't seem to be a way of passing parameters to the constructor of the fixture. Is there any? Or is there any other way to obtain a parametrized fixture? Or should I just keep on using customized test suites? TIA, Markus

4 10