- Boost-users - lists.preview.boost.org

Program Options - options dependencies
by Angelo Mondaini 02 Jul '14

02 Jul '14

Dear all, I am using the Program Options and I would like to know if I can add options dependencies through the lib. For example, consider a "test" program that has a flag "--has-dependencies" that needs a flag "--dependency" and a flag "--no-depenencies". It would run like this: $./test --no-dependencies Program running... $./test --has-dependencies Error! Flag "--dependency" is needed! $./test --has-dependencies --dependency Program running... PS: I know I can use something like this, but I would like to know if there is a better option: if ( vm.count("--has-dependencies") ) if ( vm.count("--dependency") ) //do something... else //trow an error

1 0

Program Options not saving the values
by Angelo Mondaini 02 Jul '14

02 Jul '14

Dear all, I am having a problem with the Program Options lib. I am using Archlinux and boost-libs 1.55.0-6. Consider the simple code: #include "boost/program_options.hpp" #include <iostream> #include <string> int main(int argc, char** argv) { int add(5); namespace po = boost::program_options; po::options_description desc("Options"); desc.add_options() ("help", "Print help messages") ("add",po::value<int>(&add)->required(), "additional options") ("like", "this"); po::variables_map vm; po::store(po::parse_command_line(argc, argv, desc), vm); if ( vm.count("help") ) { std::cout << "Basic Command Line Parameter App" << std::endl << desc << std::endl; return 1; } std::cout << "var: " << add << std::endl; std::cout << "vm: " << vm["add"].as<int>() << std::endl; po::notify(vm); return 1; } Compiling and running: $ g++ program_options.cpp -lboost_program_options $ ./a.out --add 4 var: 5 vm: 4 Why the value of the variable "add" is not receiving 4? Thanks for any help.

2 2

[ANN] CppCon 2014 program available
by Boris Kolpackov 02 Jul '14

02 Jul '14

The CppCon 2014 Program is now available with talk titles, abstracts, and speakers: http://cppcon.org/conference-program/ The program contains over 100 one-hour sessions by over 70 speakers including plenary sessions by Scott Meyers and Herb Sutter, as well as the keynotes by C++ creator Bjarne Stroustrup on Keeping Simple Things Simple and Mark Maimone on using C++ on Mars: Incorporating C++ into Mars Rover Flight Software. We have also extended the Early Bird deadline to July 9 so you have a week to study the program and still get the Early Bird rate. Hope to see you in Bellevue! Boris

1 0

Why does async_connect() call listen()?
by Soren Dreijer 01 Jul '14

01 Jul '14

Hi there, By coincidence, I ended up looking at a stack trace where my application calls async_connect() on a asio::ip::tcp::socket. Two things took me by surprise: 1. Asio calls listen() under the hood. Why does it do that when I'm just trying to make an outbound TCP connection? 2. If the listen() call above is indeed required, why does it happen on the same thread where I call async_connect()? I thought the point of the method was to defer the work to the reactor? (For what it's worth, I've had a case on a customer's machine where the call to listen() would hang for 30 seconds before returning -- probably because of a bad firewall -- causing my entire app to hang since the code assumes async_connect() is indeed async.) I've included the full stack trace below. Thanks, Soren 0:000> k ChildEBP RetAddr 0117db50 0f681c65 WS2_32!listen 0117db70 0f691013 EvoClr!boost::asio::detail::socket_ops::listen+0x35 [c:\private\src\vendor\boost_1_55_0_sdk\include\boost\asio\detail\impl\socket_ops.ipp @ 658] 0117dbd8 0f690e9f EvoClr!boost::asio::detail::socket_select_interrupter::open_descriptors+0x163 [c:\private\src\vendor\boost_1_55_0_sdk\include\boost\asio\detail\impl\socket_select_interrupter.ipp @ 78] 0117dbe4 0f690cc0 EvoClr!boost::asio::detail::socket_select_interrupter::socket_select_interrupter+0xf [c:\private\src\vendor\boost_1_55_0_sdk\include\boost\asio\detail\impl\socket_select_interrupter.ipp @ 42] 0117dc1c 0f690c1e EvoClr!boost::asio::detail::select_reactor::select_reactor+0x70 [c:\private\src\vendor\boost_1_55_0_sdk\include\boost\asio\detail\impl\select_reactor.ipp @ 48] 0117dc44 0f17837e EvoClr!boost::asio::detail::service_registry::create<boost::asio::detail::select_reactor>+0x4e [c:\private\src\vendor\boost_1_55_0_sdk\include\boost\asio\detail\impl\service_registry.hpp @ 81] 0117dc80 0f6909e9 EvoClr!boost::asio::detail::service_registry::do_use_service+0x9e [c:\private\src\vendor\boost_1_55_0_sdk\include\boost\asio\detail\impl\service_registry.ipp @ 123] 0117dca0 0f6908ee EvoClr!boost::asio::detail::service_registry::use_service<boost::asio::detail::select_reactor>+0x39 [c:\private\src\vendor\boost_1_55_0_sdk\include\boost\asio\detail\impl\service_registry.hpp @ 49] 0117dca8 0f68fab0 EvoClr!boost::asio::use_service<boost::asio::detail::select_reactor>+0xe [c:\private\src\vendor\boost_1_55_0_sdk\include\boost\asio\impl\io_service.hpp @ 34] 0117dcbc 0f68f731 EvoClr!boost::asio::detail::win_iocp_socket_service_base::get_reactor+0x30 [c:\private\src\vendor\boost_1_55_0_sdk\include\boost\asio\detail\impl\win_iocp_socket_service_base.ipp @ 620] 0117dce4 0f68f6f1 EvoClr!boost::asio::detail::win_iocp_socket_service_base::start_connect_op+0x11 [c:\private\src\vendor\boost_1_55_0_sdk\include\boost\asio\detail\impl\win_iocp_socket_service_base.ipp @ 550] 0117dd28 0f68ed22 EvoClr!boost::asio::detail::win_iocp_socket_service<boost::asio::ip::tcp>::async_connect<boost::_bi::bind_t<void,boost::_mfi::mf1<void,Swift::BoostConnection,boost::system::error_code const &>,boost::_bi::list2<boost::_bi::value<boost::shared_ptr<Swift::BoostConnection> >,boost::arg<1> > > >+0xc1 [c:\private\src\vendor\boost_1_55_0_sdk\include\boost\asio\detail\win_iocp_socket_service.hpp @ 515] 0117dd68 0f68c41a EvoClr!boost::asio::stream_socket_service<boost::asio::ip::tcp>::async_connect<boost::_bi::bind_t<void,boost::_mfi::mf1<void,Swift::BoostConnection,boost::system::error_code const &>,boost::_bi::list2<boost::_bi::value<boost::shared_ptr<Swift::BoostConnection> >,boost::arg<1> > > >+0x52 [c:\private\src\vendor\boost_1_55_0_sdk\include\boost\asio\stream_socket_service.hpp @ 234] 0117ddec 0f68a32e EvoClr!boost::asio::basic_socket<boost::asio::ip::tcp,boost::asio::stream_socket_service<boost::asio::ip::tcp> >::async_connect<boost::_bi::bind_t<void,boost::_mfi::mf1<void,Swift::BoostConnection,boost::system::error_code const &>,boost::_bi::list2<boost::_bi::value<boost::shared_ptr<Swift::BoostConnection> >,boost::arg<1> > > >+0x11a [c:\private\src\vendor\boost_1_55_0_sdk\include\boost\asio\basic_socket.hpp @ 779] 0117de9c 0f210146 EvoClr!Swift::BoostConnection::connect+0x11e [c:\private\src\vendor\swift\swiften\network\boostconnection.cpp @ 70]

4 4

[serialization] avoid nvp for wrapper class
by dariomt＠gmail.com 01 Jul '14

01 Jul '14

Hi list, How do I tell Boost.Serialization to serialize a wrapper as the primitive type, without requiring an nvp wrapper? I specifically don't want an extra level in the xml output. Example: given BOOST_STRONG_TYPEDEF(int, myInt); I'd like myInt to be serialized as an int. Thanks!

1 0

[atomic] ThreadSanitizer reports a data race when using the code from "reference counting" example
by Adam Romanek 01 Jul '14

01 Jul '14

Hi Boosters! I'd like to draw your attention to an issue with Boost.Atomic that I encountered when using ThreadSanitizer. The problem is that when using the code shown in "reference counting" example [1] from the docs, the ThreadSanitizer reports a data race. Everything is described in detail in a StackOverflow thread [2] so I don't want to repeat all that here. Please help me determine whether it's a false positive, an issue in Boost.Atomic or a wrong usage of the code. Additionally, I don't understand this: Write of size 1 at 0x7d040000f7f0 by thread T2: #0 operator delete(void*) <null>:0 (a.out+0x00000004738b) What kind of write does ThreadSanitizer might refer to? WBR, Adam Romanek [1] http://www.boost.org/doc/libs/1_55_0/doc/html/atomic/usage_examples.html#bo… [2] http://stackoverflow.com/questions/24446561/threadsanitizer-reports-data-ra…

