- Boost-users - lists.boost.org

get local time in microsecondes :-)
by jellad tarek 30 Apr '12

30 Apr '12

hello i want to get the local time in microseconds (no the diff between 2 times)... like wireshark or commview. in this format 15:23:10,251485 is it possible with the booooost library ?????? 1000 thanks

1 0

filesystem: 'copy' is not a member of boost::filesystem
by Matan Nassau 30 Apr '12

30 Apr '12

Good afternoon, Calling boost::filesystem::copy(), I get the the compiler error 'copy' is not a member of 'boost::filesystem' When I look in boost/filesystem/v3/operations.hpp I see namespace filesystem { … using filesystem3::character_file; // using filesystem3::copy; using copy_file; … } Why is "using filesystem3::copy" line commented out? Matan

2 2

managed_shared_memory memory leak(?)
by Michael Herrmann 29 Apr '12

29 Apr '12

Hello everyone, the following trivial example highlights a memory leak according to MSVC 2010. Does anybody know why this is and how it can be avoided? // The following three directives are required for MSVC's automatic memory // leak detection. #define _CRTDBG_MAP_ALLOC #include <stdlib.h> #include <crtdbg.h> #include <boost/interprocess/managed_shared_memory.hpp> int main(int argc, char *argv[]) { { using namespace boost::interprocess; static const char* shMemIdentifier = "MySharedMemory"; struct ShMemCleaner { ShMemCleaner() { shared_memory_object::remove(shMemIdentifier); } ~ShMemCleaner() {shared_memory_object::remove(shMemIdentifier); } } cleaner; // Create a new segment with given name and size managed_shared_memory segment(create_only, shMemIdentifier, 1024); int* intInShMem = segment.construct<int>("myInt")(2); segment.destroy<int>("myInt"); } _CrtDumpMemoryLeaks(); } Thank you very much! Best, Michael

2 4

C++ Now! Conference Program Highlights C++11
by Jon Kalb 29 Apr '12

29 Apr '12

C++ Now! (formerly BoostCon) is pleased to announce its 2012 program with 35+ inspiring C++ practitioners delivering more than fifty technical sessions. In honor of the release of the new C++11 standard, this May's conference will, for the first time, be offered in three tracks. In addition to the sessions that attendees have come to expecton topics like library design and usage, programming techniques, best practices, academic research, development tools, concurrency, reliability, and performancethis year's program includes a full track devoted to C++11 <http://cppnow.org/locations/c11/> and three keynotes by industry luminaries <http://cppnow.org/overview/> . For those eager to get on board with the new standard, the C++11 content features fifteen hours of tutorial material covering the most important new features and APIs, presented, in many cases, by the language designers themselves. C++ Now! is offering the most complete C++11 tutorial coverage of any conference this year! Conference speakers include book and library authors, academics, C++ Standard Committee members, tool builders, architects, and engineers. With our very high presenter-to-audience ratio, attendees will have ample opportunity for one-on-one interaction with leaders who are currently defining the state of the art in C++. Dave Abrahams, the conference co-chair, writes, "We planned for an expansion, but even I am surprised at the presenter response and the resulting depth of this year's program. I'm preparing for a flood of new attendees." Reserve your place today at http://cppnow.org/registration C++ Now! 2012, held May 13-18 in Aspen Colorado is hosted by Boost in cooperation with ACM. * Complete program: http://cppnow.org/schedule * Speakers: http://cppnow.org/participants * Registration: http://cppnow.org/registration Jon

4 5

date_time, g++-4.7.0, compile error
by List User 29 Apr '12

29 Apr '12

The following code gives compile error with g++-4.7.0 but compiles fine with g++-4.6. #include <iostream> #include <boost/date_time/local_time/local_time.hpp> using namespace std; int main(){ boost::posix_time::ptime time_t_epoch(boost::gregorian::date(1970,1,1)); cout << time_t_epoch << endl; return 0; } The following is the error message that is repeatedly seen (compiler outputs a lot of messages) /usr/include/boost/date_time/local_time/local_date_time.hpp:433:84: error: use of deleted function boost::shared_ptr<boost::date_time::time_zone_base<boost::posix_time::ptime, char> >::shared_ptr(const boost::shared_ptr<boost::date_time::time_zone_base<boost::posix_time::ptime, char> >&) I am using Ubuntu 12.04 and libboost-date-time1.46.1. Any suggestions? thanks suresh

2 2

[wserialization] serializing to a stringstream
by Sean Farrow 29 Apr '12

29 Apr '12

Hi: I'm using xml serialization and need to serialize to a string stream for encryption purposes. As I am using xml_woarchive, should I use wstringstream or just the normal stringstream? Does the wide version even exist? Essentially does the boost serialization library convert to narrow characters before serializing or not? Any help appreciated. Regards Sean.

2 1

How to send serialized data via boost::interprocess::message_queue
by Jens Saathoff 28 Apr '12

28 Apr '12

Hi! I'm working with message_queue and want to send a structure to receiver-app. How to serialize i correctly and how to receive it? Here's some sending code: Data data; > data.counter = 9; > data.money = 5.4; > //data.name = "Guten Tag"; > > std::stringstream os; // = new std::stringstream; > boost::archive::text_oarchive oa(os); > oa << data; > > ipc::message_queue::remove("mq_main"); > ipc::message_queue mq(ipc::create_only, "mq_main", 1, > sizeof(std::stringstream)); > mq.send(&os, sizeof(os), 0); I implemented the serializing code in the structure "Data" Add here's my code to receive: Data data; > std::stringstream is; // = new std::stringstream; > try > { > unsigned int priority; ///< The priority > ipc::message_queue::size_type recvd_size; > ipc::message_queue mq(ipc::open_only, "mq_main"); > > if(mq.try_receive(&is, sizeof(std::stringstream), recvd_size, > priority)) > { > boost::archive::text_iarchive ai(is); // CRASH > ai >> data; > } > //mq.receive(&is, sizeof(is), recvd_size, priority); > //mq.do_receive(ipc::message_queue_t::non_blocking, &is, > sizeof(is), recvd_size, priority); > > //boost::archive::text_iarchive * ai = new > boost::archive::text_iarchive(is); > > //*ai >> data; > > //data << ai; > //mq_recv->receive(&data, sizeof(data), recvd_size, priority); > > ipc::message_queue::remove("mq_main"); > //is.~basic_stringstream(); > } > catch(ipc::interprocess_exception &ex) > { > ipc::message_queue::remove("mq_main"); > std::cout << ex.what() << std::endl; > return; > } > The receiver-app crashes at boost::archive::text_iarchive ai(is). The error is: 0xC0000005: Access violation reading location 0x00f56a34. I really don't have a clue...pls help. Thank you very much :-)

1 0

serialize derived class object through boost::serialization
by breadbread1984 28 Apr '12

28 Apr '12

I want to serialize a derived class object through boost::serialization library. To test whether both the base and the derived class object have been serialized properly, I print message to the console when the serialize function is called. When the following code is compiled and runned, the message of serialize function for the base class object is not shown. Thus, the base class object is not serialized properly. Why the serialization is not done on the base class object? #include <cstdlib> #include <iostream> #include <fstream> #include <boost/serialization/version.hpp> #include <boost/serialization/export.hpp> #include <boost/archive/text_iarchive.hpp> #include <boost/archive/text_oarchive.hpp> #include <boost/shared_ptr.hpp> using namespace std; using namespace boost::archive; using boost::shared_ptr; class Base { friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int version); protected: int a; public: Base():a(0){} virtual ~Base(){} int geta() const {return a;} void seta(int aa) {a = aa;} }; template<class Archive> void Base::serialize(Archive & ar,const unsigned int version) { cout<<"serializing base class object"<<endl; ar & a; } class Derived : public Base { friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int version); protected: int b; public: Derived():Base(),b(0){} virtual ~Derived(){} int getb() const {return b;} void setb(int bb) {b = bb;} }; template<class Archive> void Derived::serialize(Archive & ar,const unsigned int version) { boost::serialization::base_object<Base>(*this); boost::serialization::void_cast_register<Derived,Base> ( static_cast<Derived*>(NULL), static_cast<Base*>(NULL) ); cout<<"serializing derived class object"<<endl; ar & b; } BOOST_CLASS_EXPORT_GUID(Derived,"Derived"); int main(int argc,char ** argv) { shared_ptr<Base> ptr(new Derived()); ptr->seta(4); Base * p = ptr.get(); Derived * pp = dynamic_cast<Derived*>(p); assert(pp); pp->setb(4); ofstream out("test.dat"); text_oarchive oa(out); oa << p; return EXIT_SUCCESS; }

2 1

undefined symbol: PyUnicodeUCS4_FromEncodedObject
by Dylan Dandelion 28 Apr '12

28 Apr '12

Is there a way to specify boost.python to be built with UCS2 instead of USC4? I am trying to build some libraries and ran into the following error: ImportError: /home/user/boost_1_49_0/stage/lib/libboost_python.so.1.49.0: undefined symbol: PyUnicodeUCS4_FromEncodedObject I am using a version of Python that seems to use only UCS2. # python Python 2.7.2 (default, Aug 24 2011, 22:13:27) [GCC 4.2.4 (Ubuntu 4.2.4-1ubuntu4)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> print sys.maxunicode 65535 >From what I searched online so far, there are some suggestions to recompile Python with some flags to use UCS4, but that is not possible for me. Thanks!

1 0

Do boost run well on x64 platform with such warning?
by clive 27 Apr '12

27 Apr '12

Hi,my friends I have a stupid question Now i build boost 1.49 on x64 platform with vc2005 I find such many warnings: warning C4267: '=' : conversion from 'size_t' to 'unsigned int', possible loss of data or conversion from '_int64' to 'unsigned int', possible loss of data I want to make sure that these warnings really do lose data whether or not on x64 flatform. Put another way, could these warning be neglected or should i change the source code? Thanks

2 1