2 3

Intel 14.0.1 error with boost::bind
by Aniket Pugaonkar 01 Jul '14

01 Jul '14

Hi, I am using a test program for compiling a boost::bind in Intel MIC(Xeom Phi). Here are the details of the code and platform on which it is compiled. I am using thread building blocks in my code, but the following code does not contain any TBB threads. The errors in my test code below and original code are same. Compiler : Intel 13.0.1 / intel 14.0.1 SP1 Update 3 (latest from intel composer XE trial version) I am using our lab's compiler installed on a cluster. The TBB is installed in my home directory. boost 1.55 is also installed in my home location. Compiled for MIC: icpc -mmic -L/home/aniketnp/tbb42_20140122oss/lib/mic -std=c++11 -I/home/aniketnp/boost_1_55_0 -I/home/aniketnp/tbb42_20140122oss/include test.cpp Scenario: a functor takes 2 arguments in its operator()() by using a boost::bind() method. The operator()() method contains a function which uses comparisons ( < or > ) using if-else logic. The error pops up here. Here is the following code. #include <iostream> #include <boost/bind.hpp> using namespace std; struct Info_t { int start; int end; Info_t(int s=0,int e=0) : start(s), end(e) { } }; template <typename T, typename time> void process_info(const T& info1, const T& info2, const time& t) { //the below gives compiler error * if ((info1.start < info2.end) && (info2.end > info1.end) && (info1.end < info2.start) )* std::cout << "yess error with mic" << std::endl; //the below if works fine if ((info1.start < info2.end) && (info2.end > info1.end)) std::cout << "no error at all" << std::endl; } template<typename Time> struct my_functor { public: my_functor() { } my_functor(Time& time_) : time(time_) { } typedef void result_type; template<typename info_t> void operator()(const info_t& info1, const info_t& info2) { const auto& i1 = info1; const auto& i2 = info2; process_info<info_t, Time> (i1,i2, time); } private: Time& time; }; int main() { Info_t i1(10,2); Info_t i2(2,10); int t = 1; auto func = boost::bind( my_functor<int>(t), _1, _2 ); func(i1,i2); return 0; } test.cpp(16): error: expression must have a constant value if ((info1.start < info2.end) && (info2.end > info1.end) && (info1.end < info2.start) ) ^ detected during: instantiation of "void my_functor<Time>::operator()(const info_t &, const info_t &) [with Time=int, info_t=Info_t]" at line 313 of "/home/aniketnp/boost_1_55_0/boost/bind/bind.hpp" instantiation of "void boost::_bi::list2<A1, A2>::operator()(boost::_bi::type<void>, F &, A &, int) [with A1=boost::arg<1>, A2=boost::arg<2>, F=my_functor<int>, A=boost::_bi::list2<Info_t &, Info_t &>]" at line 61 of "/home/aniketnp/boost_1_55_0/boost/bind/bind_template.hpp" instantiation of "boost::_bi::bind_t<R, F, L>::result_type boost::_bi::bind_t<R, F, L>::operator()(A1 &, A2 &) [with R=boost::_bi::unspecified, F=my_functor<int>, L=boost::_bi::list2<boost::arg<1>, boost::arg<2>>, A1=Info_t, A2=Info_t]" at line 48 test.cpp(16): error: this operator is not allowed in a template argument expression if ((info1.start < info2.end) && (info2.end > info1.end) && (info1.end < info2.start) ) ^ detected during: instantiation of "void my_functor<Time>::operator()(const info_t &, const info_t &) [with Time=int, info_t=Info_t]" at line 313 of "/home/aniketnp/boost_1_55_0/boost/bind/bind.hpp" instantiation of "void boost::_bi::list2<A1, A2>::operator()(boost::_bi::type<void>, F &, A &, int) [with A1=boost::arg<1>, A2=boost::arg<2>, F=my_functor<int>, A=boost::_bi::list2<Info_t &, Info_t &>]" at line 61 of "/home/aniketnp/boost_1_55_0/boost/bind/bind_template.hpp" instantiation of "boost::_bi::bind_t<R, F, L>::result_type boost::_bi::bind_t<R, F, L>::operator()(A1 &, A2 &) [with R=boost::_bi::unspecified, F=my_functor<int>, L=boost::_bi::list2<boost::arg<1>, boost::arg<2>>, A1=Info_t, A2=Info_t]" at line 48 test.cpp(16): error: expected a ">" if ((info1.start < info2.end) && (info2.end > info1.end) && (info1.end < info2.start) ) ^ detected during: instantiation of "void my_functor<Time>::operator()(const info_t &, const info_t &) [with Time=int, info_t=Info_t]" at line 313 of "/home/aniketnp/boost_1_55_0/boost/bind/bind.hpp" instantiation of "void boost::_bi::list2<A1, A2>::operator()(boost::_bi::type<void>, F &, A &, int) [with A1=boost::arg<1>, A2=boost::arg<2>, F=my_functor<int>, A=boost::_bi::list2<Info_t &, Info_t &>]" at line 61 of "/home/aniketnp/boost_1_55_0/boost/bind/bind_template.hpp" instantiation of "boost::_bi::bind_t<R, F, L>::result_type boost::_bi::bind_t<R, F, L>::operator()(A1 &, A2 &) [with R=boost::_bi::unspecified, F=my_functor<int>, L=boost::_bi::list2<boost::arg<1>, boost::arg<2>>, A1=Info_t, A2=Info_t]" at line 48 As a workaround, I try to do this, but same error if ((info2.start < info2.end) && (info2.end > info1.end) ) { if ( info1.end < info2.start) //do something } // error is propagated towards inner if loop test.cpp(17): error: expression must have a constant value if ( info1.end < info2.start) ^ detected during: instantiation of "void my_functor<Time>::operator()(const info_t &, const info_t &) [with Time=int, info_t=Info_t]" at line 313 of "/home/aniketnp/boost_1_55_0/boost/bind/bind.hpp" instantiation of "void boost::_bi::list2<A1, A2>::operator()(boost::_bi::type<void>, F &, A &, int) [with A1=boost::arg<1>, A2=boost::arg<2>, F=my_functor<int>, A=boost::_bi::list2<Info_t &, Info_t &>]" at line 61 of "/home/aniketnp/boost_1_55_0/boost/bind/bind_template.hpp" instantiation of "boost::_bi::bind_t<R, F, L>::result_type boost::_bi::bind_t<R, F, L>::operator()(A1 &, A2 &) [with R=boost::_bi::unspecified, F=my_functor<int>, L=boost::_bi::list2<boost::arg<1>, boost::arg<2>>, A1=Info_t, A2=Info_t]" at line 49 test.cpp(17): error: this operator is not allowed in a template argument expression (rest error is the same) ------------------------------------------------------------------------------------------------- Now, if I compile it without " -mmic " flag, then there is no compiler errors. I compile with this : icpc -L/home/aniketnp/tbb42_20140122oss/lib/intel64/gcc4.4 -std=c++11 -I/home/aniketnp/boost_1_55_0 -I/home/aniketnp/tbb42_20140122oss/include test.cpp I dont get any error. It compiles and runs fine. Any thoughts ? Please let me know. -- Thanks and regards, Aniket Pugaonkar

1 0

Oneshot fixture per test suit
by Florian Lindner 30 Jun '14

30 Jun '14

Hello, is it possible to have a test fixture that is created once per test suite and is destroyed after the last test of the test suite has been ran? A test suite level fixture is created before each and every test, a global fixture just once for the entire test programm. Thanks, Florian

1 0

Re: [Boost-users] [fusion] maps and arrays
by Seeger, Steven D. (GSFC-444.0)[Embedded Flight Systems, Inc] 29 Jun '14

29 Jun '14

From: Agust?n K-ballo Berg? Subject: Re: [Boost-users] [fusion] maps and arrays >Not an official answer in any way, but considering it's not explicitly >documented as supported and your test case also fails when replacing >`fusion::map` with `std::tuple` I would consider it just a fluke in the >past. On the other hand, the following code compiles correctly (albeit >with possibly a warning): Hi Agustin thanks for your reply. You are correct that what I'm doing is not documented. In fact, it doesn't really make sense now that I look at it. The for_each should be called on each type. If the type is an array it doesn't make sense for a for_each to break down the array. That said, there should be some way to specialize operator() in the functor passed to it in order to correctly handle array types. > typedef std::tuple<short, > int, > std::array<int, 2>, // note std::array > std::string > test_t; You inspired me with your use of std::array to try it out in my example. I changed "print_me" to use t.second instead of just t (which is correct) and then made a template function to support std::array with std::cout. That did the trick. Of course, the real goal here would be to handle it on the for_each side not the cout side, as outputting the types is not always the goal. > test_t test{1, 2, {}, {"hello"}}; You know one other weird thing, is that with boost 1.53 I could initialize this with std::array<int, 2> as: test_1 test{1,2, {{3,4}}, {"hello"}}; Now with 1.55 it's only working with: test_1 test{1,2,std::int<array, 2>{3, 4}, "hello"}; //missing braces on string correct I'm using both gcc 4.8.3 and clang 3.4.1. Steven

2 1

[thread] mutex is locked
by gast128 29 Jun '14

29 Jun '14

Dear all, does anybody know if there is a possibility to check if a mutex is locked? There is an 'owns_lock' on the lock type but not on the mutex. The main use case for me is debugging (and documentation) purposes: void MyClass::Process() { boost::unique_lock<boost::mutex> lck(m_mtx); ProcessImpl(); } void MyClass::ProcessImpl() { _ASSERT(m_mtx.is_locked()); //does not exist :( }

4 4

Selecting one element per fusion sequence using mpl::int_s
by gsermaid 29 Jun '14

29 Jun '14

Dear all, I am trying to create a fusion sequence whose elements are non-const references to the elements of given set of sequences. In particular, for a given sequence of integral constants, say vector< int_<2>, int_<1> >, and two fusion sequences, say X = vector< X0, X1, X2, X3 > and Y = vector< Y0, Y1, Y2 >, I would like to create the following sequence R = vector< X2&, Y1& >, such that at<0>(R) == at<2>(X) and at<1>(R) == at<1>(Y). I am using fusion::transform to achieve the above but the transform function takes the sequences as const references so I end up with R = vector<const X2&, const Y1&>, which is not what I want. Below is my code; any ideas on how to get a sequence of non-const references would be greatly appreciated. Thanks for reading! #include <boost/fusion/include/vector.hpp> #include <boost/fusion/include/transform.hpp> #include <boost/fusion/sequence/io/out.hpp> #include <boost/fusion/include/at.hpp> #include <boost/mpl/assert.hpp> #include <boost/type_traits.hpp> #include <iostream> using namespace boost::fusion; using boost::mpl::int_; using my_ints = vector< int_<2>, int_<1> >; using my_x = vector<int, double, unsigned, float>; using my_y = vector<unsigned, float, long>; using joined = vector<my_x, my_y>; struct my_functor { template <class I, class Seq> typename result_of::at<Seq, I>::type operator()(I& i, Seq& seq) const { return boost::fusion::at<I>(seq); } }; int main() { my_ints ints; my_x x(-2, 3.5, 15, -1.3); my_y y(4, 10.1, 100); joined jv(x, y); auto tv = transform(ints, jv, my_functor()); std::cout << tv << std::endl; // prints (15 10.1) // these two fail to compile because the first argument is const-qualified BOOST_MPL_ASSERT(( boost::is_same< decltype(at_c<0>(tv)), unsigned& > )); BOOST_MPL_ASSERT(( boost::is_same< decltype(at_c<1>(tv)), float& > )); }

2 1

[fusion] maps and arrays
by Seeger, Steven D. (GSFC-444.0)[Embedded Flight Systems, Inc] 28 Jun '14

28 Jun '14

I've had some code written with boost 1.53 a while ago that uses fusion maps to define at compile-time packet structures. There is then compile time generated code that handles marshaling, unmarshaling, and packet size calculation on these structures. One of the big reasons for going this route was the ability to have arrays contained in the packets. When upgrading from boost 1.53 to 1.55 on my Gentoo box, this all broke. I posted a bug report at https://svn.boost.org/trac/boost/ticket/10133 but it seems fusion bug reports don't get much activity here. I'm contacting the list to ask if the use of arrays in containers was just a fluke or if it should be working and something happened in 1.55 (or possibly 1.54 which I never tried.) If this is not something that should be supported then I will abandon this code and go with something else. It's been really nice to work on some client/server stuff with it because the work that went in to handle the code generation saves a lot of time going forward. Thanks, Steven

2 1

Boost.Coroutine with segmentation fault
by Van Pers 27 Jun '14

27 Jun '14

Hi all, I am writting a code with Coroutines lib, this code uses coroutines in a recursive way but when I create a large number of coroutines the program crashes (segmentation fault). I write a simplified version that reproduces this error: #include<iostream> #include<cstdlib> #include<boost/coroutine/all.hpp> #include <boost/bind.hpp> #include <boost/shared_ptr.hpp> class FClass{ private: int n; public: boost::coroutines::coroutine<void>::pull_type* startResume; FClass(int n) : n(n){ startResume = NULL; } void resume(){ if(startResume && *(startResume)) (*(startResume))(); } void doSomething ( boost::coroutines::coroutine< void >::push_type & fPause){ if (n > 2){ FClass* tc1 = new FClass(--n); tc1->startResume = new boost::coroutines::coroutine<void>::pull_type( boost::bind( &FClass::doSomething, tc1, _1) ); FClass* tc2 = new FClass(--n); tc2->startResume = new boost::coroutines::coroutine<void>::pull_type( boost::bind( &FClass::doSomething, tc2, _1) ); fPause(); tc1->resume(); tc2->resume(); } return; } }; int main(int argc, char** argv){ int max = 10; if (argc > 1){ max = atoi(argv[1]); } FClass* firstObject = new FClass (max) ; firstObject->startResume = new boost::coroutines::coroutine<void>::pull_type( boost::bind(&FClass::doSomething, firstObject, _1) ); firstObject->resume(); } gdb output reports:"memset () at ../sysdeps/x86_64/memset.S:78 ../sysdeps/x86_64/memset.S:No such file or directory." Anybody can help me? Regards, Van

1 0

core when using managed shared memory -- file based
by Sean K 27 Jun '14

27 Jun '14

I have a client and server set up where the client would write to the shared memory via a managed memory vector. And then the server would read that shared memory via the managed mapped file. It works for most situations. However, I just ran into a situation where the client -- writing to the vector, crashes. and I am trying to figure out what caused the crash. Below are the client (writer) and the server (reader) source code.... as close as to the current. Any insights as to why the vector.push_back() crashed? (this is happening on RH 5.9 64 bit OS.. but the code is compiled for 32 bit.) client: #include <iostream> #include <iostream> #include <string> #include <cstdlib> using namespace std; #include "fileheader.h" int main() { std::string data = "Hello"; char myinput[1024]; printf("enter number of count \n"); scanf("%s", &myinput); printf("You entered %s \n", myinput); data = myinput; int count = std::atoi(myinput); for (int counter = 0; counter < count; counter ++) { try { std::string tmpPath = "/var/tmp/log/testfile/ManagedMappedFile";; printf("temp directory: %s \n", tmpPath.c_str()); managed_mapped_file segment(open_or_create, tmpPath.c_str(), SHARED_MEMORY_SIZE); printf("initialized managed shared memory \n"); BString bstrData(segment.get_segment_manager()); bstrData = "hello world"; StrAllocator alloc_init(segment.get_segment_manager()); printf("ALLOCATED memory successfully\n"); BStrVector *myvec = segment.find_or_construct<BStrVector> (SHARED_VECTOR_NAME)(alloc_init); myvec->push_back(bstrData); segment.flush(); printf("inserted mystring into shmvector %d\n", counter); } catch (boost::interprocess::bad_alloc e) { printf("we caught bad alloc\n"); printf("explanation: %s\n", e.what()); printf("error code: %d\n", e.get_error_code()); printf("native: %d\n", e.get_native_error()); break; } catch (...) { printf("caught unknown exception\n"); } } printf("wrote number"); return 0; } contents of fileheader.h #ifndef FILEHEADER_H_ #define FILEHEADER_H_ #include <boost/interprocess/managed_shared_memory.hpp> #include <boost/interprocess/managed_mapped_file.hpp> #include <boost/thread/thread.hpp> #include <boost/interprocess/containers/vector.hpp> #include <boost/interprocess/containers/string.hpp> #include <boost/interprocess/allocators/allocator.hpp> #include <boost/interprocess/detail/tmp_dir_helpers.hpp> using namespace boost::interprocess; typedef boost::interprocess::managed_mapped_file::segment_manager segment_manager_t; typedef boost::interprocess::allocator<char, segment_manager_t> ShmemAllocator; typedef boost::interprocess::basic_string<char, std::char_traits<char>, ShmemAllocator> BString; typedef boost::interprocess::allocator<BString, segment_manager_t> StrAllocator; typedef boost::interprocess::vector<BString, StrAllocator> BStrVector; typedef std::pair<BString *, std::size_t> BStringPair; typedef std::pair<BStrVector *, std::size_t> BStrVectorPair; const char * SHARED_VECTOR_NAME = "MyVector"; const int SHARED_MEMORY_SIZE = 65536; #endif /* FILEHEADER_H_ */ g++ -m32 -fPIC -Xlinker -zmuldefs filewriter.cpp -o writer -I/cots/boost_1_42_0/include -L/cots/boost_1_42_0/lib -lboost_thread -lboost_system -pthread Server: #include <iostream> #include <string> #include <cstdlib> using namespace std; #include "../../filewriter/src/fileheader.h" int main() { int count = 0; std::string tmpPath = "/var/tmp/log/testfile"; //boost::interprocess::detail::get_tmp_base_dir(tmpPath); printf("temp directory: %s \n", tmpPath.c_str()); //boost::interprocess::detail::create_tmp_dir_and_get_filename("ManagedMappedFile", tmpPath); printf("temp file: %s \n", tmpPath.c_str()); // file_mapping::remove(tmpPath.c_str()); while (true) { try { managed_mapped_file segment(open_only, tmpPath.c_str()); if (segment.get_num_named_objects() > 0){ BStrVectorPair message = segment.find<BStrVector> (SHARED_VECTOR_NAME); printf("stuff in memory\n"); int size = message.first->size(); int retcode = 0; bool success=true; printf("PROCESS: Number of messages: %d\n", size); for (int imessage=0; imessage < size ; imessage++){ const char * const buffer = message.first->at(imessage).c_str(); int len = message.first->at(imessage).length(); printf("PROCESS: going to process this message: %s\n" , buffer); } printf("p.second: %d \n", message.second); segment.destroy<BStrVectorPair>(SHARED_VECTOR_NAME); } } catch (exception& e){ printf("exception %s", e.what()); } catch (...){ printf("unexpected exception"); } int msecs = 2000; boost::this_thread::sleep(boost::posix_time::milliseconds(msecs)); printf("sleeping...\n"); } return 0; } g++ -m32 -fPIC -Xlinker -zmuldefs filereader.cpp -o reader -I/cots/boost_1_42_0/include -L/cots/boost_1_42_0/lib -lboost_thread -lboost_system -pthread

1 0

Unexpected behavior when using as::ftime() of Boost Locale library
by Mouse Beer 27 Jun '14

27 Jun '14

Hi all, I see a mismatch when using %Y format specifier with as::ftime. It looks like it outputs the year according to the week of the year. I hope I didn't miss or misunderstand anything... please find my small test program attached for reference. It was compiled as follows: g++ -g -Wall -I /opt/boost/1.55/include -L /opt/boost/1.55/lib -lboost_locale -lboost_thread -lboost_system -licuuc -licui18n -licudata -lpthread -lrt boost_dates_test.cpp I am running on Debian Testing: $ ldd a.out linux-vdso.so.1 (0x00007fffa39fe000) libboost_locale.so.1.55.0 => /opt/boost/1.55/lib/libboost_locale.so.1.55.0 (0x00007fba3335b000) libboost_thread.so.1.55.0 => /opt/boost/1.55/lib/libboost_thread.so.1.55.0 (0x00007fba33142000) libboost_system.so.1.55.0 => /opt/boost/1.55/lib/libboost_system.so.1.55.0 (0x00007fba32f3e000) libicuuc.so.52 => /usr/lib/x86_64-linux-gnu/libicuuc.so.52 (0x00007fba32ba2000) libicui18n.so.52 => /usr/lib/x86_64-linux-gnu/libicui18n.so.52 (0x00007fba3279a000) libicudata.so.52 => /usr/lib/x86_64-linux-gnu/libicudata.so.52 (0x00007fba30f2c000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fba30d0f000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fba30b07000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fba307fb000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fba304fa000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fba302e4000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fba2ff3a000) libboost_chrono.so.1.55.0 => /opt/boost/1.55/lib/libboost_chrono.so.1.55.0 (0x00007fba2fd34000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fba2fb2f000) /lib64/ld-linux-x86-64.so.2 (0x00007fba33642000) The program shows the output of cout<<date_time and cout<<as:ftime("%Y-%m...")<<date_time If a mismatch in the year is detected, a "!" is added at the end of the line. When running with en_US locale, the output is as follows: [ 10:49:40 ] [0] $ export LC_ALL=en_US.utf8 [ 10:50:39 ] [0] $ locale LANG= LANGUAGE= LC_CTYPE="en_US.utf8" LC_NUMERIC="en_US.utf8" LC_TIME="en_US.utf8" LC_COLLATE="en_US.utf8" LC_MONETARY="en_US.utf8" LC_MESSAGES="en_US.utf8" LC_PAPER="en_US.utf8" LC_NAME="en_US.utf8" LC_ADDRESS="en_US.utf8" LC_TELEPHONE="en_US.utf8" LC_MEASUREMENT="en_US.utf8" LC_IDENTIFICATION="en_US.utf8" LC_ALL=en_US.utf8 [ 10:50:41 ] [0] $ ./a.out Dec 27, 2000, 12:00:00 AM ++ 2000-12-27 00:00:00 Dec 28, 2000, 12:00:00 AM ++ 2000-12-28 00:00:00 Dec 29, 2000, 12:00:00 AM ++ 2000-12-29 00:00:00 Dec 30, 2000, 12:00:00 AM ++ 2000-12-30 00:00:00 Dec 31, 2000, 12:00:00 AM ++ 2001-12-31 00:00:00 ! Jan 1, 2001, 12:00:00 AM ++ 2001-01-01 00:00:00 Jan 2, 2001, 12:00:00 AM ++ 2001-01-02 00:00:00 Jan 3, 2001, 12:00:00 AM ++ 2001-01-03 00:00:00 Jan 4, 2001, 12:00:00 AM ++ 2001-01-04 00:00:00 Jan 5, 2001, 12:00:00 AM ++ 2001-01-05 00:00:00 Dec 27, 2001, 12:00:00 AM ++ 2001-12-27 00:00:00 Dec 28, 2001, 12:00:00 AM ++ 2001-12-28 00:00:00 Dec 29, 2001, 12:00:00 AM ++ 2001-12-29 00:00:00 Dec 30, 2001, 12:00:00 AM ++ 2002-12-30 00:00:00 ! Dec 31, 2001, 12:00:00 AM ++ 2002-12-31 00:00:00 ! Jan 1, 2002, 12:00:00 AM ++ 2002-01-01 00:00:00 Jan 2, 2002, 12:00:00 AM ++ 2002-01-02 00:00:00 Jan 3, 2002, 12:00:00 AM ++ 2002-01-03 00:00:00 Jan 4, 2002, 12:00:00 AM ++ 2002-01-04 00:00:00 Jan 5, 2002, 12:00:00 AM ++ 2002-01-05 00:00:00 Dec 27, 2002, 12:00:00 AM ++ 2002-12-27 00:00:00 Dec 28, 2002, 12:00:00 AM ++ 2002-12-28 00:00:00 Dec 29, 2002, 12:00:00 AM ++ 2003-12-29 00:00:00 ! Dec 30, 2002, 12:00:00 AM ++ 2003-12-30 00:00:00 ! Dec 31, 2002, 12:00:00 AM ++ 2003-12-31 00:00:00 ! Jan 1, 2003, 12:00:00 AM ++ 2003-01-01 00:00:00 Jan 2, 2003, 12:00:00 AM ++ 2003-01-02 00:00:00 Jan 3, 2003, 12:00:00 AM ++ 2003-01-03 00:00:00 Jan 4, 2003, 12:00:00 AM ++ 2003-01-04 00:00:00 Jan 5, 2003, 12:00:00 AM ++ 2003-01-05 00:00:00 Dec 27, 2003, 12:00:00 AM ++ 2003-12-27 00:00:00 Dec 28, 2003, 12:00:00 AM ++ 2004-12-28 00:00:00 ! Dec 29, 2003, 12:00:00 AM ++ 2004-12-29 00:00:00 ! Dec 30, 2003, 12:00:00 AM ++ 2004-12-30 00:00:00 ! Dec 31, 2003, 12:00:00 AM ++ 2004-12-31 00:00:00 ! Jan 1, 2004, 12:00:00 AM ++ 2004-01-01 00:00:00 Jan 2, 2004, 12:00:00 AM ++ 2004-01-02 00:00:00 Jan 3, 2004, 12:00:00 AM ++ 2004-01-03 00:00:00 Jan 4, 2004, 12:00:00 AM ++ 2004-01-04 00:00:00 Jan 5, 2004, 12:00:00 AM ++ 2004-01-05 00:00:00 Dec 27, 2004, 12:00:00 AM ++ 2005-12-27 00:00:00 ! Dec 28, 2004, 12:00:00 AM ++ 2005-12-28 00:00:00 ! Dec 29, 2004, 12:00:00 AM ++ 2005-12-29 00:00:00 ! Dec 30, 2004, 12:00:00 AM ++ 2005-12-30 00:00:00 ! Dec 31, 2004, 12:00:00 AM ++ 2005-12-31 00:00:00 ! Jan 1, 2005, 12:00:00 AM ++ 2005-01-01 00:00:00 Jan 2, 2005, 12:00:00 AM ++ 2005-01-02 00:00:00 Jan 3, 2005, 12:00:00 AM ++ 2005-01-03 00:00:00 Jan 4, 2005, 12:00:00 AM ++ 2005-01-04 00:00:00 Jan 5, 2005, 12:00:00 AM ++ 2005-01-05 00:00:00 Dec 27, 2005, 12:00:00 AM ++ 2005-12-27 00:00:00 Dec 28, 2005, 12:00:00 AM ++ 2005-12-28 00:00:00 Dec 29, 2005, 12:00:00 AM ++ 2005-12-29 00:00:00 Dec 30, 2005, 12:00:00 AM ++ 2005-12-30 00:00:00 Dec 31, 2005, 12:00:00 AM ++ 2005-12-31 00:00:00 Jan 1, 2006, 12:00:00 AM ++ 2006-01-01 00:00:00 Jan 2, 2006, 12:00:00 AM ++ 2006-01-02 00:00:00 Jan 3, 2006, 12:00:00 AM ++ 2006-01-03 00:00:00 Jan 4, 2006, 12:00:00 AM ++ 2006-01-04 00:00:00 Jan 5, 2006, 12:00:00 AM ++ 2006-01-05 00:00:00 Dec 27, 2006, 12:00:00 AM ++ 2006-12-27 00:00:00 Dec 28, 2006, 12:00:00 AM ++ 2006-12-28 00:00:00 Dec 29, 2006, 12:00:00 AM ++ 2006-12-29 00:00:00 Dec 30, 2006, 12:00:00 AM ++ 2006-12-30 00:00:00 Dec 31, 2006, 12:00:00 AM ++ 2007-12-31 00:00:00 ! Jan 1, 2007, 12:00:00 AM ++ 2007-01-01 00:00:00 Jan 2, 2007, 12:00:00 AM ++ 2007-01-02 00:00:00 Jan 3, 2007, 12:00:00 AM ++ 2007-01-03 00:00:00 Jan 4, 2007, 12:00:00 AM ++ 2007-01-04 00:00:00 Jan 5, 2007, 12:00:00 AM ++ 2007-01-05 00:00:00 Dec 27, 2007, 12:00:00 AM ++ 2007-12-27 00:00:00 Dec 28, 2007, 12:00:00 AM ++ 2007-12-28 00:00:00 Dec 29, 2007, 12:00:00 AM ++ 2007-12-29 00:00:00 Dec 30, 2007, 12:00:00 AM ++ 2008-12-30 00:00:00 ! Dec 31, 2007, 12:00:00 AM ++ 2008-12-31 00:00:00 ! Jan 1, 2008, 12:00:00 AM ++ 2008-01-01 00:00:00 Jan 2, 2008, 12:00:00 AM ++ 2008-01-02 00:00:00 Jan 3, 2008, 12:00:00 AM ++ 2008-01-03 00:00:00 Jan 4, 2008, 12:00:00 AM ++ 2008-01-04 00:00:00 Jan 5, 2008, 12:00:00 AM ++ 2008-01-05 00:00:00 Dec 27, 2008, 12:00:00 AM ++ 2008-12-27 00:00:00 Dec 28, 2008, 12:00:00 AM ++ 2009-12-28 00:00:00 ! Dec 29, 2008, 12:00:00 AM ++ 2009-12-29 00:00:00 ! Dec 30, 2008, 12:00:00 AM ++ 2009-12-30 00:00:00 ! Dec 31, 2008, 12:00:00 AM ++ 2009-12-31 00:00:00 ! Jan 1, 2009, 12:00:00 AM ++ 2009-01-01 00:00:00 Jan 2, 2009, 12:00:00 AM ++ 2009-01-02 00:00:00 Jan 3, 2009, 12:00:00 AM ++ 2009-01-03 00:00:00 Jan 4, 2009, 12:00:00 AM ++ 2009-01-04 00:00:00 Jan 5, 2009, 12:00:00 AM ++ 2009-01-05 00:00:00 Dec 27, 2009, 12:00:00 AM ++ 2010-12-27 00:00:00 ! Dec 28, 2009, 12:00:00 AM ++ 2010-12-28 00:00:00 ! Dec 29, 2009, 12:00:00 AM ++ 2010-12-29 00:00:00 ! Dec 30, 2009, 12:00:00 AM ++ 2010-12-30 00:00:00 ! Dec 31, 2009, 12:00:00 AM ++ 2010-12-31 00:00:00 ! Jan 1, 2010, 12:00:00 AM ++ 2010-01-01 00:00:00 Jan 2, 2010, 12:00:00 AM ++ 2010-01-02 00:00:00 Jan 3, 2010, 12:00:00 AM ++ 2010-01-03 00:00:00 Jan 4, 2010, 12:00:00 AM ++ 2010-01-04 00:00:00 Jan 5, 2010, 12:00:00 AM ++ 2010-01-05 00:00:00 Dec 27, 2010, 12:00:00 AM ++ 2011-12-27 00:00:00 ! Dec 28, 2010, 12:00:00 AM ++ 2011-12-28 00:00:00 ! Dec 29, 2010, 12:00:00 AM ++ 2011-12-29 00:00:00 ! Dec 30, 2010, 12:00:00 AM ++ 2011-12-30 00:00:00 ! Dec 31, 2010, 12:00:00 AM ++ 2011-12-31 00:00:00 ! Jan 1, 2011, 12:00:00 AM ++ 2011-01-01 00:00:00 Jan 2, 2011, 12:00:00 AM ++ 2011-01-02 00:00:00 Jan 3, 2011, 12:00:00 AM ++ 2011-01-03 00:00:00 Jan 4, 2011, 12:00:00 AM ++ 2011-01-04 00:00:00 Jan 5, 2011, 12:00:00 AM ++ 2011-01-05 00:00:00 Dec 27, 2011, 12:00:00 AM ++ 2011-12-27 00:00:00 Dec 28, 2011, 12:00:00 AM ++ 2011-12-28 00:00:00 Dec 29, 2011, 12:00:00 AM ++ 2011-12-29 00:00:00 Dec 30, 2011, 12:00:00 AM ++ 2011-12-30 00:00:00 Dec 31, 2011, 12:00:00 AM ++ 2011-12-31 00:00:00 Jan 1, 2012, 12:00:00 AM ++ 2012-01-01 00:00:00 Jan 2, 2012, 12:00:00 AM ++ 2012-01-02 00:00:00 Jan 3, 2012, 12:00:00 AM ++ 2012-01-03 00:00:00 Jan 4, 2012, 12:00:00 AM ++ 2012-01-04 00:00:00 Jan 5, 2012, 12:00:00 AM ++ 2012-01-05 00:00:00 Dec 27, 2012, 12:00:00 AM ++ 2012-12-27 00:00:00 Dec 28, 2012, 12:00:00 AM ++ 2012-12-28 00:00:00 Dec 29, 2012, 12:00:00 AM ++ 2012-12-29 00:00:00 Dec 30, 2012, 12:00:00 AM ++ 2013-12-30 00:00:00 ! Dec 31, 2012, 12:00:00 AM ++ 2013-12-31 00:00:00 ! Jan 1, 2013, 12:00:00 AM ++ 2013-01-01 00:00:00 Jan 2, 2013, 12:00:00 AM ++ 2013-01-02 00:00:00 Jan 3, 2013, 12:00:00 AM ++ 2013-01-03 00:00:00 Jan 4, 2013, 12:00:00 AM ++ 2013-01-04 00:00:00 Jan 5, 2013, 12:00:00 AM ++ 2013-01-05 00:00:00 Dec 27, 2013, 12:00:00 AM ++ 2013-12-27 00:00:00 Dec 28, 2013, 12:00:00 AM ++ 2013-12-28 00:00:00 Dec 29, 2013, 12:00:00 AM ++ 2014-12-29 00:00:00 ! Dec 30, 2013, 12:00:00 AM ++ 2014-12-30 00:00:00 ! Dec 31, 2013, 12:00:00 AM ++ 2014-12-31 00:00:00 ! Jan 1, 2014, 12:00:00 AM ++ 2014-01-01 00:00:00 Jan 2, 2014, 12:00:00 AM ++ 2014-01-02 00:00:00 Jan 3, 2014, 12:00:00 AM ++ 2014-01-03 00:00:00 Jan 4, 2014, 12:00:00 AM ++ 2014-01-04 00:00:00 Jan 5, 2014, 12:00:00 AM ++ 2014-01-05 00:00:00 When running with de_DE locale, the output is as follows: [ 10:51:42 ] [0] $ export LC_ALL=de_DE.utf8 [ 10:55:04 ] [0] $ locale LANG= LANGUAGE= LC_CTYPE="de_DE.utf8" LC_NUMERIC="de_DE.utf8" LC_TIME="de_DE.utf8" LC_COLLATE="de_DE.utf8" LC_MONETARY="de_DE.utf8" LC_MESSAGES="de_DE.utf8" LC_PAPER="de_DE.utf8" LC_NAME="de_DE.utf8" LC_ADDRESS="de_DE.utf8" LC_TELEPHONE="de_DE.utf8" LC_MEASUREMENT="de_DE.utf8" LC_IDENTIFICATION="de_DE.utf8" LC_ALL=de_DE.utf8 [ 10:55:05 ] [0] $ ./a.out 27.12.2000 00:00:00 ++ 2000-12-27 00:00:00 28.12.2000 00:00:00 ++ 2000-12-28 00:00:00 29.12.2000 00:00:00 ++ 2000-12-29 00:00:00 30.12.2000 00:00:00 ++ 2000-12-30 00:00:00 31.12.2000 00:00:00 ++ 2000-12-31 00:00:00 01.01.2001 00:00:00 ++ 2001-01-01 00:00:00 02.01.2001 00:00:00 ++ 2001-01-02 00:00:00 03.01.2001 00:00:00 ++ 2001-01-03 00:00:00 04.01.2001 00:00:00 ++ 2001-01-04 00:00:00 05.01.2001 00:00:00 ++ 2001-01-05 00:00:00 27.12.2001 00:00:00 ++ 2001-12-27 00:00:00 28.12.2001 00:00:00 ++ 2001-12-28 00:00:00 29.12.2001 00:00:00 ++ 2001-12-29 00:00:00 30.12.2001 00:00:00 ++ 2001-12-30 00:00:00 31.12.2001 00:00:00 ++ 2002-12-31 00:00:00 ! 01.01.2002 00:00:00 ++ 2002-01-01 00:00:00 02.01.2002 00:00:00 ++ 2002-01-02 00:00:00 03.01.2002 00:00:00 ++ 2002-01-03 00:00:00 04.01.2002 00:00:00 ++ 2002-01-04 00:00:00 05.01.2002 00:00:00 ++ 2002-01-05 00:00:00 27.12.2002 00:00:00 ++ 2002-12-27 00:00:00 28.12.2002 00:00:00 ++ 2002-12-28 00:00:00 29.12.2002 00:00:00 ++ 2002-12-29 00:00:00 30.12.2002 00:00:00 ++ 2003-12-30 00:00:00 ! 31.12.2002 00:00:00 ++ 2003-12-31 00:00:00 ! 01.01.2003 00:00:00 ++ 2003-01-01 00:00:00 02.01.2003 00:00:00 ++ 2003-01-02 00:00:00 03.01.2003 00:00:00 ++ 2003-01-03 00:00:00 04.01.2003 00:00:00 ++ 2003-01-04 00:00:00 05.01.2003 00:00:00 ++ 2003-01-05 00:00:00 27.12.2003 00:00:00 ++ 2003-12-27 00:00:00 28.12.2003 00:00:00 ++ 2003-12-28 00:00:00 29.12.2003 00:00:00 ++ 2004-12-29 00:00:00 ! 30.12.2003 00:00:00 ++ 2004-12-30 00:00:00 ! 31.12.2003 00:00:00 ++ 2004-12-31 00:00:00 ! 01.01.2004 00:00:00 ++ 2004-01-01 00:00:00 02.01.2004 00:00:00 ++ 2004-01-02 00:00:00 03.01.2004 00:00:00 ++ 2004-01-03 00:00:00 04.01.2004 00:00:00 ++ 2004-01-04 00:00:00 05.01.2004 00:00:00 ++ 2004-01-05 00:00:00 27.12.2004 00:00:00 ++ 2004-12-27 00:00:00 28.12.2004 00:00:00 ++ 2004-12-28 00:00:00 29.12.2004 00:00:00 ++ 2004-12-29 00:00:00 30.12.2004 00:00:00 ++ 2004-12-30 00:00:00 31.12.2004 00:00:00 ++ 2004-12-31 00:00:00 01.01.2005 00:00:00 ++ 2004-01-01 00:00:00 ! 02.01.2005 00:00:00 ++ 2004-01-02 00:00:00 ! 03.01.2005 00:00:00 ++ 2005-01-03 00:00:00 04.01.2005 00:00:00 ++ 2005-01-04 00:00:00 05.01.2005 00:00:00 ++ 2005-01-05 00:00:00 27.12.2005 00:00:00 ++ 2005-12-27 00:00:00 28.12.2005 00:00:00 ++ 2005-12-28 00:00:00 29.12.2005 00:00:00 ++ 2005-12-29 00:00:00 30.12.2005 00:00:00 ++ 2005-12-30 00:00:00 31.12.2005 00:00:00 ++ 2005-12-31 00:00:00 01.01.2006 00:00:00 ++ 2005-01-01 00:00:00 ! 02.01.2006 00:00:00 ++ 2006-01-02 00:00:00 03.01.2006 00:00:00 ++ 2006-01-03 00:00:00 04.01.2006 00:00:00 ++ 2006-01-04 00:00:00 05.01.2006 00:00:00 ++ 2006-01-05 00:00:00 27.12.2006 00:00:00 ++ 2006-12-27 00:00:00 28.12.2006 00:00:00 ++ 2006-12-28 00:00:00 29.12.2006 00:00:00 ++ 2006-12-29 00:00:00 30.12.2006 00:00:00 ++ 2006-12-30 00:00:00 31.12.2006 00:00:00 ++ 2006-12-31 00:00:00 01.01.2007 00:00:00 ++ 2007-01-01 00:00:00 02.01.2007 00:00:00 ++ 2007-01-02 00:00:00 03.01.2007 00:00:00 ++ 2007-01-03 00:00:00 04.01.2007 00:00:00 ++ 2007-01-04 00:00:00 05.01.2007 00:00:00 ++ 2007-01-05 00:00:00 27.12.2007 00:00:00 ++ 2007-12-27 00:00:00 28.12.2007 00:00:00 ++ 2007-12-28 00:00:00 29.12.2007 00:00:00 ++ 2007-12-29 00:00:00 30.12.2007 00:00:00 ++ 2007-12-30 00:00:00 31.12.2007 00:00:00 ++ 2008-12-31 00:00:00 ! 01.01.2008 00:00:00 ++ 2008-01-01 00:00:00 02.01.2008 00:00:00 ++ 2008-01-02 00:00:00 03.01.2008 00:00:00 ++ 2008-01-03 00:00:00 04.01.2008 00:00:00 ++ 2008-01-04 00:00:00 05.01.2008 00:00:00 ++ 2008-01-05 00:00:00 27.12.2008 00:00:00 ++ 2008-12-27 00:00:00 28.12.2008 00:00:00 ++ 2008-12-28 00:00:00 29.12.2008 00:00:00 ++ 2009-12-29 00:00:00 ! 30.12.2008 00:00:00 ++ 2009-12-30 00:00:00 ! 31.12.2008 00:00:00 ++ 2009-12-31 00:00:00 ! 01.01.2009 00:00:00 ++ 2009-01-01 00:00:00 02.01.2009 00:00:00 ++ 2009-01-02 00:00:00 03.01.2009 00:00:00 ++ 2009-01-03 00:00:00 04.01.2009 00:00:00 ++ 2009-01-04 00:00:00 05.01.2009 00:00:00 ++ 2009-01-05 00:00:00 27.12.2009 00:00:00 ++ 2009-12-27 00:00:00 28.12.2009 00:00:00 ++ 2009-12-28 00:00:00 29.12.2009 00:00:00 ++ 2009-12-29 00:00:00 30.12.2009 00:00:00 ++ 2009-12-30 00:00:00 31.12.2009 00:00:00 ++ 2009-12-31 00:00:00 01.01.2010 00:00:00 ++ 2009-01-01 00:00:00 ! 02.01.2010 00:00:00 ++ 2009-01-02 00:00:00 ! 03.01.2010 00:00:00 ++ 2009-01-03 00:00:00 ! 04.01.2010 00:00:00 ++ 2010-01-04 00:00:00 05.01.2010 00:00:00 ++ 2010-01-05 00:00:00 27.12.2010 00:00:00 ++ 2010-12-27 00:00:00 28.12.2010 00:00:00 ++ 2010-12-28 00:00:00 29.12.2010 00:00:00 ++ 2010-12-29 00:00:00 30.12.2010 00:00:00 ++ 2010-12-30 00:00:00 31.12.2010 00:00:00 ++ 2010-12-31 00:00:00 01.01.2011 00:00:00 ++ 2010-01-01 00:00:00 ! 02.01.2011 00:00:00 ++ 2010-01-02 00:00:00 ! 03.01.2011 00:00:00 ++ 2011-01-03 00:00:00 04.01.2011 00:00:00 ++ 2011-01-04 00:00:00 05.01.2011 00:00:00 ++ 2011-01-05 00:00:00 27.12.2011 00:00:00 ++ 2011-12-27 00:00:00 28.12.2011 00:00:00 ++ 2011-12-28 00:00:00 29.12.2011 00:00:00 ++ 2011-12-29 00:00:00 30.12.2011 00:00:00 ++ 2011-12-30 00:00:00 31.12.2011 00:00:00 ++ 2011-12-31 00:00:00 01.01.2012 00:00:00 ++ 2011-01-01 00:00:00 ! 02.01.2012 00:00:00 ++ 2012-01-02 00:00:00 03.01.2012 00:00:00 ++ 2012-01-03 00:00:00 04.01.2012 00:00:00 ++ 2012-01-04 00:00:00 05.01.2012 00:00:00 ++ 2012-01-05 00:00:00 27.12.2012 00:00:00 ++ 2012-12-27 00:00:00 28.12.2012 00:00:00 ++ 2012-12-28 00:00:00 29.12.2012 00:00:00 ++ 2012-12-29 00:00:00 30.12.2012 00:00:00 ++ 2012-12-30 00:00:00 31.12.2012 00:00:00 ++ 2013-12-31 00:00:00 ! 01.01.2013 00:00:00 ++ 2013-01-01 00:00:00 02.01.2013 00:00:00 ++ 2013-01-02 00:00:00 03.01.2013 00:00:00 ++ 2013-01-03 00:00:00 04.01.2013 00:00:00 ++ 2013-01-04 00:00:00 05.01.2013 00:00:00 ++ 2013-01-05 00:00:00 27.12.2013 00:00:00 ++ 2013-12-27 00:00:00 28.12.2013 00:00:00 ++ 2013-12-28 00:00:00 29.12.2013 00:00:00 ++ 2013-12-29 00:00:00 30.12.2013 00:00:00 ++ 2014-12-30 00:00:00 ! 31.12.2013 00:00:00 ++ 2014-12-31 00:00:00 ! 01.01.2014 00:00:00 ++ 2014-01-01 00:00:00 02.01.2014 00:00:00 ++ 2014-01-02 00:00:00 03.01.2014 00:00:00 ++ 2014-01-03 00:00:00 04.01.2014 00:00:00 ++ 2014-01-04 00:00:00 05.01.2014 00:00:00 ++ 2014-01-05 00:00:00 Sorry for the long post! Did I make any mistake in my program or is this a bug of as::ftime("%Y") formatting? Thank you yery much for your help! Regards, Holger

1 0

[Boost : icpc assignment operator compiler error with boost filter_iterator and filtered_graph
by Aniket Pugaonkar 26 Jun '14

26 Jun '14

Hello, I have the following filter iterator working perfectly with gcc 4.7 and 4.9 as well (C++11 support) But when I compile my code with intel compiler 13.0.1 version I get the following error error: *implicitly generated assignment operator cannot copy: reference member* "my_func::G" ... Details: I am using a filtered_graph over Boost::adjacency_list as my graph type (Graph_t). The vertex_iterator (from graph_traits<Graph_t> .. provides iterator range to iterate over graph vertices. I have to assign each graph vertex an id (using property_maps) and group them together by applying filter_iterator over vertex iterator. example: suppose I want to create 4 subgroups of vertices. So I create a filter predicate which is passed to filter iterator which gives me iterators <fbegin, fend> satisfying the predicate. For FOUR such groups, I get 4 pairs of filter iterators. A vector stores such filter_iterator pairs. std::vector < pair <filter_iterator_t, filter_iterator_t> > my_vector //stores iterator pair. Here is the code: vertex_iterator vbegin, vend; boost::tie(vbegin, vend) = boost::vertices(G); for (int i=0; i<4; ++i) { //for each i, create a filter_pred object my_filter_pred <Graph> filter_pred(G, i) //now create begin and end filter iterators as follows auto fbegin = boost::make_filter_iterator< my_filter_pred<Graph>, vertex_iterator> (filter_pred, vbegin, vend) auto fend = boost::make_filter_iterator< my_filter_pred<Graph>, vertex_iterator> (filter_pred, vend, vend) //fbegin, fend are of type filter iterator //insert the iterator pair into vector my_vector.push_back( std::make_pair (fbegin, fend) ); } The predicate is below : template<typename Graph> struct my_filter_pred { public: my_filter_pred() { } my_filter_pred(Graph& _G, int _value) : G(_G), value(_value) { } template<typename vertex_t> bool operator() (vertex_t vertex) { //get property "p" of vertex in graph G auto p = get (mypropertytype, vertex, G); return (p.val == value); } private: Graph& G; } ERROR : error: implicitly generated assignment operator cannot copy: reference member "my_filter_pred <Graph>::G [with ... ]" I tried to provide my own assignment operator as below: my_filter_pred& operator=(const my_filter_pred& other) { if (this != &other) G = other.G; return *this; } But it gave the same icpc error for actual typedef graph which is below : error: implicitly generated assignment operator cannot copy: " implicit generation of boost::filtered_graph_base<Graph_t> " .... Please help what should I do in this case to work. main motive : is to have a container which stores <iterator, iterator> pair which satisfies a predicate. Filter iterator was the best choice i could have to apply different filter predicate to same vertex_iterator range vbegin, vend; Thanks Aniket Pugaonkar Aniket Pugaonkar

1 0

[Bimap] Iterator invalidation
by Adam Badura 25 Jun '14

25 Jun '14

What are rules for iterator invalidation in Boost.Bimap? I have looked in documentation (version 1.55) but didn't found anything. I'm particularly interested in the bimap<...>::iterator (or ::const_iterator) invalidation. But the question remains valid for any kind of iterators. Adam Badura

2 2

Autobahn for C++: RPC and PubSub
by Tobias Oberstein 24 Jun '14

24 Jun '14

Hi, I'm happy to anounce Autobahn|Cpp - another subproject of Autobahn (http://autobahn.ws) this time for C++ 11 / Boost. Autobahn|Cpp allows remote procedure calls and publish & subscribe messaging for C++ application components and uses boost::future, continuations and Boost/ASIO as underlying network library. Here is how app code looks like: https://github.com/tavendo/AutobahnCpp/blob/master/README.md#show-me-some-c… Using Autobahn|Cpp, you can e.g. call your C++ code from JavaScript running in a browser. And much more. This is an early alpha version, things aren't fully hashed out, but there are a couple of examples included here: https://github.com/tavendo/AutobahnCpp/blob/master/README.md#examples Cheers, /Tobias

2 3

Boost Social Event at CppCon
by Jon Kalb 24 Jun '14

24 Jun '14

Boosters, Because a lot of Boosters are going to be attending CppCon, we¹d like to arrange a social event for Boosters/C++Now regulars. http://cppcon.org/ If you are planning to attend CppCon or even If you are just going to be in or around Bellevue, Washington between September 7th and 12 and you¹d like to join us for dinner, please let us know so we can get a count. Please send mail to: social(a)boost.org Once we settle on a date, etc, we¹ll let everyone who responded know when and where, so please let us know, even if you are a ³maybe.² This year¹s CppCon program includes sessions from a number of Boosters and C++Now regulars with sessions specifically about Boost Libraries. If you are considering attending, please be aware that the Early Bird registration deadline is just days away. http://cppcon.org/registration/ If you are attending, please make your hotel reservations soon. We are likely to sell out of our room block. http://cppcon.org/lodging/ I hope to see you at CppCon. Jon

1 0

Re: [Boost-users] [Boost.Test] BOOST_CHECK_THROW behaviour
by Ghyslain Leclerc 23 Jun '14

23 Jun '14

On 23/06/2014 17:19:01 +1200, Gavin Lambert wrote >>You could try submitting that as a bug report in Trac (if it's not already there), or waiting for Gennadiy Rozental's response. Done. I hope I did it properly. Never reported a bug on Boost before. Quoted our discussion, so that some more info is available if necessary. >>In the meantime, you'd need to write a more intelligent test yourself. I will do it manually. Found someone on Stack Overflow who wanted the same behavior I expected and did it. In case it helps someone, here is the snippet: try { … code that should throw ... BOOST_ERROR( “<function_name> did not throw anything. Expected a <exception_name>” ); } catch( <exception_name> const& ) { //ok, this is the expected case } catch(…) { BOOST_ERROR( “<function_name> has throw an unknown exception, but a <exception_name> was expected.” ); } and the reference: http://stackoverflow.com/questions/21774387/boost-unit-testing-exceptions Thanks again for your help.

1 0

[Boost.Test] BOOST_CHECK_THROW behaviour
by Ghyslain Leclerc 23 Jun '14

23 Jun '14

Hello, Sorry for the long post! I have a simple class, which I am posting a fraction of here for discussion sake: ------------------------------------------------------ class AsciiTableRow { public: void setCol( std::size_t colIdx, std::string const& newContent ); void setCol( std::size_t colIdx, const char* newContent ); private: void checkIdxBound_( std::size_t colIdx, std::string const& msg ); std::vector< std::string > data_; bool maxColWidthIsValid_; } inline void AsciiTableRow::setCol( std::size_t colIdx, std::string const& newVal ) { checkIdxBound_( colIdx, "setCol" ); maxColWidthIsValid_ = false; data_[colIdx] = newVal; } inline void AsciiTableRow::setCol( std::size_t colIdx, const char* newContent ) { setCol( colIdx, std::string( newContent ) ); } inline void AsciiTableRow::checkIdxBound_( std::size_t colIdx, std::string const& msg ) { if( colIdx > data_.size() ) { throw std::out_of_range( "AsciiTableRow::" + msg + " : colIdx out of range" ); } } ------------------------------------------------------ The code above should be sufficient for the discussion and I don’t think any other code is relevant. Should you need to see my constructor and destructor, nothing is virtual so I just copy every value and set some defaults. Nothing fancy, but I will gladly post the code if need be. What I do then is try and devise a test to see if the exception is indeed thrown and if it is the correct one. Here is the code I use: AsciiTableRow testRow; // empty, so any index will throw BOOST_CHECK_THROW( testRow.setCol( 30, 12 ), std::out_of_range ); BOOST_CHECK_THROW( testRow.setCol( 30, 12l ), std::out_of_range ); This works fine. Then, I had the idea to check what the behaviour would be if the wrong exception is thrown. I simply changed the first call like this : BOOST_CHECK_THROW( testRow.setCol( 30, 12 ), std::runtime_error ); BOOST_CHECK_THROW( testRow.setCol( 30, 12l ), std::out_of_range ); I was under the impression (and I might be wrong here, sorry :-( ) that the Boost.Test library would (the numbers are not to mean that order, simply there for enumeration): 1- output a message saying the test has failed, that an exception was indeed thrown, but it was not a runtime_error 2- continue the rest of the test (single test currently) 3- terminate but I actually never get the message of step 1, the execution of the rest of the test seems never occur (the second BOOST_CHECK_THROW) and the program terminate because of my exception and not very gracefully. I guess my questions to the other users here are: - Was my understanding of what BOOST_CHECK_THROW does flawed ? - Is the behaviour normal ? - Is there an obvious problem I am missing with the design of my simple class ? In case it is useful, I am on OSX 10.9. I have compiled boost myself (sources of version 1.55 downloaded from the Boost site). I compile my work with C++11 enabled. I am using GCC 4.7 installed via Macports. Anyhow, any insight will be appreciated. As everyone is busy, thanks in advance to anybody for any time spent on this. Ghyslain

2 1

[asio] Closing async client socket after writing last message
by Nicholas Yue 23 Jun '14

23 Jun '14

Hi, I have adapted the chat tutorial example to send messages to a similar (chat tutorial based) server. It is currently working fine however due to the async_write(), I can't close the socket until after all the pending data has been processed on the server end. I have google and found discussion and mentioned about async_write() completion handler calling socket.close() however, I was not able to find specific detail as to how that is done. I want to avoid closing the connection prematurely as it is asynchronous writing. My current do_write() looks like this void DisplayChatClient::do_write(DisplayChatMessage msg) { DLOG(INFO) << "DisplayChatClient::do_write()"; bool write_in_progress = !write_msgs_.empty(); write_msgs_.push_back(msg); if (!write_in_progress) { boost::asio::async_write(socket_, boost::asio::buffer(write_msgs_.front().data(), write_msgs_.front().length()), boost::bind(&DisplayChatClient::handle_write, this, boost::asio::placeholders::error)); } } void DisplayChatClient::handle_write(const boost::system::error_code& error) { DLOG(INFO) << "DisplayChatClient::handle_write()"; if (!error) { write_msgs_.pop_front(); if (!write_msgs_.empty()) { boost::asio::async_write(socket_, boost::asio::buffer(write_msgs_.front().data(), write_msgs_.front().length()), boost::bind(&DisplayChatClient::handle_write, this, boost::asio::placeholders::error)); } } else { do_close(); } } Cheers -- Nicholas Yue Graphics - Arnold, Alembic, RenderMan, OpenGL, HDF5 Custom Dev - C++ porting, OSX, Linux, Windows http://au.linkedin.com/in/nicholasyue https://vimeo.com/channels/naiadtools

4 7

Boost Filesystem fails with FreeBSD 10, clang, and boost
by Ricky Huang 21 Jun '14

21 Jun '14

Hello all, I am currently migrating to a FreeBSD 10 system which comes default with clang language. I was able to compile Boost just fine. But when I include filesysstem.hpp to it, I get the following error message: > Linking CXX executable boost_clang_test > /usr/bin/ld: : invalid DSO for symbol `_ZN5boost6system15system_categoryEv' definition > /usr/local/lib/libboost_system.so.1.55.0: could not read symbols: Bad value > CC: error: linker command failed with exit code 1 (use -v to see invocation) > *** Error code 1 > > Stop. I am using cmake as my build system, could it be possible that I need to adjust my cmake variables? I am not sure if I've came to correct forum or should this be on FreeBSD, clang, CMake forum(s)? Please let me know if I am at the wrong place… The minimum amount of code to induce the problem are the following 2 files: CMakeLists.txt: cmake_minimum_required(VERSION 2.8) # Find and include Boost libraries find_package(Boost 1.55 COMPONENTS filesystem REQUIRED) include_directories(${Boost_INCLUDE_DIR}) set(LIBS ${LIBS} ${Boost_LIBRARIES}) set(BOOST_CLANG_TEST_SOURCES ${SOURCES} main.cpp) add_executable(boost_clang_test ${BOOST_CLANG_TEST_SOURCES}) target_link_libraries(boost_clang_test ${LIBS}) main.cpp: #include <stdio.h> #include <iostream> #include <sstream> #include <string> #include <boost/filesystem.hpp> using namespace std; using namespace boost::filesystem; const char *progname; int main(int argc, char **argv){ return 0; } Thanks in advance.

3 4

[graph] kamada_kawai_spring_layout warnings
by Michael Olea 21 Jun '14

21 Jun '14

Hi. I'm getting compiler warnings for subscripts out of range from kamada_kawai_spring_layout.hpp. I'm using boost_55_0, compiled with clang: Apple LLVM version 5.1 (clang-503.0.40) (based on LLVM 3.4svn) Target: x86_64-apple-darwin13.2.0 Thread model: posix ../../../../../include/boost/graph/kamada_kawai_spring_layout.hpp:110:49: warning: array index 2 is past the end of the array (which contains 2 elements) [-Warray-bounds] double denom = mat[0][0] * (mat[1][1] * mat[2][2] - mat[2][1] * mat[1][2]) The offending code is: template <> struct linear_solver<3> { template <typename Vec> static Vec solve(double mat[2][2], Vec rhs) { double denom = mat[0][0] * (mat[1][1] * mat[2][2] - mat[2][1] * mat[1][2]) - mat[1][0] * (mat[0][1] * mat[2][2] - mat[2][1] * mat[0][2]) + mat[2][0] * (mat[0][1] * mat[1][2] - mat[1][1] * mat[0][2]); double x_num = rhs[0] * (mat[1][1] * mat[2][2] - mat[2][1] * mat[1][2]) - rhs[1] * (mat[0][1] * mat[2][2] - mat[2][1] * mat[0][2]) + rhs[2] * (mat[0][1] * mat[1][2] - mat[1][1] * mat[0][2]); double y_num = mat[0][0] * (rhs[1] * mat[2][2] - rhs[2] * mat[1][2]) - mat[1][0] * (rhs[0] * mat[2][2] - rhs[2] * mat[0][2]) + mat[2][0] * (rhs[0] * mat[1][2] - rhs[1] * mat[0][2]); double z_num = mat[0][0] * (mat[1][1] * rhs[2] - mat[2][1] * rhs[1] ) - mat[1][0] * (mat[0][1] * rhs[2] - mat[2][1] * rhs[0] ) + mat[2][0] * (mat[0][1] * rhs[1] - mat[1][1] * rhs[0] ); Vec result; result[0] = x_num / denom; result[1] = y_num / denom; result[2] = z_num / denom; return result; } }; Looks like it should be: static Vec solve(double mat[3][3], Vec rhs) ... No?

1 0

stack unwinding with boost::fcontext
by David Frank 20 Jun '14

20 Jun '14

Context - 1.53.0 beta1 Context - 1.53.0 beta1 Context Struct fcontext_t and related functions Each instance of fcontext_t represents a context (CPU registers and stack space). View on www.boost.org Preview by Yahoo I'm wondering if there is any example showing how to do stack unwinding as described at the bottom of the above link as quoted below: " Stack unwinding Sometimes it is necessary to unwind the stack of an unfinished context to destroy local stack variables so they can release allocated resources (RAII pattern). The user is responsible for this task. " Thanks, Frank

2 1