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

Herb Sutter on C++ Standardization and Visual Studio
by LeMay.Steve 30 Jun '13

30 Jun '13

Herb Sutter on C++ Standardization at Microsoft. http://channel9.msdn.com/Events/Build/2013/2-306 SGL

3 2

future<>.then and promises
by Tobias Furuholm 30 Jun '13

30 Jun '13

I am trying out future<>.then and I am seeing some results that confuses me. I have tried to illustrate this with a few examples. The first example is using a promise together with future<>.then. It generates no output: boost::promise<int> promise; boost::future<int> fut = promise.get_future(); promise.set_value(123); fut.then([](boost::future<int>& f) { std::cout << "The value is: " << f.get() << std::endl; return f.get(); }); boost::chrono::milliseconds duration(1000); boost::this_thread::sleep_for(duration); Why is fut.then not triggered? (assigning fut.then to another future makes no difference) By adding a launch policy I get the output "The value is: 123" which is the output I would expect from all my examples: boost::promise<int> promise; boost::future<int> fut = promise.get_future(); promise.set_value(123); fut.then(boost::launch::async, [](boost::future<int>& f) { std::cout << "The value is: " << f.get() << std::endl; return f.get(); }); boost::chrono::milliseconds duration(1000); boost::this_thread::sleep_for(duration); To make this more real, let's move promise.set_value to after .then boost::promise<int> promise; boost::future<int> fut = promise.get_future(); fut.then(boost::launch::async, [](boost::future<int>& f) { std::cout << "The value is: " << f.get() << std::endl; return f.get(); }); promise.set_value(123); boost::chrono::milliseconds duration(1000); boost::this_thread::sleep_for(duration); This program outputs nothing and never terminates. But when I assign the result of fut.then to another future I get the expected output once again: boost::promise<int> promise; boost::future<int> fut = promise.get_future(); boost::future<int> fut2 = fut.then(boost::launch::async, [](boost::future<int>& f) { std::cout << "The value is: " << f.get() << std::endl; return f.get(); }); promise.set_value(123); boost::chrono::milliseconds duration(1000); boost::this_thread::sleep_for(duration); Finally, as I bonus I add an example where I use async to generate a future instead. boost::future<int> fut = boost::async([]() { return 123; }); fut.then([](boost::future<int>& f) { std::cout << "The value is: " << f.get() << std::endl; return f.get(); }); boost::chrono::milliseconds duration(1000); boost::this_thread::sleep_for(duration); This generates the output "The value is: " (without 123). Once again, by assigning the result of fut.then to another future I get the expected output. I use boost 1.54 beta 1 with clang 3.2 on Linux and. /Tobias

3 7

Re: [Boost-users] Accessing memory in shared segments
by Andy Falanga (afalanga) 28 Jun '13

28 Jun '13

>From: Andy Falanga (afalanga) >Sent: Thursday, June 27, 2013 7:42 AM >To: 'boost-users(a)lists.boost.org' >Subject: Accessing memory in shared segments > >Hi, > >I have some code which shares data with shared memory. To that end, I'm using >boost::interprocess:managed_shared_memory. Without respect to scope and functions, what I have is >roughly: > >boost::interprocess::managed_shared_memory sharedMem(boost::interprocess::create_only, > "SharedMemory", 4096); > >//later on >u_int8_t* dataSegment = sharedMemory.construct<u_int8_t>("data")[5](0); >char* string1 = sharedMemory.construct<char>("String 1")[50]('\0'); >// other stuff > >// placing stuff in the data segment >for(int i(0); i < 5; i++) dataSegment[i] = anEarlierArray[i]; > > >// then, in other process read the data Segment >char ary[5]; >for(int i(0); i< 5; i++) ary[i] = dataSegment.first[i]; > > >For whatever reason I couldn't simply access through dataSegment[n] notation. The weirdest thing is, >the data is being read back to me in the reverse order that it should be. For example, if >[0x2,0x4,0x7,0x1] is written I read it back as [0x1,0x7,0x4,x02] even though I'm writing and reading >in the same order. Why is this? What is it I'm missing about using shared memory? Problem solved: it was between the keyboard and the chair. Further debugging showed that the data wasn't being written in reverse (it made no sense that it would have been) but rather was a result of some HID libraries I'm using under the hood. Posting this in case someone hits on this message while looking through the archives. Andy

1 0

[beta] 1.54 for ARM
by Michael Powell 28 Jun '13

28 Jun '13

Hello, I haven't actually built 1.54 for ARM yet, although I have successfully built and am using 1.53 for ARM today. Is it that much different from 1.53? And/or has someone already built it for ARM to give a little beta feedback? If I can manufacture some time this weekend I may give that a go regardless. Thank you... Regards, Michael Powell

1 0

Re: [Boost-users] [asio] How to deal with no-connect and/or read-timeout
by Marat Abrarov 28 Jun '13

28 Jun '13

> If the timer handler is called first, then you're done: initiate > disconnection, etc. > If the read handler is called first, you simply reset the timer (maybe > cancel and then reset). > I honestly don't know if you have to worry about a race condition (timer > going off while handler for async_read is executing), or if a cancel / > reschedule out of the async_read handler would preempt any other handlers. > You might end up having to stick both the async_read and deadline_timer in > the same strand; that would prohibit concurrent execution. There is a good example: http://www.boost.org/doc/libs/1_53_0/doc/html/boost_asio/example/timeouts/se rver.cpp and a good article: http://blog.think-async.com/2010/04/timeouts-by-analogy.html and a rather heavy example: http://sourceforge.net/projects/asio-samples/ (see project named echo_server). In general, you will need a state machine (or even few of them). Regards, Marat Abrarov.

6 18

Re: [Boost-users] Mutex synchronised wrapper class for boost::interprocess vector of strings
by Riskybiz 28 Jun '13

28 Jun '13

"It's not an easy task. You should catch the exception and then notify all connected processes that should disconnected from the segmenet (as only offline growing is supported). After that a process can call "grow" to try extend the segment. Then, all processes can attach to the newly grown segment. Think of that as a complex binary file that must be extended and internal structures changed. All users should close the file, the file should be changed by a process and then all users can start using the file again." OK Ion, I see. 1. Can I ask what mechanism you would suggest for notifying the other processes to disconnect before the grow() operation. 2. My wrapper class implementation is still in the experimental stages, I'm trying to build it up to operate in the way I need. I've hacked it around a bit to account for the fact that I cannot control the order in which the client & server instances will ultimately be launched by the 3rd party application I'm building a DLL for; so I've got to make the wrapper class as flexible as possible. What I'm trying to do is get my toy client process to wait, if it should happen to launch first, before the server, and then have the clients notified by the server process when data is ready to be accessed. So....I can get the client to wait using a named_condition, but then I can't get it to wake up. The notifyall() is not taking effect. P.S. In my tests I first launch the client and then the server process. Have I missed something fundamental here, is my notifyall() properly constructed and directed to the right destination? 3. Also, another thought; if the shared memory segment should happen to grow whilst a client is waiting then the client will need to remap the segment on waking, correct? But will it even get the notifyall() signal, because the client is still 'looking' at a different memory location? Could this be my problem? Not sure. Though I did test the code without the grow() commands and the client process still did not wake! Many, many thanks for your help so far, just a few more hurdles to clear and this wrapper class will be operational. Riskybiz. #ifndef SHARED_MEMORY_WRAPPER_H//if not defined already #define SHARED_MEMORY_WRAPPER_H//then define it #include <boost/interprocess/managed_shared_memory.hpp> #include <boost/interprocess/containers/vector.hpp> #include <boost/interprocess/containers/string.hpp> #include <boost/interprocess/allocators/allocator.hpp> #include <boost/interprocess/sync/named_mutex.hpp> #include <boost/interprocess/sync/named_condition.hpp> #include <iostream> #include <stdexcept> using namespace boost::interprocess; class SharedMemoryWrapper { public: SharedMemoryWrapper(const std::string &name, bool server) : m_name(name), m_server(server) { try { //Open the shared segment. Will throw an interprocess exception if fails to open i.e. segment does not exist. Control jumps to the catch block. m_segment = new managed_shared_memory(open_only, m_name.c_str()); //Find the vector using the c-string name and open it sharedSegmentVector = m_segment->find<MyShmStringVector>("sharedSegmentVector").first; //Open the underlying mutex m_mutex = new named_mutex(open_only, "smw_mutex"); //Open the underlying condition variable waitForData = new named_condition(open_only, "smw_named_condition"); if(m_server)//Flag to put client processes to sleep until ready for them { sleep = false; } else { sleep = true; } } catch(interprocess_exception &ipe)//Catch the interprocess exception and instantiate the shared memory resources here. { try { std::cout << "Error: interprocess_exception: " << ipe.what() << "Going to instantiate shared memory resources now...." << std::endl; //Clean up resources from any prior instances named_mutex::remove("smw_mutex"); named_condition::remove("smw_named_condition"); shared_memory_object::remove(m_name.c_str()); //Create shared memory m_segment = new managed_shared_memory(create_only, m_name.c_str(), 100000); //Create allocators CharAllocator charallocator(m_segment->get_segment_manager()); StringAllocator stringallocator(m_segment->get_segment_manager()); //This vector is fully constructed in shared memory. All pointers //buffers are constructed in the same shared memory segment //This vector can be safely accessed from other processes. sharedSegmentVector = m_segment->construct<MyShmStringVector>("sharedSegmentVector")(stringallocat or); if(m_server)//Flag to put client processes to sleep until ready for them { sleep = false; } else { sleep = true; } //Instantiate the underlying mutex m_mutex = new named_mutex(create_only, "smw_mutex"); //Instantiate the underlying condition variable waitForData = new named_condition(create_only, "smw_named_condition"); //......despite the exception code continues executing to the end of the constructor. } catch(interprocess_exception &ipe1) { std::cout << "Error: Whilst instantiating shared memory resources: interprocess_exception: " << ipe1.what() << std::endl; } } catch(...) { std::cout << "Error: Unknown Exception: " << std::endl; } } ~SharedMemoryWrapper() { /* //Destructor: Will remove the shared memory resources if (m_server) { named_mutex::remove("named_mutex"); //Destroy the vector from the managed_shared_memory //m_segment->destroy_ptr(sharedSegmentVector);//This will free all strings that the vector contains m_segment->destroy<MyShmStringVector>("sharedSegmentVector");//Destroy the vector //Is it necessary to destroy the allocators here? //Remove the managed_shared_memory; this may fail if the memory does not exist or is mapped or opened by another process shared_memory_object::remove(m_name.c_str()); } */ //Delete instance members delete m_mutex; delete m_segment; delete waitForData; } //Writer void write(const std::string &inStr) { try { CharAllocator charallocator(m_segment->get_segment_manager()); scoped_lock<named_mutex> lock(*m_mutex); try { if(sleep)//Put client process to sleep when it first tries to access. { std::cout << "Going to wait...." << std::endl; sleep = false; waitForData->wait(lock);//Set condition variable to wait. When ready to allow access then call notify(). } } catch(interprocess_exception &ex) { std::cout << "Error in Writer Process Wait: interprocess_exception: "<< ex.what() << std::endl; } MyShmString shmStr(inStr.c_str(), charallocator); sharedSegmentVector->push_back(shmStr); //Try to grow if free memory is running low if(m_segment->get_free_memory() < 50000) { std::cout << "Free Memory Before: " << m_segment->get_free_memory() << " Elements: " << getSize() << std::endl; delete m_mutex;//delete delete waitForData;//delete delete m_segment;//unmap managed_shared_memory::grow(m_name.c_str(), 50000);//grow m_segment = new managed_shared_memory(open_only, m_name.c_str());//remap sharedSegmentVector = m_segment->find<MyShmStringVector>("sharedSegmentVector").first;//find //Reopen the underlying mutex m_mutex = new named_mutex(open_only, "smw_mutex"); //Reopen the underlying condition variable waitForData = new named_condition(open_only, "smw_named_condition"); std::cout << "Free Memory After Grow: " << m_segment->get_free_memory() << " Elements: " << getSize() << std::endl; } } catch(interprocess_exception ipe) { std::cout << "Error in SharedMemoryWrapper::write(): interprocess_exception: "<< ipe.what() << std::endl; } catch(...) { std::cout << "Error in SharedMemoryWrapper::write(): unknown error" << std::endl; } } //Reader std::string read(size_t &index) { try { scoped_lock<named_mutex> lock(*m_mutex); try { if(sleep)//Put client process to sleep when it first tries to access. { std::cout << "Going to wait...." << std::endl; sleep = false; waitForData->wait(lock);//Set condition variable to wait. When ready to allow access then call notify(). } } catch(interprocess_exception &ex) { std::cout << "Error in Reader Process Wait: interprocess_exception: "<< ex.what() << std::endl; } const MyShmString &shmStr = (*sharedSegmentVector)[index]; std::string stdStr(shmStr.begin(), shmStr.end()); return stdStr; } catch(interprocess_exception &ipe) { std::cout << "Error in SharedMemoryWrapper::read(): interprocess_exception: "<< ipe.what() << std::endl; } catch(std::range_error &re) { std::cout << "Error in SharedMemoryWrapper::read(): range_error: " << re.what() << std::endl; } catch(...) { std::cout << "Error in SharedMemoryWrapper::read(): unknown error "<< std::endl; } return "Error in SharedMemoryWrapper::read()"; } //Notifier void notify() { try { scoped_lock<named_mutex> lock(*m_mutex); std::cout << "Going to Notify...." << std::endl; lock.unlock(); waitForData->notify_all();//notify to release the wait condition; when data is available and ready to be accessed by client processes std::cout << "Notified" << std::endl; } catch(interprocess_exception &ipe) { std::cout << "Error: boost_interprocess exception: in notifier: " << ipe.what() << std::endl; } catch(...) { std::cout << "Unknown Error In Notifier: " << std::endl; } } //Vector Size size_t getSize() const { return this->sharedSegmentVector->size(); } //Remover void release() { try { std::cout << "Going to release shared memory resources...." << std::endl; named_mutex::remove("named_mutex"); named_condition::remove("smw_named_condition"); //Destroy the vector from the managed_shared_memory //m_segment->destroy_ptr(sharedSegmentVector);//This will free all strings that the vector contains m_segment->destroy<MyShmStringVector>("sharedSegmentVector");//Destroy the vector //Is it necessary to destroy the allocators here? //Remove the managed_shared_memory; this may fail if the memory does not exist or is mapped or opened by another process shared_memory_object::remove(m_name.c_str()); std::cout << "Resources Released" << std::endl; } catch(interprocess_exception ipe2) { std::cout << "Error: remove() interprocess_exception: " << ipe2.what() << std::endl; } } private: //Typedefs typedef boost::interprocess::allocator<char, managed_shared_memory::segment_manager> CharAllocator; typedef boost::interprocess::basic_string<char, std::char_traits<char>, CharAllocator> MyShmString; typedef boost::interprocess::allocator<MyShmString, managed_shared_memory::segment_manager> StringAllocator; typedef boost::interprocess::vector<MyShmString, StringAllocator> MyShmStringVector; bool m_server; std::string m_name; bool sleep; managed_shared_memory *m_segment; MyShmStringVector *sharedSegmentVector; named_mutex *m_mutex; named_condition *waitForData; };//class #endif//header guard Server program to prepare the shared vector of strings: // PrepareSharedMemoryVectorOfStrings.cpp : Defines the entry point for the console application. // #include "SharedMemoryWrapper.h" #include <iostream> #include <string> #include <sstream> int main(int argc, char *argv[]) { SharedMemoryWrapper *smw = new SharedMemoryWrapper("SMT", true); size_t cnt(0); while(cnt < 100) { //Convert number to string representation std::string cntStr = static_cast<std::ostringstream*>( &(std::ostringstream() << cnt) )->str(); //Write to shared memory vector smw->write(cntStr); cnt++; } size_t vecSize = smw->getSize(); std::cout << "Elements Present: "<< vecSize << std::endl; smw->notify(); //smw->release(); delete smw; return 0; } Client program to access the shared memory vector of strings: // AccessSharedMemoryVectorOfStrings.cpp : Defines the entry point for the console application. // #include "SharedMemoryWrapper.h" #include <iostream> #include <string> int main(int argc, char *argv[]) { SharedMemoryWrapper *smw = new SharedMemoryWrapper("SMT", false); try { std::string outStr("Blank"); //if(smw->getSize() == 100) //{ outStr = ""; for(size_t index = 0; index < 100; index++) { outStr += (smw->read(index) + " "); } //} std::cout << outStr << std::endl; } catch(...) { std::cout << "Error: Unknown Exception." << std::endl; } smw->release();//removes shared memory resources from the system delete smw; return 0; }

1 0

global instances for managed_shared_memory & message_queue
by bb.andersen 27 Jun '13

27 Jun '13

Dear Boost Grurus, First of all let me thank you for the huge effort that people like Mr. Gaztañaga has made to keep boost interprocess improved. It is a really time-saver API! I have a very basic question that, despite the large amount of documentation I've looked, I haven't clarified yet. I just want to create a global static variables (i.e. instances) for managed_shared_memory, message_queue, mutex and condition var. By now I have my app prototype (CGI) is running fine with auto vars, as appeared in the several examples: /main() { ... boost::interprocess::permissions perm; perm.set_unrestricted(); managed_shared_memory segment(create_only,"MonitorOEE_SharedMemory", 65536, 0, perm); ... message_queue mq(create_only, "MonitorOEE_MessageQueue", 256, sizeof(t_QRequest), perm); ... named_mutex mutex_waiting(create_only, namedMutex, perm); ... named_condition cdv_wakeup(create_only, namedConditionVar, perm); ... }/ All segment, mq, cdv_wakeup live in the context of the main function... Now I want them to be globally accessible from different functions. But I am not able to. I just partially succeeded creating global pointers to managed_shared_memory and message_queue. But when constructing object to the pointer segmentation faults appear... ///Global Declarations ... static boost::interprocess::message_queue *mq; static boost::interprocess::managed_shared_memory *segment; static boost::interprocess::interprocess_mutex mutex_waiting; static boost::interprocess::interprocess_condition cdv_wakeup; ... main() { .. std::auto_ptr<boost::interprocess::managed_shared_memory>ptr01(new boost::interprocess::managed_shared_memory(open_only,"MonitorOEE_SharedMemory")); segment = ptr01.get(); //this seems to work but fails when constructing objects: IPC_SOAPRequest *pSOAPRequest =segment->construct<IPC_SOAPRequest>(namedSOAPRequest)(); (the autovar counterpart works seamlessly) ... std::auto_ptr<boost::interprocess::message_queue>ptr02(new boost::interprocess::message_queue(open_only,MonitorOEE_MessageQueue")); mq = ptr02.get(); //Seems to work...(send and receive) .. //dunno how to instantiate to mutex and cond var global references } / I am sure it should be an easier and tidier way. Can you give me just the first steps to work this out? I've been sleepless a couple of nights. Eskerrik Asko! (Thanks in the basque language!) -- View this message in context: http://boost.2283326.n4.nabble.com/global-instances-for-managed-shared-memo… Sent from the Boost - Users mailing list archive at Nabble.com.

2 1

Re: [Boost-users] Mutex synchronised wrapper class for boost::interprocess
by Riskybiz 27 Jun '13

27 Jun '13

Ion; thank you!! I found the errors in my prior code thanks to your tip and used the improvements you suggested. I had unwittingly declared variables with very similar names and different types, leading to confused behavior. Anyway that is solved and I now have a working implementation of a mutex synchronised interprocess vector of strings. Have included it below in case it's of use to anyone else trying the same... A further question if I may? What is the best approach to extend a managed_shared_memory_segment? I can dynamically add (via write() function) shared vector elements until such time as an interprocess_exception boost_interprocess::bad_alloc is thrown; when the memory allocated to the shared segment is filled. Is there a way to handle this exception so that the segment can be extended with more memory and then resume adding data elements to the vector? Or perhaps some other way to detect the segment memory is running short and take action to extend it? Thanks again, Riskybiz. Code: Class Definition: #ifndef SHARED_MEMORY_WRAPPER_H//if not defined already #define SHARED_MEMORY_WRAPPER_H//then define it #include <boost/interprocess/managed_shared_memory.hpp> #include <boost/interprocess/containers/vector.hpp> #include <boost/interprocess/containers/string.hpp> #include <boost/interprocess/allocators/allocator.hpp> #include <boost/interprocess/sync/named_mutex.hpp> #include <iostream> #include <stdexcept> using namespace boost::interprocess; class SharedMemoryWrapper { public: SharedMemoryWrapper(const std::string &name, bool server) : m_name(name), m_server(server) { if (server) { //Clean up resources from any prior instances named_mutex::remove("named_mutex"); shared_memory_object::remove(m_name.c_str()); //Create shared memory m_segment = new managed_shared_memory(create_only, m_name.c_str(), 1000000); //Create allocators CharAllocator charallocator(m_segment->get_segment_manager()); StringAllocator stringallocator(m_segment->get_segment_manager()); //This vector is fully constructed in shared memory. All pointers //buffers are constructed in the same shared memory segment //This vector can be safely accessed from other processes. sharedSegmentVector = m_segment->construct<MyShmStringVector>("sharedSegmentVector")(stringallocat or); } else { try { //Open the shared segment m_segment = new managed_shared_memory(open_only, name.c_str()); //Find the vector using the c-string name and open it sharedSegmentVector = m_segment->find<MyShmStringVector>("sharedSegmentVector").first; } catch(interprocess_exception ipe) { std::cout << "Error: Interprocess Exception: " << ipe.what() << std::endl; } catch(...) { std::cout << "Error: Unknown Exception: " << std::endl; } } m_mutex = new named_mutex(open_or_create, "named_mutex"); } ~SharedMemoryWrapper() { /* //Destructor: Will remove the shared memory resources if (m_server) { named_mutex::remove("named_mutex"); //Destroy the vector from the managed_shared_memory //m_segment->destroy_ptr(sharedSegmentVector);//This will free all strings that the vector contains m_segment->destroy<MyShmStringVector>("sharedSegmentVector");//Destroy the vector //Is it necessary to destroy the allocators here? //Remove the managed_shared_memory; this may fail if the memory does not exist or is mapped or opened by another process shared_memory_object::remove(m_name.c_str()); } */ //Delete instance members delete m_mutex; delete m_segment; } //Writer void write(const std::string &inStr) { try { CharAllocator charallocator(m_segment->get_segment_manager()); scoped_lock<named_mutex> lock(*m_mutex); MyShmString shmStr(inStr.c_str(), charallocator); sharedSegmentVector->push_back(shmStr); } catch(interprocess_exception ipe) { std::cout << "Error in SharedMemoryWrapper::write(): interprocess_exception: "<< ipe.what() << std::endl; } catch(...) { std::cout << "Error in SharedMemoryWrapper::write(): unknown error" << std::endl; } } //Reader std::string read(size_t &index) { try { scoped_lock<named_mutex> lock(*m_mutex); const MyShmString &shmStr = (*sharedSegmentVector)[index]; std::string stdStr(shmStr.begin(), shmStr.end()); return stdStr; } catch(interprocess_exception ipe) { std::cout << "Error in SharedMemoryWrapper::read(): interprocess_exception: "<< ipe.what() << std::endl; } catch(std::range_error re) { std::cout << "Error in SharedMemoryWrapper::read(): range_error: " << re.what() << std::endl; } catch(...) { std::cout << "Error in SharedMemoryWrapper::read(): unknown error "<< std::endl; } return "Error in SharedMemoryWrapper::read()"; } //Vector Size size_t getSize() const { return this->sharedSegmentVector->size(); } private: //Typedefs typedef boost::interprocess::allocator<char, managed_shared_memory::segment_manager> CharAllocator; typedef boost::interprocess::basic_string<char, std::char_traits<char>, CharAllocator> MyShmString; typedef boost::interprocess::allocator<MyShmString, managed_shared_memory::segment_manager> StringAllocator; typedef boost::interprocess::vector<MyShmString, StringAllocator> MyShmStringVector; bool m_server; std::string m_name; managed_shared_memory *m_segment; MyShmStringVector *sharedSegmentVector; named_mutex *m_mutex; };//class #endif//header guard Test Programmes: // PrepareSharedMemoryVectorOfStrings.cpp : Defines the entry point for the console application. // #include "SharedMemoryWrapper.h" #include <iostream> #include <string> #include <sstream> int main(int argc, char *argv[]) { SharedMemoryWrapper *smw = new SharedMemoryWrapper("SharedMemoryTest", true); size_t cnt(0); while(cnt < 100) { //Convert number to string representation std::string cntStr = static_cast<std::ostringstream*>( &(std::ostringstream() << cnt) )->str(); //Write to shared memory vector smw->write("Iteration: " + cntStr); cnt++; } size_t vecSize = smw->getSize(); std::cout << "Elements Present: "<< vecSize << std::endl; delete smw; return 0; } // AccessSharedMemoryVectorOfStrings.cpp : Defines the entry point for the console application. // #include "SharedMemoryWrapper.h" #include <iostream> #include <string> int main(int argc, char *argv[]) { SharedMemoryWrapper *smw = new SharedMemoryWrapper("SharedMemoryTest", false); std::string outStr; for(size_t index = 0; index < 100; index++) { outStr = smw->read(index); std::cout << outStr << std::endl; } delete smw; return 0; }

2 1

[1.54.0] Release candidates available
by Marshall Clow 27 Jun '13

27 Jun '13

Release candidate files for 1.54.0 are available at http://boost.cowic.de/rc/ As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. This helps ensure the candidates build OK before we push them out to SourceForge. The files (and associated md5s) are: efbfbff5a85a9330951f243d0a46e4b9 *boost_1_54_0_rc1.tar.gz 15cb8c0803064faef0c4ddf5bc5ca279 *boost_1_54_0_rc1.tar.bz2 78a35834c45220a6164310e280abe675 *boost_1_54_0_rc1.zip 89e734ffd2afe0982b2d9fc21d033dba *boost_1_54_0_rc1.7z Thanks! -- The release managers

2 1

ASIO: Problem with building boost 1.53 ASIO examples under cygwin
by mschulze＠ivs.cs.ovgu.de 27 Jun '13

27 Jun '13

Hi all, I tried building boost 1.53 ASIO examples under cygwin and it didn't worked with bjam or b2 respectively. Then I used "bjam -n" to get the invoked commands in order to further track down the issue. I end up with the following command to compile an example "g++" -ftemplate-depth-128 -O0 -fno-inline -Wall -g -mthreads -DBOOST_ALL_NO_LIB=1 -DBOOST_CHRONO_DYN_LINK=1 -DBOOST_SYSTEM_DYN_LINK=1 -DBOOST_SYSTEM_NO_DEPRECATED -DBOOST_THREAD_BUILD_DLL=1 -DBOOST_THREAD_POSIX -DBOOST_THREAD_USE_DLL=1 -I"../../../.." -o "blocking_udp_echo_server" "blocking_udp_echo_server.cpp" -D__USE_W32_SOCKETS -D_WIN32_WINNT=0x0501 ../../../../bin.v2/libs/thread/build/gcc-4.5.3/release/link-static/threading-multi/libboost_thread.a ../../../../bin.v2/libs/system/build/gcc-4.5.3/release/link-static/threading-multi/libboost_system.a -lws2_32 -lmswsock and I got the following errors: In file included from ../../../../boost/asio/detail/impl/posix_tss_ptr.ipp:24:0, from ../../../../boost/asio/detail/posix_tss_ptr.hpp:77, from ../../../../boost/asio/detail/tss_ptr.hpp:27, from ../../../../boost/asio/detail/call_stack.hpp:20, from ../../../../boost/asio/impl/handler_alloc_hook.ipp:19, from ../../../../boost/asio/handler_alloc_hook.hpp:80, from ../../../../boost/asio/detail/handler_alloc_helpers.hpp:22, from ../../../../boost/asio/detail/bind_handler.hpp:19, from ../../../../boost/asio/detail/wrapped_handler.hpp:18, from ../../../../boost/asio/io_service.hpp:24, from ../../../../boost/asio/basic_io_object.hpp:19, from ../../../../boost/asio/basic_socket.hpp:19, from ../../../../boost/asio/basic_datagram_socket.hpp:20, from ../../../../boost/asio.hpp:20, from blocking_udp_echo_server.cpp:13: ../../../../boost/asio/error.hpp:77:17: error: a function call cannot appear in a constant-expression ../../../../boost/asio/error.hpp:130:15: error: a function call cannot appear in a constant-expression ../../../../boost/asio/error.hpp:135:19: error: a function call cannot appear in a constant-expression ../../../../boost/asio/error.hpp:149:23: error: a function call cannot appear in a constant-expression ../../../../boost/asio/error.hpp:163:15: error: a function call cannot appear in a constant-expression ../../../../boost/asio/error.hpp:244:45: warning: boost::asio::error::system_category defined but not used ../../../../boost/asio/error.hpp:246:45: warning: boost::asio::error::netdb_category defined but not used ../../../../boost/asio/error.hpp:248:45: warning: boost::asio::error::addrinfo_category defined but not used ../../../../boost/asio/error.hpp:250:45: warning: boost::asio::error::misc_category defined but not used ../../../../boost/asio/detail/winsock_init.hpp:78:30: warning: boost::asio::detail::winsock_init_instance defined but not used The error messages boils down to the use of "__MSABI_LONG(x)" within an enumeration definition. __MSABI_LONG is a macro that has to be resolved during the cpp run but isn't but it seems not to be known at this point. I also tested the boost version 1.52 and there are none of these issues and it worked like it is intended. Best regards, Michael

2 4

Accessing memory in shared segments
by Andy Falanga (afalanga) 27 Jun '13

27 Jun '13

Hi, I have some code which shares data with shared memory. To that end, I'm using boost::interprocess:managed_shared_memory. Without respect to scope and functions, what I have is roughly: boost::interprocess::managed_shared_memory sharedMem(boost::interprocess::create_only, "SharedMemory", 4096); //later on u_int8_t* dataSegment = sharedMemory.construct<u_int8_t>("data")[5](0); char* string1 = sharedMemory.construct<char>("String 1")[50]('\0'); // other stuff // placing stuff in the data segment for(int i(0); i < 5; i++) dataSegment[i] = anEarlierArray[i]; // then, in other process read the data Segment char ary[5]; for(int i(0); i< 5; i++) ary[i] = dataSegment.first[i]; For whatever reason I couldn't simply access through dataSegment[n] notation. The weirdest thing is, the data is being read back to me in the reverse order that it should be. For example, if [0x2,0x4,0x7,0x1] is written I read it back as [0x1,0x7,0x4,x02] even though I'm writing and reading in the same order. Why is this? What is it I'm missing about using shared memory? Thanks, Andy

1 0

[System] Getting error messages in English
by Igor R 27 Jun '13

27 Jun '13

I'd like to always get English error messages on Win7 with localized UI. As far as I can see, system_error_category::message() calls FormatMessageA passing it MAKELANGID(LANG_NEUTRAL, SUBLANG_DEFAULT). I tried to set locale, but it doesn't affect FormatMessageA for some reason. I'd appreciate any idea.

1 0

[1.54.0] Beta 1 Available
by Marshall Clow 27 Jun '13

27 Jun '13

Boost release 1.54.0 beta 1 is now available from SourceForge See http://sourceforge.net/projects/boost/files/boost/1.54.0.beta.1/ This release contains 3 new libraries: • Log: Logging library, from Andrey Semashev. • TTI: Type Traits Introspection library, from Edward Diener. • Type Erasure: Runtime polymorphism based on concepts. and numerous enhancements and bug fixes for existing libraries. For details of what's in the release, see http://www.boost.org/users/history/version_1_54_0.html. Note that the links to files on this web page are for the final release - use the SourceForge link above to get the beta files. Please download the beta, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team

5 4

Re: [Boost-users] [boost] [thread] synchronized_value: value and move semantics
by Klaim - Joël Lamotte 26 Jun '13

26 Jun '13

On Wed, Jun 26, 2013 at 12:37 PM, Ben Pope <benpope81(a)gmail.com> wrote: > > I think this should just not exist in C++11 and instead be replaced by > something like monitor<T> described by Herb Sutter [1]: I'm using several variants of Monitor in my projects. It don't work well in cases where what you really want is syncrhonization, which happen sometime when the design suggests it. In this case you need a mutex, so synchronized_value helps with that. In my opinion, If the multiple access is a bottleneck in real application, it is very easy to spot with a profiler and modify the code as you pointed. Joel Lamotte

1 0

Problem Iterating a directory
by Sarma Tangirala 26 Jun '13

26 Jun '13

Hello, I am using boost filesystem to iterate through my directory and have encountered a problem that I am unsure of how to debug. try { //for ( boostfs::directory_iterator dir(boostfs::path("/home/vtangira/Desktop/person_finder_v20130513/data/dummy1")), end_itr; for ( boostfs::directory_iterator dir(boostfs::path(paths_to_files.at(0).c_str())), end_itr; dir != end_itr; dir++ ) { std::cout << "File: " << dir->path() << std::endl; } } catch (boostfs::filesystem_error e) { cout << "Error Code: " << e.code() << endl << "Error Msg: " << e.code().message() << endl; } In this snippet, the line with the for loop that has been commented out works but the the one below it with the vector does not. The vector version represents the same string. Any advice is appreciated. Thanks -- 0 1 0 0 0 1 1 1 1

3 4

Re: [Boost-users] [Asio] Does stop() cancel handlers post()ed to io_service?
by Marat Abrarov 26 Jun '13

26 Jun '13

> However, I'm still interested whether stop() should always cancel the > queued handlers, i.e. if this is a bug (on windows). The io_service > documentation says this regarding the use of a work object > (http://alturl.com/98rvq) > > "To effect a shutdown, the application will then need to call the > io_service > object's stop() member function. This will cause the io_service run() > call > to return as soon as possible, abandoning unfinished operations and > without > permitting ready handlers to be dispatched. > Alternatively, if the application requires that all operations and > handlers > be allowed to finish normally, the work object may be explicitly > destroyed." I think (I've just inspected the Asio code) this behavior is designed in such a way for performance reasons - to not check "stopped" flag too often. Even the "stopped" flag is just an atomic value - it's Windows IOCP where OS uses specific technics for scheduling IOCP-tied threads and, may be, the author of Asio thinks (or even knows/has experience) that even atomic-value-check degrades performance or brakes specific scheduling of IOCP-tied threads. Regards, Marat Abrarov.

1 0

[Boost.Process] Status request
by Damien Kick 26 Jun '13

26 Jun '13

Thought that perhaps somebody on this list would know if/where a/the most current version of Boost.Process might be found. Or has this library been abandoned? Begin forwarded message: From: Damien Kick <dkick(a)shoretel.com<mailto:dkick@shoretel.com>> Subject: Boost.Process Date: June 25, 2013 5:16:10 PM CDT To: <boris(a)highscore.de<mailto:boris@highscore.de>> I've found your version of Boost.Process at <http://www.highscore.de/cpp/process/index.html>. I noticed that the date on this page is from 2009; are you still working on this library? If not, thank you for your effort so far. If you are still working on the library, I was hoping you might have some insights and/or help for a compilation error I'm finding when trying to use Boost.Process with Boost 1.53 on Windows 7 with Visual Studio 2010 SP1. First of all, I had to add a header file to .../process/operation.hpp; i.e. I had to add #include <boost/filesystem/operation.hpp> to get the declaration of boost::filesystem::filesystem_error. But then I'm finding the following error 1>------ Build started: Project: ZERO_CHECK, Configuration: Debug Win32 ------ 2>------ Build started: Project: test-cma, Configuration: Debug Win32 ------ 2> cma.cpp 2>Z:\Documents\perforce\dkick-mac\projects\DandM\DMTarget\windows-6.1\msvc-10.0\include\boost/process/detail/pipe.hpp(129): error C2665: 'boost::system::system_error::system_error' : none of the 7 overloads could convert all the argument types 2> Z:\Documents\perforce\dkick-mac\projects\DandM\DMTarget\windows-6.1\msvc-10.0\include\boost/system/system_error.hpp(39): could be 'boost::system::system_error::system_error(int,const boost::system::error_category &,const std::string &)' 2> Z:\Documents\perforce\dkick-mac\projects\DandM\DMTarget\windows-6.1\msvc-10.0\include\boost/system/system_error.hpp(43): or 'boost::system::system_error::system_error(int,const boost::system::error_category &,const char *)' 2> while trying to match the argument list '(DWORD, overloaded-function, const char [54])' ========== Build: 1 succeeded, 1 failed, 3 up-to-date, 0 skipped ========== Which is coming from .../boost/process/detail/pipe.hpp (the bold italic line below). From the quick skim I've given some of the documentation, I think the fact that BOOST_PROCESS_WINDOWS_USE_NAMED_PIPE is not defined means that I would find some features disabled, right? How is this determined; i.e. whether or not to define BOOST_PROCESS_WINDOWS_USE_NAMED_PIPE? # if defined(BOOST_PROCESS_WINDOWS_USE_NAMED_PIPE) static unsigned int nextid = 0; std::string pipe = "\\\\.\\pipe\\boost_process_" + boost::lexical_cast<std::string>(::GetCurrentProcessId()) + "_" + boost::lexical_cast<std::string>(nextid++); hs[0] = ::CreateNamedPipeA(pipe.c_str(), PIPE_ACCESS_INBOUND | FILE_FLAG_OVERLAPPED, 0, 1, 8192, 8192, 0, &sa); if (hs[0] == INVALID_HANDLE_VALUE) boost::throw_exception(boost::system::system_error(::GetLastError(), boost::system::system_category, "boost::process::detail::pipe::pipe: CreateNamedPipe failed")); hs[1] = ::CreateFileA(pipe.c_str(), GENERIC_WRITE, 0, NULL, OPEN_EXISTING, FILE_FLAG_OVERLAPPED, NULL); if (hs[1] == INVALID_HANDLE_VALUE) boost::throw_exception(boost::system::system_error(::GetLastError(), boost::system::system_category, "boost::process::detail::pipe::pipe: CreateFile failed")); OVERLAPPED overlapped; ZeroMemory(&overlapped, sizeof(overlapped)); overlapped.hEvent = ::CreateEvent(NULL, TRUE, FALSE, NULL); if (!overlapped.hEvent) boost::throw_exception(boost::system::system_error(::GetLastError(), boost::system::system_category, "boost::process::detail::pipe::pipe: CreateEvent failed")); BOOL b = ::ConnectNamedPipe(hs[0], &overlapped); if (!b) { if (::GetLastError() == ERROR_IO_PENDING) { if (::WaitForSingleObject(overlapped.hEvent, INFINITE) == WAIT_FAILED) { ::CloseHandle(overlapped.hEvent); boost::throw_exception(boost::system::system_error(::GetLastError(), boost::system::system_category, "boost::process::detail::pipe::pipe: WaitForSingleObject failed")); } } else if (::GetLastError() != ERROR_PIPE_CONNECTED) { ::CloseHandle(overlapped.hEvent); boost::throw_exception(boost::system::system_error(::GetLastError(), boost::system::system_category, "boost::process::detail::pipe::pipe: ConnectNamedPipe failed")); } } ::CloseHandle(overlapped.hEvent); # else if (!::CreatePipe(&hs[0], &hs[1], &sa, 0)) boost::throw_exception(boost::system::system_error(::GetLastError(), boost::system::system_category, "boost::process::detail::pipe::pipe: CreatePipe failed")); # endif ________________________________ This e-mail and any attachments are confidential. If it is not intended for you, please notify the sender, and please erase and ignore the contents.

1 0

Re: [Boost-users] [Asio] Does stop() cancel handlers post()ed to io_service?
by Marat Abrarov 26 Jun '13

26 Jun '13

> The program below gives different results on Windows (Visual Studio > 2008) and Linux. While stop() does cancel the handlers on Linux, the same > is not true for Windows. I also tried to destroy the io_service object > instead of calling stop, but this does not cancel the handlers on either > system, even though the documentation seems to state it should. It would be more accurate to say "on Windows asio::io_service::stop() does not cancel already queued (!) handlers". See example below. ~~~~~~~~~~~~~~~~~~~~~~~ #if defined(WIN32) #include <tchar.h> #endif #include <cstdlib> #include <cstddef> #include <iostream> #include <boost/ref.hpp> #include <boost/asio.hpp> #include <boost/bind.hpp> #include <boost/thread.hpp> #include <boost/function.hpp> namespace { typedef boost::function<void (boost::asio::io_service&)> work_factory; void run_test(work_factory wf) { { boost::asio::io_service io_service; { wf(io_service); std::cout << "io_service work created" << std::endl; { std::cout << "work thread starting..." << std::endl; boost::thread work_thread(boost::bind( &boost::asio::io_service::run, boost::ref(io_service))); boost::this_thread::sleep(boost::posix_time::millisec(300)); io_service.stop(); std::cout << "io_service signalled to stop" << std::endl; work_thread.join(); std::cout << "work thread stopped" << std::endl; } } std::cout << "destroying io_service..." << std::endl; } std::cout << "io_service destroyed" << std::endl; } void test_function1() { static int counter = 0; std::cout << "handler #" << counter++ << std::endl; boost::this_thread::sleep(boost::posix_time::millisec(100)); } void post_test_function1(boost::asio::io_service& io_service) { for (std::size_t i = 0; i != 10; ++i) { io_service.post(&test_function1); } } void post_test_function2(boost::asio::io_service&); void test_function2(boost::asio::io_service& io_service) { static int counter = 0; std::cout << "handler #" << counter++ << std::endl; boost::this_thread::sleep(boost::posix_time::millisec(100)); post_test_function2(io_service); } void post_test_function2(boost::asio::io_service& io_service) { io_service.post(boost::bind(test_function2, boost::ref(io_service))); } } // anonymous namespace #if defined(WIN32) int _tmain(int /*argc*/, _TCHAR* /*argv*/[]) #else int main(int /*argc*/, char* /*argv*/[]) #endif { std::cout << "Test 1" << std::endl; run_test(post_test_function1); std::cout << std::endl << "Test 2" << std::endl; run_test(post_test_function2); return EXIT_SUCCESS; } ~~~~~~~~~~~~~~~~~~~~~~~ Regards, Marat Abrarov.

2 1

Declaring tricky templated variables such as disjoint_sets.
by Jeremy Murphy 25 Jun '13

25 Jun '13

Hi, this is a somewhat general C++ question, but I'm specifically concerned about a Boost class in this case. How do I declare a boost::disjoint_sets<Rank, Parent, FindCompress> variable without some kind of automatic template deduction? Usually I see such classes declared taking their template parameters from within a function such as: template <typename Rank, typename Parent> void foo(Rank rank, Parent parent) { disjoint_sets<Rank, Parent> dset; } but what if I want to declare dset at file scope? I've been trying to manually construct the Rank and Parent types, but it's slightly doing my head in and the iterator_property_map example seems to be stale. Is there a general C++ technique or a Boost-specific one that can help me out here? Or is it just a matter of laboriously building up the typedefs? Thanks, cheers. Jeremy

2 1

[Asio] Does stop() cancel handlers post()ed to io_service?
by Martin Gernhard 25 Jun '13

25 Jun '13

Hello, I want to cancel all pending handlers of an io_service. Is io_service::stop() supposed to cancel handlers that have been added using post()? The documentation for stop() is somewhat ambiguous on this matter, only stating that run() "should return as soon as possible". Alternatively, should the destructor of io_service cancel the handlers? I am trying to build a "worker thread" using Boost.Asio (1.53) and Boost.Thread as outlined at http://think-async.com/Asio/Recipes. I have already looked at the documentation and searched the bug tracker, the mailing list archives, Google and Stack Overflow but only found an unanswered message from almost two years ago (http://lists.boost.org/boost-users/2011/09/70596.php) as well as another message that describes different behavior of stop() than what I am experiencing (http://thread.gmane.org/gmane.comp.lib.boost.user/73762) The program below gives different results on Windows (Visual Studio 2008) and Linux. While stop() does cancel the handlers on Linux, the same is not true for Windows. I also tried to destroy the io_service object instead of calling stop, but this does not cancel the handlers on either system, even though the documentation seems to state it should. Result on Windows for stop() and ~io_service and on Linux for ~io_service: Start 0 1 2 Stop 3 4 5 6 7 8 9 Result on Linux for stop(): Start 0 1 2 Stop For now I am using the workaround of querying a boost::atomic<bool> flag from every handler and setting it to false after calling stop(). Is there a better way to achieve this, maybe by implementing a custom IO object / service? It feels like overkill for something seemingly simple. Regards, Martin #include <boost/asio.hpp> #include <boost/bind.hpp> #include <boost/function.hpp> #include <boost/scoped_ptr.hpp> #include <boost/thread.hpp> #include <iostream> using namespace boost; using namespace boost::asio; void testFunction() { static int counter = 0; std::cout << counter++ << std::endl; this_thread::sleep( posix_time::millisec( 100 ) ); } int main() { shared_ptr<io_service> m_ioService(new io_service()); scoped_ptr<io_service::work> m_work(new io_service::work(*m_ioService)); scoped_ptr<thread> m_thread; for ( unsigned int i = 0; i != 10; ++i ) { m_ioService->post( &testFunction ); } std::cout << "Start" << std::endl; m_thread.reset( new thread( bind( &io_service::run, m_ioService ) ) ); this_thread::sleep( posix_time::millisec( 300 ) ); std::cout << "Stop" << std::endl; m_work.reset(); m_ioService->stop(); m_thread->join(); m_thread.reset(); m_ioService->reset(); return 0; }

1 0

[asio] synchronous read from sslstream with unknown length
by "Torsten Müller" 25 Jun '13

25 Jun '13

1 0

[asio] How to deal with no-connect and/or read-timeout
by Michael Powell 25 Jun '13

25 Jun '13

Hello, I posted previously, but this is a bit of a follow-on thought. Did some searching, and SO has this note: http://stackoverflow.com/questions/13126776/asioread-with-timeout Pardon me while I stare in disbelief. Seriously? Okay, I'd like to use Boost.Asio to facilitate things. Is this the way (one proposed way) of handling read-with-timeout? Our scenario goes similar to this I think: * Client may (or may not) connect, depending on the integration scenario. The main service thread should tolerate either, with plausibly the socket connection/session operating in another thread "asynchronously". * When client connects, the session logic is pretty straightforward: read if/when there is something to read, and pass it through a message framing unwrapper. Completed message gets deserialized and published into a thread-safe queue. * Events may be generated from the main service thread and subsequently published to the client: effectively a write operation, after passing a serialized message through a message framing wrapper. Doable? Feasible, possibly with some sort of a ping-ponging-back-and-forth type of session handling callback mechanism? I am cautiously optimistic that this has more to do with connection/session callback/state-machine type things, than it does Asio? Regards, Michael

2 2

[asio] Grasping the proto-typical socket server
by Michael Powell 25 Jun '13

25 Jun '13

Hello, I've dealt with sockets, and socket servers, in the past, so am familiar with them. Abstracting out a prototypical server details, drawing from the plethora of examples, this is what I can determine. I see three primary abstractions, the server itself, with endpoint binding, socket connection acceptor, so far so good. Then there's a connection, which is a sort of io_service to socket adapter. Followed closely by a session concern, where reads and writes are actually performed. Studying the examples, however, it seems to me that by design io_service wants to be *the* first class citizen that runs, with asynchronous callbacks being the mode of choice. How might we go about mixing this code, presumably in the main thread (?), with any worker service-oriented thread that might be going on. For instance, I start a thread and wait for it to finish and rejoin for a main service loop. Socket connection sessions are secondary to this service behavior taking place IMO. If a client connects, great, we'll interact with it. If not, that should be transparent to the application. Possibly session is a second thread worker with a thread-local-scope io_service, that we pub/sub messages to the main service loop. Thoughts on this type of approach? Much appreciated... Regards, Michael

2 1

Mutex synchronised wrapper class for boost::interprocess shared memory vector of strings
by Riskybiz 24 Jun '13

24 Jun '13

I'm trying to create a wrapper class to control a managed shared memory segment using Boost::Interprocess. I'm having trouble reading data from the shared memory vector of strings... When the vector is instantiated in the managed shared segment I place in the first vector element a test string; "testing testing 1 2 3". Immediately after placing it there and in the scope of the same code block I can access the vector element and print out the string using std::cout. However when I try to read the vector element using the read() function the test program crashes. The problem is with the line: std::string stdStr = sharedSegmentVector->at(index).c_str(); Question is how to fix this? I'm confused because at instantiation time this same code will access the shared memory vector; later on in the read() function it will not. I've as yet been unable to test the write() function; because I can't yet read() the vector! Any help to get this working is much appreciated, With thanks, Riskybiz Class Definition: #ifndef SHARED_MEMORY_WRAPPER_H//if not defined already #define SHARED_MEMORY_WRAPPER_H//then define it #include <boost/interprocess/managed_shared_memory.hpp> #include <boost/interprocess/containers/vector.hpp> #include <boost/interprocess/containers/string.hpp> #include <boost/interprocess/allocators/allocator.hpp> #include <boost/interprocess/sync/named_mutex.hpp> #include <iostream> #include <stdexcept> using namespace boost::interprocess; class SharedMemoryWrapper { public: SharedMemoryWrapper(const std::string &name, bool server) : m_name(name), m_server(server) { if (server) { named_mutex::remove("named_mutex"); shared_memory_object::remove(m_name.c_str()); //Create shared memory managed_shared_memory m_segment(create_only, m_name.c_str(), 10000); //Create allocators CharAllocator charallocator(m_segment.get_segment_manager()); StringAllocator stringallocator(m_segment.get_segment_manager()); //This string is in only in this process (the pointer pointing to the //buffer that will hold the text is not in shared memory). //But the buffer that will hold "this is my text" is allocated from //shared memory MyShmString mystring(charallocator); mystring = "testing testing 1 2 3"; //This vector is fully constructed in shared memory. All pointers //buffers are constructed in the same shared memory segment //This vector can be safely accessed from other processes. MyShmStringVector *sharedSegmentVector = m_segment.construct<MyShmStringVector>("sharedSegmentVector")(stringallocato r); sharedSegmentVector->push_back(mystring); std::string outStr = sharedSegmentVector->at(0).c_str(); std::cout << "Shared Memory Vector Instantiated: Index 0 Data is: " << outStr << std::endl; } else { //Open the shared segment managed_shared_memory m_segment(open_only, name.c_str()); //Find the vector using the c-string name and open it MyShmStringVector *sharedSegmentVector = m_segment.find<MyShmStringVector>("sharedSegmentVector").first; } m_mutex = new named_mutex(open_or_create, "named_mutex"); } ~SharedMemoryWrapper() { if (m_server) { named_mutex::remove("named_mutex"); //Destroy the vector from the managed_shared_memory //m_segment->destroy_ptr(sharedSegmentVector);//This will free all strings that the vector contains m_segment->destroy<MyShmStringVector>("sharedSegmentVector");//Destroy the vector //Is it necessary to destroy the allocators here? //Remove the managed_shared_memory; this may fail if the memory does not exist or is mapped or opened by another process shared_memory_object::remove(m_name.c_str()); } delete m_mutex; delete m_segment; } //Writer void write(const std::string &in) { try { CharAllocator charallocator(m_segment->get_segment_manager()); scoped_lock<named_mutex> lock(*m_mutex); MyShmString shmStr(in.c_str(), charallocator); sharedSegmentVector->push_back(shmStr); } catch(...) { std::cout << "Error in SharedMemoryWrapper::write(): unknown error" << std::endl; } } //Reader std::string read(int index) { try { scoped_lock<named_mutex> lock(*m_mutex); std::cout << "Shared Memory Vector Entered Read(), Passed Index: " << index << std::endl; std::string stdStr = sharedSegmentVector->at(index).c_str(); std::cout << "Shared Memory Vector Read At: Index" << index << "Data is: " << stdStr << std::endl; return stdStr; } catch(std::range_error err) { std::cout << "Error in SharedMemoryWrapper::read(): range_error" << std::endl; } catch(...) { std::cout << "Error in SharedMemoryWrapper::read(): unknown error " << std::endl; } return "ERROR IN SharedMemoryWrapper::read()"; } private: //Typedefs typedef boost::interprocess::allocator<char, managed_shared_memory::segment_manager> CharAllocator; typedef boost::interprocess::basic_string<char, std::char_traits<char>, CharAllocator> MyShmString; typedef boost::interprocess::allocator<MyShmString, managed_shared_memory::segment_manager> StringAllocator; typedef boost::interprocess::vector<MyShmString, StringAllocator> MyShmStringVector; bool m_server; std::string m_name; managed_shared_memory *m_segment; MyShmStringVector *sharedSegmentVector; named_mutex *m_mutex; };//class #endif//header guard Test Programme: #include "stdafx.h" #include "SharedMemoryWrapper.h" #include <iostream> #include <string> int main(int argc, char *argv[]) { SharedMemoryWrapper *smw = new SharedMemoryWrapper("SharedMemory1", true); std::string outStr = smw->read(0); std::cout << outStr << std::endl; return 0; }

2 1

Re: [Boost-users] Mutex synchronised wrapper class for boost::interprocess shared memory vector of strings
by Riskybiz 24 Jun '13

24 Jun '13

Date: Wed, 19 Jun 2013 22:05:32 +0200 From: Ion Gazta?aga <igaztanaga(a)gmail.com> To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] Mutex synchronised wrapper class for boost::interprocess shared memory vector of strings Message-ID: <51C20F0C.8090408(a)gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed El 18/06/2013 16:28, Riskybiz escribi?: > I'm trying to write a wrapper class in C++ to give mutex synchronised > interprocess access to a shared memory vector of strings. This is my first > foray into boost::interprocess and allocators are proving something of a > mystery. > > Is anyone able to see why on compilation I get the error: When you build any container in shared memory it must be constructed with an allocator. Change your push function to (not charallocator is passed to MyShmString): void push(const std::string & in) { CharAllocator charallocator(m_segment->get_segment_manager()); scoped_lock<named_mutex> lock(*m_mutex); MyShmString inStr(in.c_str(), charallocator); sharedSegmentVector->push_back(inStr); } Best, Ion Thanks for the reply Ion. I'm now having trouble reading from the vector in the shared memory. I get an exception when calling read(0) or read(1). What I'm trying to do is read "testing testing 123" from the first element of the sharedSegmentVector. Is it necessary to use some particular type conversion technique in the reader function to access a sharedSegmentVector string element? Any help to get this working is much appreciated; I've been trying for more than a month to get to this point! Code below..... Thanks Riskybiz #ifndef SHARED_MEMORY_WRAPPER_H//if not defined already #define SHARED_MEMORY_WRAPPER_H//then define it #include <boost/interprocess/managed_shared_memory.hpp> #include <boost/interprocess/containers/vector.hpp> #include <boost/interprocess/containers/string.hpp> #include <boost/interprocess/allocators/allocator.hpp> #include <boost/interprocess/sync/named_mutex.hpp> using namespace boost::interprocess; class SharedMemoryWrapper { public: SharedMemoryWrapper(const std::string &name, bool server) : m_name(name), m_server(server) { if (server) { named_mutex::remove("named_mutex"); shared_memory_object::remove(m_name.c_str()); //Create shared memory managed_shared_memory m_segment(create_only, m_name.c_str(), 10000); //Create allocators CharAllocator charallocator(m_segment.get_segment_manager()); StringAllocator stringallocator(m_segment.get_segment_manager()); //This string is in only in this process (the pointer pointing to the //buffer that will hold the text is not in shared memory). //But the buffer that will hold "this is my text" is allocated from //shared memory MyShmString mystring(charallocator); mystring = "testing testing 1 2 3"; //This vector is fully constructed in shared memory. All pointers //buffers are constructed in the same shared memory segment //This vector can be safely accessed from other processes. MyShmStringVector *sharedSegmentVector = m_segment.construct<MyShmStringVector>("sharedSegmentVector")(stringallocato r); sharedSegmentVector->push_back(mystring); } else { //Open the shared segment managed_shared_memory m_segment(open_only, name.c_str()); //Find the vector using the c-string name and open it MyShmStringVector *sharedSegmentVector = m_segment.find<MyShmStringVector>("sharedSegmentVector").first; } m_mutex = new named_mutex(open_or_create, "named_mutex"); } ~SharedMemoryWrapper() { if (m_server) { named_mutex::remove("named_mutex"); //Destroy the vector from the managed_shared_memory m_segment->destroy_ptr(sharedSegmentVector);//This will free all strings that the vector contains m_segment->destroy<MyShmStringVector>("sharedSegmentVector");//Destroy the vector //Is it necessary to destroy the allocators here? //Remove the managed_shared_memory; this may fail if the memory does not exist or is mapped or opened by another process shared_memory_object::remove(m_name.c_str()); } delete m_mutex; delete m_segment; } //Writer void write(const std::string &in) { CharAllocator charallocator(m_segment->get_segment_manager()); scoped_lock<named_mutex> lock(*m_mutex); MyShmString shmStr(in.c_str(), charallocator); sharedSegmentVector->push_back(shmStr); } //Reader std::string read(long index) { CharAllocator charallocator(m_segment->get_segment_manager()); scoped_lock<named_mutex> lock(*m_mutex); MyShmString shmStr(sharedSegmentVector->at(index), charallocator); std::string stdStr = std::string(shmStr.begin(), shmStr.end()); return stdStr; } private: //Typedefs typedef boost::interprocess::allocator<char, managed_shared_memory::segment_manager> CharAllocator; typedef boost::interprocess::basic_string<char, std::char_traits<char>, CharAllocator> MyShmString; typedef boost::interprocess::allocator<MyShmString, managed_shared_memory::segment_manager> StringAllocator; typedef boost::interprocess::vector<MyShmString, StringAllocator> MyShmStringVector; bool m_server; std::string m_name; managed_shared_memory *m_segment; MyShmStringVector *sharedSegmentVector; named_mutex *m_mutex; };//class #endif//header guard

2 1

[interprocess]shared_memory_object stores content in disk?
by Adrian Yu 24 Jun '13

24 Jun '13

I'm training multiple networks based on a single database. So to accelerate speed and reduce disk reading, I use shared_memory_object class provided by boost. Since the lab workstation is currently unavailable, I migrated my code to my personal computer. On the lab workstation, the host program successfully reads all data to memory. But on my PC, strangely it creates a file on system drive rather than storing the data in memory. The whole database is about 3.7 GB; the lab workstation has 32 GB memory and runs Windows Server 2008 R2; my PC has 8 GB memory and runs Windows 7. There should be enough memory to store the data. So why? Are there certain ways to force the program to keep all data in memory?

2 1

[Interprocess] Allocation algorithms
by Oodini 24 Jun '13

24 Jun '13

Hello, I need to allocate and fill about 10 big memories areas (several Gb) at the startup of my program. The data will never be modified or freed after during the program lifetime, and will be *only read* an other processes. What allocation algorithm should I take from the ones provided by the library ? Should I create a new one, more efficient (no reallocations, no race conditions...) ? Thanks.

3 3

[Interprocess] Minimal size of a managed_shared_memory
by Oodini 24 Jun '13

24 Jun '13

Hello, A managed_shared_memory is a typedef for a basic_managed_shared_memory using rbtree_best_fit as allocation algorithm. In the documentation : http://www.boost.org/doc/libs/1_53_0/doc/html/interprocess/memory_algorithm… It is said at the and of the page : "In most 32 systems with 8 byte alignment the minimum size of a block is 24 byte". I am on Windows XP SP3 32 bits. The alignement is 8 byte. But if I create a managed_shared_memory with a size lesser than 120 bytes, my app crashes. This value comes from several get_min_size function, the deepest being in the rbtree_best_fit class. So I wonder which value we can grant to the documentation above. How are the 120 bytes used ?

2 1

Boost::Interprocess Documentation request
by Riskybiz 24 Jun '13

24 Jun '13

In the Boost::Interprocess documentation and under the heading "Where is this being allocated?"; is an example of how to create a vector of strings in a managed_shared_memory segment. Link to Boost::Interprocess documentation here: http://www.boost.org/doc/libs/1_53_0/doc/html/interprocess/allocators_contai ners.html#interprocess.allocators_containers.containers_explained Please could this example be extended to demonstrate; 1. How to add string elements to the shared memory vector from a different process? 2. How to access and copy strings from the shared memory vector from a different process? This really would be invaluable to people trying to use Boost::Interprocess for the first time! My particular project has ground to a halt for over a month simply trying to get a working implementation of a Boost::Interprocess mutex synchronised shared memory vector of strings. I would like one process to add strings to the shared memory vector and several other processes to read string data from the vector. Right now I don't know if I'll ever get it to work! Running out of ideas here! Hope someone can help. Thanks, Riskybiz.

1 0

[property_tree] Serializing ptree to/from JSON
by Michael Powell 24 Jun '13

24 Jun '13

Hello, I am writing some code to serialize a package to/from JSON. Overall, it is working well, except for what appears to be a weak link in the ptree chain of events. I take a POCO (for all intents) and populate a ptree, then parse that to JSON using the property_tree JSON parser. No problem. Then I take that same string and want to parse it into another ptree. In and of itself, seems like it is no problem. The new ptree has a count, so I gather the parse worked. However, when I try to use ptree.count(path), or ptree.find(path), neither of these work. They are returning 0 or not_found(), respectively. I may be able to bypass that check for the moment and run it through ptree.get<Type>(path) for the time being, but that seems less desirable. Any insights on ptree along these lines? Thanks! Regards, Michael Powell

3 3

[FunctionTypes] Getting functor/lambda parameters (VS2012)
by Mateusz Loskot 23 Jun '13

23 Jun '13

Hi, I'm using C++ compiler from the latest VS2012. I'm trying this simple technique to determined type of functor or lambda call parameter, it works well: #include <boost/function_types/parameter_types.hpp> int main() { auto foo = [](int) -> void {}; typedef decltype(foo) foo_type; typedef boost::function_types::parameter_types < decltype(&foo_type::operator()) >::type parameter_types; } Next, I move the typedef into class template, in constructor body, it works well too: template <typename T> struct A { A(T t) { typedef typename boost::function_types::parameter_types < decltype(&T::operator()) >::type parameter_types; } }; Finally, I move further with the technique, so I can access parameter types within class template scope: template <typename T> struct B { typedef typename boost::function_types::parameter_types < decltype(&T::operator()) >::type parameter_types; }; This example does compile with clang 3.4 (svn trunk) and GCC 4.8.1, but it does not compile with Visual C++ 11.0. Does anyone understand what C++11 feaure VS2012 is lacking so it prevents compilation of the sample with B template above? Here is complete .cpp file https://gist.github.com/mloskot/5846468 Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

1 0

install with b2 - conflicting documentation
by Kirk Joppy 23 Jun '13

23 Jun '13

Hello, I am trying to build the regex library which I will then use through MinGW. I already installed MinGW and added ..\MinGW\bin to my system PATH. I now want to build regex and put it somewhere. I am aware of two different pieces of documentation detailing how to do this: http://www.boost.org/doc/libs/1_53_0/more/getting_started/windows.html#prep… http://www.boost.org/doc/libs/1_53_0/doc/html/bbv2/installation.html The main difference seems to be whether you should be in BOOST_ROOT or BOOST_ROOT\tools\build\v2. Which is it? In either case I gather than I should do this $ bootstrap.bat gcc and in fact I've done that in both BOOST_ROOT and BOOST_ROOT\tools\build\v2 with apparent success. I just don't know what I'm supposed to do next. I tried running $ b2 --prefix=H:\boost-test --with-regex install from within BOOST_ROOT\tools\build\v2, and that put some stuff into H:\boost-text, but I couldn't find any actual library files. Before I screw around any more I thought I'd ask knowledgeable folks for the right way to do this. Thank you very much, kjoppy

2 2

An example: how I learned to iterate through property trees (ptree)
by Cook, Rich 22 Jun '13

22 Jun '13

I just wanted to post a program I wrote that creates a boost::ptree, saves it to JSON, reads it back, then iterates through the tree and prints its nodes. #include <boost/property_tree/ptree.hpp> #include <boost/property_tree/json_parser.hpp> #include <string> #include <iostream> using namespace std; using boost::property_tree::ptree; string indent(int level) { string s; for (int i=0; i<level; i++) s += " "; return s; } void printTree (ptree &pt, int level) { if (pt.empty()) { cerr << "\""<< pt.data()<< "\""; } else { if (level) cerr << endl; cerr << indent(level) << "{" << endl; for (ptree::iterator pos = pt.begin(); pos != pt.end();) { cerr << indent(level+1) << "\"" << pos->first << "\": "; printTree(pos->second, level + 1); ++pos; if (pos != pt.end()) { cerr << ","; } cerr << endl; } cerr << indent(level) << " }"; } return; } int main(int, char*[]) { // first, make a json file: string tagfile = "testing2.pt"; ptree pt1; pt1.put("object1.type","ASCII"); pt1.put("object2.type","INT64"); pt1.put("object3.type","DOUBLE"); pt1.put("object1.value","one"); pt1.put("object2.value","2"); pt1.put("object3.value","3.0"); pt1.put("object4.type", "ASCII"); pt1.put("object4.value", "shallow"); pt1.put("object4.subobject1.type", "ASCII"); pt1.put("object4.subobject1.value", "deep child"); pt1.put("object4.subobject1.subsubobject.type", "ASCII"); pt1.put("object4.subobject1.subsubobject.value", "deep child"); pt1.put("object5.type", "ASCII"); pt1.put("object5.value", "shallow"); write_json(tagfile, pt1); ptree pt; bool success = true; //try { read_json(tagfile, pt); printTree(pt, 0); cerr << endl; return success; } PROGRAM OUTPUT: rcook@rzbeast (blockbuster): ./ptree { "object1": { "type": "ASCII", "value": "one" }, "object2": { "type": "INT64", "value": "2" }, "object3": { "type": "DOUBLE", "value": "3.0" }, "object4": { "type": "ASCII", "value": "shallow", "subobject1": { "type": "ASCII", "value": "deep child", "subsubobject": { "type": "ASCII", "value": "deep child" } } }, "object5": { "type": "ASCII", "value": "shallow" } } -- ✐Richard Cook ✇ Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ☎ (office) (925) 423-9605 ☎ (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL)

2 1

[smart_ptr] enable_shared_from_this and shared_ptr to a base class
by Adam Romanek 21 Jun '13

21 Jun '13

Hi, I have a question related to using shared_from_this() and a shared_ptr to a base class. Here's a modified version of the enable_shared_from_this usage example from its documentation web page: #include <boost/enable_shared_from_this.hpp> #include <boost/shared_ptr.hpp> #include <cassert> class X { public: virtual void foo() = 0; }; class Y: public X, public boost::enable_shared_from_this<Y> { virtual void foo() { shared_from_this(); } }; int main() { X* x_ptr = new Y; boost::shared_ptr<X> sp(x_ptr); sp->foo(); } First, class Y is now derived from class X. Secondly, shared_ptr's template argument is now X and the parameter to the shared_ptr's constructor is now a pointer to X. Now, calling shared_from_this() in X and/or Y throws boost::bad_weak_ptr. Is this correct behavior? Is it documented somewhere? I know that the example is a bit unrealistic since most of the time shared_ptr is constructed directly from the pointer returned by 'new Y' or created by make_shared() but still, this is something that bothers me. WBR, Adam Romanek

1 0

Re: [Boost-users] [Test]: Problem with simple Boost.Test
by Damien Kick 21 Jun '13

21 Jun '13

On Jun 20, 2013, at 8:38 PM, <boost-users-request(a)lists.boost.org<mailto:boost-users-request@lists.boost.org>> wrote: Date: Thu, 20 Jun 2013 17:01:54 +0000 (UTC) From: Gennadiy Rozental <rogeeff(a)gmail.com<mailto:rogeeff@gmail.com>> To: boost-users(a)lists.boost.org<mailto:boost-users@lists.boost.org> Subject: Re: [Boost-users] [Test]: Problem with simple Boost.Test Message-ID: <loom.20130620T185812-619(a)post.gmane.org<mailto:loom.20130620T185812-619@post.gmane.org>> Content-Type: text/plain; charset=utf-8 thusly:$ ${CXX} -c --std=c++0x -g -I${TARGET}/include cma.cpp -o cma.o $ ${CXX} --std=c++0x -g cma.o ${TARGET}/lib/libboost_test_exec_monitor.a \ ${TARGET}/lib/libboost_unit_test_framework.dylib -o cma I know docs are not ideal but this part is very clear I thought. test_exec_monitor is an old alternative t ounit test framework, which is long deprecated and they definitely do not require each other In this case, I wouldn't fault the docs per se but rather only my impatience in having tried "jumping directly to the subject of [my] interest" but not yet having realized exactly what my subject of interest really is/was nor how far I needed to jump in order to get to it ;-) I had been trying this: $ cat cma.cpp #define BOOST_TEST_MODULE cma #include <boost/test/unit_test.hpp> #include <iostream> #include <ostream> BOOST_AUTO_TEST_CASE(sanity) { std::clog << "Test the world!\n"; } $ ${CXX} -c --std=c++0x -g -I${TARGET}/include cma.cpp -o cma.o $ ${CXX} --std=c++0x -g cma.o ${TARGET}/lib/libboost_unit_test_framework.dylib -o cma Undefined symbols for architecture x86_64: "_main", referenced from: implicit entry/start for main executable ld: symbol(s) not found for architecture x86_64 collect2: error: ld returned 1 exit status $ But when I started reading through more of the documentation and got as far as <http://preview.tinyurl.com/lw7e688>, I realized that I needed to be doing something more like this: $ ${CXX} -c --std=c++0x -g -DBOOST_TEST_DYN_LINK -I${TARGET}/include cma.cpp -o cma.o $ ${CXX} --std=c++0x -g cma.o ${TARGET}/lib/libboost_unit_test_framework.dylib -o cma $ env DYLD_LIBRARY_PATH=${TARGET}/lib ./cma Running 1 test case... Test the world! *** No errors detected $ Thank you, Gennadiy, for having taken the time to respond to my question as well as having taken the time you spent on Boost.Test. ________________________________ This e-mail and any attachments are confidential. If it is not intended for you, please notify the sender, and please erase and ignore the contents.

1 0

Re: [Boost-users] [Test]: Problem with simple Boost.Test
by Damien Kick 21 Jun '13

21 Jun '13

Date: Mon, 17 Jun 2013 23:03:16 +0000 (UTC) From: legalize+jeeves(a)mail.xmission.com<mailto:legalize+jeeves@mail.xmission.com> (Richard) To: boost-users(a)lists.boost.org<mailto:boost-users@lists.boost.org> Subject: Re: [Boost-users] [Test]: Problem with simple Boost.Test Message-ID: <kpo4jk$2ih$2(a)ger.gmane.org<mailto:kpo4jk$2ih$2@ger.gmane.org>> [Please do not mail me a copy of your followup] boost-users(a)lists.boost.org<mailto:boost-users@lists.boost.org> spake the secret code <7364AB234369D348AE1CEBC1A86132DBAD32EA(a)SVLITMX02.shoretel.com<http://SVLITMX02.shoretel.com>> thusly: $ ${CXX} -c --std=c++0x -g -I${TARGET}/include cma.cpp -o cma.o $ ${CXX} --std=c++0x -g cma.o ${TARGET}/lib/libboost_test_exec_monitor.a \ ${TARGET}/lib/libboost_unit_test_framework.dylib -o cma Why are you linking against boost_test_exec_monitor? I've never needed to do that. boost_unit_test_framework should be enough. Interesting. Because I'm finding the following: $ ${CXX} -c --std=c++0x -g -I${TARGET}/include cma.cpp -o cma.o $ ${CXX} --std=c++0x -g cma.o ${TARGET}/lib/libboost_unit_test_framework.dylib -o cma Undefined symbols for architecture x86_64: "_main", referenced from: implicit entry/start for main executable ld: symbol(s) not found for architecture x86_64 collect2: error: ld returned 1 exit status $ But that is also what I'm finding with the system GCC and the Fink install of Boost 1.46, and so that behavior isn't unique my attempt to build/use a Boost with GCC 4.8.0 using --std=c++0x. $ g++ -c -g -I/sw/include cma.cpp -o cma.o $ g++ -g -L/sw/lib cma.o -lboost_unit_test_framework-mt Undefined symbols for architecture x86_64: "_main", referenced from: start in crt1.10.6.o ld: symbol(s) not found for architecture x86_64 collect2: ld returned 1 exit status $ g++ --version i686-apple-darwin11-llvm-g++-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00) Copyright (C) 2007 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. $ fink list --tab boost1.46 Information about 7237 packages read in 1 seconds. i boost1.46.1.cmake 1.46.1-2 Boost C++ Libraries i boost1.46.1.cmake-shlibs 1.46.1-2 Boost C++ Libraries $ ________________________________ This e-mail and any attachments are confidential. If it is not intended for you, please notify the sender, and please erase and ignore the contents.

3 2

matrix inversion in boost.
by Mohit Singh 21 Jun '13

21 Jun '13

Hi, I am trying to do a simple matrix inversion operation using boost. But I am getting an error. Basically what I am trying to find is inversted_matrix = inverse(trans(matrix) * matrix) But I am getting an error Check failed in file boost_1_53_0/boost/numeric/ublas/lu.hpp at line 299: detail::expression_type_check (prod (triangular_adaptor<const_matrix_type, upper> (m), e), cm2) terminate called after throwing an instance of 'boost::numeric::ublas::internal_logic' what(): internal logic Aborted (core dumped) My attempt: #include <boost/numeric/ublas/matrix.hpp> #include <boost/numeric/ublas/vector.hpp> #include <boost/numeric/ublas/io.hpp> #include <boost/numeric/ublas/vector_proxy.hpp> #include <boost/numeric/ublas/matrix.hpp> #include <boost/numeric/ublas/triangular.hpp> #include <boost/numeric/ublas/lu.hpp> namespace ublas = boost::numeric::ublas; template<class T> bool InvertMatrix (const ublas::matrix<T>& input, ublas::matrix<T>& inverse) { using namespace boost::numeric::ublas; typedef permutation_matrix<std::size_t> pmatrix; // create a working copy of the input matrix<T> A(input); // create a permutation matrix for the LU-factorization pmatrix pm(A.size1()); // perform LU-factorization int res = lu_factorize(A,pm); if( res != 0 ) return false; // create identity matrix of "inverse" inverse.assign(ublas::identity_matrix<T>(A.size1())); // backsubstitute to get the inverse lu_substitute(A, pm, inverse); return true; } int main(){ using namespace boost::numeric::ublas; matrix<double> m(4,5); vector<double> v(4); vector<double> thetas; m(0,0) = 1; m(0,1) = 2104; m(0,2) = 5; m(0,3) = 1;m(0,4) = 45; m(1,0) = 1; m(1,1) = 1416; m(1,2) = 3; m(1,3) = 2;m(1,4) = 40; m(2,0) = 1; m(2,1) = 1534; m(2,2) = 3; m(2,3) = 2;m(2,4) = 30; m(3,0) = 1; m(3,1) = 852; m(3,2) = 2; m(3,3) = 1;m(3,4) = 36; std::cout<<m<<std::endl; matrix<double> product = prod(trans(m), m); std::cout<<product<<std::endl; matrix<double> inversion(5,5); bool inverted; inverted = InvertMatrix(product, inversion); std::cout<<inversion<<std::endl; } -- Mohit "When you want success as badly as you want the air, then you will get it. There is no other secret of success." -Socrates

1 0

[BGL] boykov_kolbogorov_max_flow() classes / groups
by Nil Goyette 20 Jun '13

20 Jun '13

I have been testing the the boykov_kolbogorov_max_flow function in the previous weeks and I have a question that I can't seem to find the answer myself. I asked for it on StackOverflow [1] but nobody answered. Can someone tell me why I get three classes (groups) instead of two? I always get class '0' and '4', and '1' on some cases. I thought a Graph Cut was supposed to output only two classes, so what's the meaning of '1'? Please read the SO question in [1] for more details. Thanks for your time. Nil Goyette [1] http://stackoverflow.com/questions/16905613/3-classes-0-1-4-on-boost-graph-…

1 0

accumulator extended quantil value
by Philipp Kraus 20 Jun '13

20 Jun '13

Hello, I have got created an extended_p_square_quantile into an accumulator, with 3 quantils (0.25, 0.5, 0.75) as a boost::array. How can I get access to the quantil values of the accumulator? For the variance I use accumulator::variance(myacc), but a call with quantil(myacc, 0.5) does not work. Thanks Phil

2 3

boost_1_53_0: no matching function for call to ‘hash_value
by Shailja Kumari 20 Jun '13

20 Jun '13

> Hi , > > I am using boost_1_53_0 for my applications build. The boost_1_53_0 is > throwing the following error message. > > boost_1_53_0/boost/functional/hash/extensions.hpp:269:34: error: no > matching function for call to ‘hash_value(const > Rubedo::Utils::Hashing::HashedString<16>&)’ > return hash_value(val); > ^ > > boost_1_53_0/boost/functional/hash/hash.hpp:187:57: error: no type named > ‘type’ in ‘struct > boost::hash_detail::basic_numbers<Rubedo::Utils::Hashing::HashedString<16> > >’ > > The following code build fine with boost_1_49_0, but have error with > boost_1_53_0 on linux. Do you have fixes for these ? Please let me know. > > Thanks > >

2 1

boost serialisation, PORTABLE_BINARY_ARCHIVE fix required
by avib369 . 20 Jun '13

20 Jun '13

Currently portable binary archive is broken on AIX platforms. The reason is because the default 'char' type is unsigned on this platform. Whereas for most other platforms it is signed, By going through the portable binary and replacing 'char' with 'signed char' this long standing bug is fixed. I have tested the fix on Linux(opensuse103,opensuse113, HPUX, AIX(power6,power7) This is a fairly safe and quick fix, can I please ask the authors of this library to add this fix, for the next version of boost. Here are the changes I made: (flagged under ' // changed ' comment //-------------------------------------------------------- portable_binary_iarchive.hpp void load(signed char & t){ // changed this->primitive_base_t::load(t); } //------------------------------------------------------------- portable_binary_iarchive.cpp void portable_binary_iarchive::load_impl(boost::intmax_t & l, char maxsize){ signed char size; // changed l = 0; this->primitive_base_t::load(size); if(0 == size){ return; } bool negative = (size < 0); ...... // ----------------------------------------------------------------- portable_binary_oarchive.hpp void save(const signed char & t){ // changed this->primitive_base_t::save(t); } // ----------------------------------------------------------- portable_binary_oarchive.cpp void portable_binary_oarchive::save_impl( const boost::intmax_t l, const char maxsize ){ signed char size = 0; // changed if(l == 0){ this->primitive_base_t::save(size); return; } .......... // ------------------------------ Ta, Avi

2 1

[property_tree] Population and Json formatting
by Michael Powell 20 Jun '13

20 Jun '13

Hello, Question about property tree. I've got an "event" concept which I want to serialize to Json through property tree. If I go something like this: ptree tree; tree.set<int>("event.id", 1); Then the resulting Json would look something like this? { "event": { "id": 1 } } or possibly? { "event": { "id" : "1" } } or possibly, with pretty turned off (nicer for message framing). {"event":{"id":"1"}} Thank you... Regards, Michael Powell

1 0

Boost and Norton 360
by Scott Alexander 20 Jun '13

20 Jun '13

Hi, I have just installed boost 1.53 32bit using the Sourceforge Visual Studio installer and my security software (Norton 360) has quarantined three files as being high risk: *boost_math_tr1f-vc110-mt-1_53.dll *boost_thread-vc110-mt-gd-1_53.dll *boost_filesystem-vc110-mt-gd-1_53.dll Does anyone know if this is common? Can I safely restore these files? Thanks, Scott

3 2

errors in boost build - 1.5.3 on Linux Mint 15 (Olivia) 64-bit
by asif saeed 20 Jun '13

20 Jun '13

Hi, I am trying to build boost 1.53 using GCC and have got the following errors: ...failed updating 348 targets... ...skipped 72 targets... ...updated 4568 targets... The "failed updating 348 targets..." shows that something has definitely gone wrong. Can any kind soul tell me what has happened? I used the following command after bootstrap: ./b2 --prefix=./ --build-type=complete --stagedir=./stage --layout=versioned --toolset=gcc Help me please. -Best regards, -Asif

2 1

[program_options] Custom Validation for a String Value
by Ryan 19 Jun '13

19 Jun '13

Hello, Is there a way of validating a string type program option before it's stored in the map? add_options() ("arg" , value<std::string>()->default_value("Hi"), "Greeting"); boost::regex pattern("^(Hello | Good Morning | Hi)$"); I've used custom validation for types that program options doesn't recognize. I'd like to check the string before it's stored in the map like the custom validation does for unknown types. I'd rather the error be caught early. Is there a way to use the regex against the program option? Ryan

1 0

Mutex synchronised wrapper class for boost::interprocess shared memory vector of strings
by Riskybiz 19 Jun '13

19 Jun '13

I'm trying to write a wrapper class in C++ to give mutex synchronised interprocess access to a shared memory vector of strings. This is my first foray into boost::interprocess and allocators are proving something of a mystery. Is anyone able to see why on compilation I get the error: error C2512: 'boost::interprocess::allocator::allocator' : no appropriate default constructor available C:\Program Files (x86)\Boost\boost_1_53_0\boost\container\string.hpp #ifndef SHARED_MEMORY_WRAPPER_H//if not defined already #define SHARED_MEMORY_WRAPPER_H//then define it #include <boost/interprocess/managed_shared_memory.hpp> #include <boost/interprocess/containers/vector.hpp> #include <boost/interprocess/containers/string.hpp> #include <boost/interprocess/allocators/allocator.hpp> #include <boost/interprocess/sync/named_mutex.hpp> using namespace boost::interprocess; class SharedMemoryWrapper { public: SharedMemoryWrapper(const std::string &name, bool server) : m_name(name), m_server(server) { if (server) { named_mutex::remove("named_mutex"); shared_memory_object::remove(m_name.c_str()); //Create shared memory managed_shared_memory m_segment(create_only, m_name.c_str(), 10000); //Create allocators CharAllocator charallocator(m_segment.get_segment_manager()); StringAllocator stringallocator(m_segment.get_segment_manager()); //This string is in only in this process (the pointer pointing to the //buffer that will hold the text is not in shared memory). //But the buffer that will hold "this is my text" is allocated from //shared memory MyShmString mystring(charallocator); mystring = "this is my text"; //This vector is fully constructed in shared memory. All pointers //buffers are constructed in the same shared memory segment //This vector can be safely accessed from other processes. MyShmStringVector *sharedSegmentVector = m_segment.construct<MyShmStringVector>("sharedSegmentVector")(stringallocato r); sharedSegmentVector->push_back(mystring); } else { //Open the shared segment managed_shared_memory m_segment(open_only, name.c_str()); //Find the vector using the c-string name and open it MyShmStringVector *sharedSegmentVector = m_segment.find<MyShmStringVector>("sharedSegmentVector").first; } m_mutex = new named_mutex(open_or_create, "named_mutex"); } ~SharedMemoryWrapper() { if (m_server) { named_mutex::remove("named_mutex"); //Destroy the vector from the managed_shared_memory m_segment->destroy_ptr(sharedSegmentVector);//This will free all strings that the vector contains m_segment->destroy<MyShmStringVector>("sharedSegmentVector");//Destroy the vector //Is it necessary to destroy the allocators here? //Remove the managed_shared_memory; this may fail if the memory does not exist or is mapped or opened by another process shared_memory_object::remove(m_name.c_str()); } delete m_mutex; delete m_segment; } //Writer void push(const std::string & in) { scoped_lock<named_mutex> lock(*m_mutex); MyShmString inStr = in.c_str(); sharedSegmentVector->push_back(inStr); } //Reader function yet to be coded. Needs to return a vector containing a subset range of elements from the shared-memory-vector. private: //Typedefs typedef boost::interprocess::allocator<char, managed_shared_memory::segment_manager> CharAllocator; typedef boost::interprocess::basic_string<char, std::char_traits<char>, CharAllocator> MyShmString; typedef boost::interprocess::allocator<MyShmString, managed_shared_memory::segment_manager> StringAllocator; typedef boost::interprocess::vector<MyShmString, StringAllocator> MyShmStringVector; bool m_server; std::string m_name; managed_shared_memory *m_segment; MyShmStringVector *sharedSegmentVector; named_mutex *m_mutex; };//class #endif//header guard With thanks, Riskybiz

2 1

[statechart] [spirit] OSI delimited message framing
by Michael Powell 19 Jun '13

19 Jun '13

Hello, I need to design a delimited message framing for TCP/IP sockets, probably using Asio to facilitate transport. Then build an OSI layer 7 application vernier to handle framing. I've dabbled a bit with Spirit and cooked up a couple of "simple" micro grammars throughout the code base. In a sense, I could see a delimited message framing strategy being a grammar of sorts, but this seems somewhat complex for a grammar to handle when you consider the overhead of verifying pass/fail (message or not a message), plus extracting the message within the delimiters. Or, more likely approach the problem with statechart in mind. I've dealt with framed messages in the past more like this. One state is the escape byte, which can be followed by SOM, EOM, or another true-escape-byte (intended message byte). Plus other fields like message type, sub-type, how to handle payload, arguments, and so forth. Anyone else dealt with things like this before? With Spirit? With Statechart? Regards, Michael Powell

5 5

Re: [Boost-users] Boost-users Digest, Vol 3479, Issue 1
by Damien Kick 19 Jun '13

19 Jun '13

Date: Mon, 17 Jun 2013 23:03:16 +0000 (UTC) From: legalize+jeeves(a)mail.xmission.com<mailto:legalize+jeeves@mail.xmission.com> (Richard) To: boost-users(a)lists.boost.org<mailto:boost-users@lists.boost.org> Subject: Re: [Boost-users] [Test]: Problem with simple Boost.Test Message-ID: <kpo4jk$2ih$2(a)ger.gmane.org<mailto:kpo4jk$2ih$2@ger.gmane.org>> [Please do not mail me a copy of your followup] boost-users(a)lists.boost.org<mailto:boost-users@lists.boost.org> spake the secret code <7364AB234369D348AE1CEBC1A86132DBAD32EA(a)SVLITMX02.shoretel.com<http://SVLITMX02.shoretel.com>> thusly: $ ${CXX} -c --std=c++0x -g -I${TARGET}/include cma.cpp -o cma.o $ ${CXX} --std=c++0x -g cma.o ${TARGET}/lib/libboost_test_exec_monitor.a \ ${TARGET}/lib/libboost_unit_test_framework.dylib -o cma Why are you linking against boost_test_exec_monitor? I've never needed to do that. boost_unit_test_framework should be enough. Interesting. Because I'm finding the following: $ ${CXX} -c --std=c++0x -g -I${TARGET}/include cma.cpp -o cma.o $ ${CXX} --std=c++0x -g cma.o ${TARGET}/lib/libboost_unit_test_framework.dylib -o cma Undefined symbols for architecture x86_64: "_main", referenced from: implicit entry/start for main executable ld: symbol(s) not found for architecture x86_64 collect2: error: ld returned 1 exit status $ But that is also what I'm finding with the system GCC and the Fink install of Boost 1.46, and so that behavior isn't unique my attempt to build/use a Boost with GCC 4.8.0 using --std=c++0x. $ g++ -c -g -I/sw/include cma.cpp -o cma.o $ g++ -g -L/sw/lib cma.o -lboost_unit_test_framework-mt Undefined symbols for architecture x86_64: "_main", referenced from: start in crt1.10.6.o ld: symbol(s) not found for architecture x86_64 collect2: ld returned 1 exit status $ g++ --version i686-apple-darwin11-llvm-g++-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00) Copyright (C) 2007 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. $ fink list --tab boost1.46 Information about 7237 packages read in 1 seconds. i boost1.46.1.cmake 1.46.1-2 Boost C++ Libraries i boost1.46.1.cmake-shlibs 1.46.1-2 Boost C++ Libraries $ ________________________________ This e-mail and any attachments are confidential. If it is not intended for you, please notify the sender, and please erase and ignore the contents.

1 0

[asio] Serial and TCP I/O
by Michael Powell 19 Jun '13

19 Jun '13

Hello, I have an application that I'd like to leverage some common code if at all possible (and/or necessary), using concepts of client/server, reader/writer, and so on. Probably also TCP/IP and/or Serial, although I gather Asio has a serial class ready to go out of the box? Serial is pretty much a "no brainer", can be a server, but to talk to devices in our use case, always the client, can be either reader or writer or both. The key question here is, do we need a separate io_service for serial as well as for TCP? Regards, Michael Powell

2 1

What is the status of the BGL-Python Bindings project
by lizy10b 19 Jun '13

19 Jun '13

Hi there, I would like to know what is the status of the BGL-Python Bindings project? The Boost 1.53 document says that "The Python bindings for the BGL are now part of a separate project" and links to http://www.osl.iu.edu/~dgregor/bgl-python/ On that page I find that the latest version is 0.9 which was released in 2005. So it means the BGL-Python Binding project is not on going? Is the BGL-Python Bindings 0.9 compatible to Boost 1.53 ? Or any other ways to use Boost graph functionalities in python? Thanks Zhiyu Li 2013-06-19 lizy10b

3 7

[build] Problem building using Intel C++ compiler
by Jason 19 Jun '13

19 Jun '13

I'm trying to build v1.53 using the Intel C++ compiler and am having some problems. I'm issuing the following commands: ./bootstrap.sh --with-toolset=intel-linux ./b2 toolset=intel-linux Upon executing the second command, I get the following error: error: intel-linux initialization: parameter 'version' inconsistent error: no value was specified in earlier initialization error: an explicit value is specified now This appears to be similar to a mailing list thread regarding v1.39, archived here: https://groups.google.com/forum/#!topic/boost-list/gu9wf3cr15Y It appears that there is a workaround listed there (and a corresponding Trac ticket #3165) that involves hand-manipulation of bjam configuration files, but it seems like this is something that should work out of the box if Intel C++ is a supported toolset. Is there any chance that this would be fixed in the future? Jason -- View this message in context: http://boost.2283326.n4.nabble.com/build-Problem-building-using-Intel-C-com… Sent from the Boost - Users mailing list archive at Nabble.com.

1 0

[BGL] null_vertex()
by Andreas Fabri 18 Jun '13

18 Jun '13

Hello, I am wondering what the function boost::graph_traits<G>::null_vertex() http://www.boost.org/doc/libs/1_53_0/libs/graph/doc/Graph.html is for, and why there is no equivalent function null_edge() best regards, andreas -- Andreas Fabri, PhD Chief Officer, GeometryFactory Editor, The CGAL Project phone: +33.492.954.912 skype: andreas.fabri

2 2

[Test]: Problem with simple Boost.Test
by Damien Kick 17 Jun '13

17 Jun '13

I'm trying to get what I think should be a simple example of Boost.Test (Boost 1.53) to work but I'm getting a segmentation fault, having used other of the Boost libraries from the same build/install of 1.53 without any problems. Am I doing anything obviously wrong? Thanks in advance for any help. $ cat test/cma.cpp #define BOOST_TEST_MODULE cma #include <boost/test/unit_test.hpp> #include <iostream> #include <ostream> BOOST_AUTO_TEST_CASE(sanity) { std::clog << "Test the world!\n"; } $ make check [100%] Building CXX object CMakeFiles/test-cma.dir/test/cma.cpp.o Linking CXX executable test-cma [100%] Built target test-cma [100%] Built target check $ env DYLD_LIBRARY_PATH=${TARGET}/lib ./test-cma Running 1 test case... Test the world! Segmentation fault: 11 $ Here are some more details. I'm trying this on Mac with GCC. $ uname -a Darwin Damien-Kicks-MacBook-Pro.local 12.4.0 Darwin Kernel Version 12.4.0: \ Wed May 1 17:57:12 PDT 2013; root:xnu-2050.24.15~1/RELEASE_X86_64 x86_64 $ ${CXX} --version g++ (GCC) 4.8.0 Copyright (C) 2013 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. I've compiled my build/install of Boost 1.53 with --std=c++0x. Again, I've used other libraries from this same build/install (DateTime, Filesystem, Random, Regex, Serialization, System, Thread), so I don't think that the problem is my use of --std=c++0x in and of itself. $ ${CXX} -c --std=c++0x -g -I${TARGET}/include cma.cpp -o cma.o $ ${CXX} --std=c++0x -g cma.o ${TARGET}/lib/libboost_test_exec_monitor.a \ ${TARGET}/lib/libboost_unit_test_framework.dylib -o cma $ env DYLD_LIBRARY_PATH=${TARGET}/lib ./cma Running 1 test case... Test the world! Segmentation fault: 11 $ If I run this under GDB (gdb) run Starting program: cma Reading symbols for shared libraries ++++.............................. done Running 1 test case... Test the world! Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000000 boost::unit_test::framework::get (id=65536, t=tut_case) at \ impl/framework.ipp:388 388 if( (res->p_type & t) == 0 ) (gdb) bt #0 boost::unit_test::framework::get (id=65536, t=tut_case) at \ impl/framework.ipp:388 #1 0x0000000100134805 in boost::unit_test::traverse_test_tree \ (suite=@0x100403f10, V=@0x7fff5fbff470) at framework.hpp:73 Previous frame inner to this frame (gdb could not unwind past this frame) (gdb) print res $1 = ('boost::unit_test::test_unit' *) 0x0 (gdb) ________________________________ This e-mail and any attachments are confidential. If it is not intended for you, please notify the sender, and please erase and ignore the contents.

2 1

[filesystem] Create file with a unicode filename/path
by Konstantin Kronfeldner 17 Jun '13

17 Jun '13

Hello, I'm working under windows 7 with mingw. I have encountered some weird behaviour with unicode filenames. My program needs to be portable, and I'm using boost::filesystem (v 1.53) to handle the file paths. This has all been going well, until I needed to open files with unicode filenames. This is not about the content of the file, but the file's name/path. I tried the following: For testing I made a folder named C:\UnicodeTest\|????????|and I tried creating a file inside of it, by appending the file name test.txt to the boost wpath. For some reason the creation of the file fails. I'm using boost's fstreams and when I try to open the file, the failbit of the stream is set. Now the funny thing is, that when I append a foldername to the path instead, a call to create_directories() succeeds and creates the correct directory C:\UnicodeTest\|????????|\folder. I really don't understand why it won't work with a file. I have also posted my problem on stackoverflow. http://stackoverflow.com/questions/16875025/open-a-file-with-unicode-path No luck so far. This is the code I use: boost::filesystem::wpath path; // find the folder to test (There are no other folders in C:\UnicodeTest) boost::filesystem::wpath dirPath = "C:\\UnicodeTest"; vector<boost::filesystem::wpath> files; copy(boost::filesystem::directory_iterator(dirPath), boost::filesystem::directory_iterator(), back_inserter(files)); for(boost::filesystem::wpath &file : files) { if(boost::filesystem::is_directory(file)) { path = file; break; } } // create a path for the folder boost::filesystem::wpath folderPath = path / "folder"; // this works just fine boost::filesystem::create_directories(folderPath); // create a path for the file boost::filesystem::wpath filePath = path / "test.txt"; boost::filesystem::ofstream stream; // this fails stream.open(filePath); if(!stream) { cout << "failed to open file " << path << endl; } else { cout << "success" << endl; }

1 0

Comparison boost spirit and ANTLR
by Olivier Austina 17 Jun '13

17 Jun '13

Hi, I would like to choose a parser. I would like to use a parser for text processing (natural language text). Which parser is suited in this case. In general which are the benefit to use boost spirit instead of ANTLR or ANTLR instead of boost spirit. Thank you. -- Regards Austina

9 15

[statechart] state_machine send_event assertion fails
by Gooding, Dustin R. (JSC-ER411) 17 Jun '13

17 Jun '13

Hello, I'm a new user of statechart and for the most part am enjoying it very much. I've implemented a state machine with about 30 states (9 orthogonal regions) and over 50 events. It works very well and as expected, except for this one issue. Every once in a while, and in a way I've been unable to consistently repeat, I get an assertion failure resulting in a core dump. /usr/include/boost/statechart/state_machine.hpp:873: boost::statechart::detail::reaction_result boost::statechart::state_machine<MostDerived, InitialState, Allocator, ExceptionTranslator>::send_event(const event_base_type&) [with MostDerived = GripperPosition, InitialState = Container, Allocator = std::allocator<void>, ExceptionTranslator = boost::statechart::null_exception_translator, boost::statechart::state_machine<MostDerived, InitialState, Allocator, ExceptionTranslator>::event_base_type = boost::statechart::event_base]: Assertion `get_pointer( pOutermostUnstableState_ ) == 0' failed. "GripperPosition" is my state_machine. "Container" is the simple_state the state machine initially enters. Container has no transitions, but many sub states (it's the owner of the 9 orthogonal regions). (As far as I can tell, if the state machine is alive, then "Container" is an active state.) "Container" has a handful of custom_reactions that essentially listen for user-supplied events, "forward" those events in to the appropriate orthogonal regions using internal-only events, and then discard the user-supplied events. The intention here is to have a single event propagate to multiple orthogonal regions, allowing them all to react. For example: boost::statechart::result Container::react(const e_still&) { post_event(i_still_action()); post_event(i_still_moving()); return discard_event(); } I am unsure if these reactions are the cause of the assertion failure, but given that the error message says "Container" is the InitialState, I have to assume so. Given that, I don't see how either Container or GripperPosition are inactive and don't know how to interpret this error. I'd appreciate some guidance. I'm running Ubuntu 12.04, GCC 4.6.3, and Boost 1.46.1. -- Dustin Gooding NASA/JSC Robotics

4 7

[multiprecision] noexcept() usage in gmp int
by Francesco Biscani 16 Jun '13

16 Jun '13

Hello, I was trying out the new multiprecision library (kudos!), and I ran into a problem. In order to make certain guarantees in my code regarding exception safety, I am mandating that types being used in generic containers are marked noexcept() for certain basic operations (namely, destruction and move operations). It seems like this is generally guaranteed in the multiprecision library (tried with cpp_int and the mpfr adaptor), with the important exception of the gmp integer class. A glance at the headers reveals that (gmp.hpp): // // Within this file, the only functions we mark as noexcept are those that manipulate // (but don't create) an mpf_t. All other types may allocate at pretty much any time // via a user-supplied allocator, and therefore throw. // Additionally, browsing the gmp documentation yields this snippet ( http://gmplib.org/manual/Custom-Allocation.html) """ There's currently no defined way for the allocation functions to recover from an error such as out of memory, they must terminate program execution. A longjmp or throwing a C++ exception will have undefined results. This may change in the future. """ Would it be possible then for the mp library authors to consider adding basic noexcept() guarantees to the gmp adaptor class in future versions? Cheers and thanks for the great library, Francesco.

2 2

Building a large graph using Parallel Boost Graph Library
by William Shipman 15 Jun '13

15 Jun '13

Hi all, I'm working with a graph that has about 16 million vertices and 320 million edges. Currently, I'm using graph-tool in Python but building the graph is far too slow. Before I start porting to C++ I starting reading up on the Parallel Boost Graph Library. From the examples in the documentation, it seems that one must build the graph on one node in the cluster, then call synchronize to send that graph to all nodes. Is there a way to build parts of the graph on each node and then synchronize those parts? Some background: the graph actually comes from a CT scan. The vertices are voxels, the edges are relationships between adjacent voxels. At the moment I'm working on a very small test volume - 256^3 voxels - but later volumes will have billions of vertices and edges. Thanks for the help.

1 0

Regarding boost interval library package.
by Pranjal vyas 15 Jun '13

15 Jun '13

Hello, I have written a program in boost which simply calculates the exponent in an interval, but for some interval inputs it is giving the wrong output such as for [1,3] or [-1,3]...but for some values it is giving correct o/p such as [1,9]. Please help in solving this query. The program is appended below.... ********************************************************************************************************************************************************* #include </boost/numeric/interval.hpp> #include <vector> #include <algorithm> #include <utility> #include <iostream> #include <iomanip> #include <math.h> using namespace boost; using namespace numeric; using namespace interval_lib; template<class T, class Policies> std::ostream &operator<<(std::ostream &os, const boost::numeric::interval<T, Policies> &x) { os << "[" << x.lower() << ", " << x.upper() << "]"; return os; } int main() { typedef interval<double,policies<save_state<rounded_transc_opp<double> >,checking_base<double> > > I; //typedef interval<double> I; I a(1,3.2); std::cout << exp(a) << std::endl; } ********************************************************************************************************************************************************** Thanks in Advance. Regards, PV

1 0

http://www.boost.org/doc/libs/1_53_0/libs/serialization/example/demo.cpp does not work properly when using polymorphic xml archive
by Fadhel 14 Jun '13

14 Jun '13

Hi all, I used http://www.boost.org/doc/libs/1_53_0/libs/serialization/example/demo.cpp file as a first introduction to boost serialization. I would like to use polymorphic archives with XML serilialization format (to avoid having the templatized version). I edited this example and run it. Writing the data has worked fine -- except for the base_class serialization which needed an nvp -- but reading it causes a memory/segmentation fault problem. The same error happens with a binary archive. Using a text archive works fine. I'm new to boost serialization and debugging the code did not help me a lot. Is there anything specific to the serialization of base classes or abstract classes with the polymorphic XML format which needs to be handled? Or is this related to the serialization of pointers to the base class. Thanks for your help. Best Regards, Fadhel BA Here is the code I'm using: ( I removed some comments to make the code shorter) /////////1/////////2/////////3/////////4/////////5/////////6/////////7/////////8 // demo.cpp #include <cstddef> // NULL #include <iomanip> #include <iostream> #include <fstream> #include <string> #include <boost/archive/polymorphic_iarchive.hpp> #include <boost/archive/polymorphic_oarchive.hpp> #include <boost/archive/polymorphic_xml_iarchive.hpp> #include <boost/archive/polymorphic_xml_oarchive.hpp> #include <boost/archive/polymorphic_binary_iarchive.hpp> #include <boost/archive/polymorphic_binary_oarchive.hpp> #include <boost/archive/polymorphic_text_iarchive.hpp> #include <boost/archive/polymorphic_text_oarchive.hpp> #include <boost/serialization/base_object.hpp> #include <boost/serialization/utility.hpp> #include <boost/serialization/list.hpp> #include <boost/serialization/assume_abstract.hpp> #include <boost/serialization/nvp.hpp> ///////////////////////////////////////////////////////////// // gps coordinate // // llustrates serialization for a simple type // class gps_position { friend std::ostream & operator<<(std::ostream &os, const gps_position &gp); friend class boost::serialization::access; int degrees; int minutes; float seconds; void serialize(boost::archive::polymorphic_oarchive &ar, const unsigned int /* file_version */) const { ar << BOOST_SERIALIZATION_NVP(degrees); ar << BOOST_SERIALIZATION_NVP(minutes); ar << BOOST_SERIALIZATION_NVP(seconds); } void serialize(boost::archive::polymorphic_iarchive &ar, const unsigned int /* file_version */) { ar >> BOOST_SERIALIZATION_NVP(degrees); ar >> BOOST_SERIALIZATION_NVP(minutes); ar >> BOOST_SERIALIZATION_NVP(seconds); } public: // every serializable class needs a constructor gps_position(){}; gps_position(int _d, int _m, float _s) : degrees(_d), minutes(_m), seconds(_s) {} }; std::ostream & operator<<(std::ostream &os, const gps_position &gp) { return os << ' ' << gp.degrees << (unsigned char)186 << gp.minutes << '\'' << gp.seconds << '"'; } ///////////////////////////////////////////////////////////// // One bus stop // // illustrates serialization of serializable members // class bus_stop { friend class boost::serialization::access; friend std::ostream & operator<<(std::ostream &os, const bus_stop &gp); virtual std::string description() const = 0; gps_position latitude; gps_position longitude; void serialize(boost::archive::polymorphic_oarchive &ar, const unsigned int version) const { ar << BOOST_SERIALIZATION_NVP(latitude); ar << BOOST_SERIALIZATION_NVP(longitude); } void serialize(boost::archive::polymorphic_iarchive &ar, const unsigned int version) { ar >> BOOST_SERIALIZATION_NVP(latitude); ar >> BOOST_SERIALIZATION_NVP(longitude); } protected: bus_stop(const gps_position & _lat, const gps_position & _long) : latitude(_lat), longitude(_long) {} public: bus_stop(){} virtual ~bus_stop(){} }; BOOST_SERIALIZATION_ASSUME_ABSTRACT(bus_stop) std::ostream & operator<<(std::ostream &os, const bus_stop &bs) { return os << bs.latitude << bs.longitude << ' ' << bs.description(); } ///////////////////////////////////////////////////////////// // Several kinds of bus stops // // illustrates serialization of derived types // class bus_stop_corner : public bus_stop { friend class boost::serialization::access; std::string street1; std::string street2; virtual std::string description() const { return street1 + " and " + street2; } void serialize(boost::archive::polymorphic_oarchive &ar, const unsigned int version) const { // save/load base class information ar << boost::serialization::make_nvp("base", boost::serialization::base_object<bus_stop>(*this)); ar << BOOST_SERIALIZATION_NVP(street1); ar << BOOST_SERIALIZATION_NVP(street2);; } void serialize(boost::archive::polymorphic_iarchive &ar, const unsigned int version) { // save/load base class information ar >> boost::serialization::make_nvp("base", boost::serialization::base_object<bus_stop>(*this)); ar >> BOOST_SERIALIZATION_NVP(street1); ar >> BOOST_SERIALIZATION_NVP(street2); } public: bus_stop_corner(){} bus_stop_corner(const gps_position & _lat, const gps_position & _long, const std::string & _s1, const std::string & _s2 ) : bus_stop(_lat, _long), street1(_s1), street2(_s2) { } }; class bus_stop_destination : public bus_stop { friend class boost::serialization::access; std::string name; virtual std::string description() const { return name; } void serialize(boost::archive::polymorphic_oarchive &ar, const unsigned int version) const { ar << boost::serialization::make_nvp("base", boost::serialization::base_object<bus_stop>(*this)); ar << BOOST_SERIALIZATION_NVP(name); } void serialize(boost::archive::polymorphic_iarchive &ar, const unsigned int version) { ar >> boost::serialization::make_nvp("base", boost::serialization::base_object<bus_stop>(*this)); ar >> BOOST_SERIALIZATION_NVP(name); } public: bus_stop_destination(){} bus_stop_destination( const gps_position & _lat, const gps_position & _long, const std::string & _name ) : bus_stop(_lat, _long), name(_name) { } }; ///////////////////////////////////////////////////////////// // a bus route is a collection of bus stops // // illustrates serialization of STL collection templates. // // illustrates serialzation of polymorphic pointer (bus stop *); // class bus_route { friend class boost::serialization::access; friend std::ostream & operator<<(std::ostream &os, const bus_route &br); typedef bus_stop * bus_stop_pointer; std::list<bus_stop_pointer> stops; void serialize(boost::archive::polymorphic_oarchive &ar, const unsigned int version) const { // in this program, these classes are never serialized directly but rather // through a pointer to the base class bus_stop. So we need a way to be // sure that the archive contains information about these derived classes. //ar.template register_type<bus_stop_corner>(); ar.register_type(static_cast<bus_stop_corner *>(NULL)); //ar.template register_type<bus_stop_destination>(); ar.register_type(static_cast<bus_stop_destination *>(NULL)); // serialization of stl collections is already defined // in the header ar << BOOST_SERIALIZATION_NVP(stops); } void serialize(boost::archive::polymorphic_iarchive &ar, const unsigned int version) { ar.register_type(static_cast<bus_stop_corner *>(NULL)); ar.register_type(static_cast<bus_stop_destination *>(NULL)); // in the header ar >> BOOST_SERIALIZATION_NVP(stops); } public: bus_route(){} void append(bus_stop *_bs) { stops.insert(stops.end(), _bs); } }; std::ostream & operator<<(std::ostream &os, const bus_route &br) { std::list<bus_stop *>::const_iterator it; // note: we're displaying the pointer to permit verification // that duplicated pointers are properly restored. for(it = br.stops.begin(); it != br.stops.end(); it++){ os << '\n' << std::hex << "0x" << *it << std::dec << ' ' << **it; } return os; } ///////////////////////////////////////////////////////////// // a bus schedule is a collection of routes each with a starting time class bus_schedule { public: // note: this structure was made public. because the friend declarations // didn't seem to work as expected. struct trip_info { void serialize(boost::archive::polymorphic_oarchive &ar, const unsigned int file_version) const { // in versions 2 or later if(file_version >= 2) // read the drivers name ar << BOOST_SERIALIZATION_NVP(driver); // all versions have the follwing info ar << BOOST_SERIALIZATION_NVP(hour); ar << BOOST_SERIALIZATION_NVP(minute); } void serialize(boost::archive::polymorphic_iarchive &ar, const unsigned int file_version) { // in versions 2 or later if(file_version >= 2) // read the drivers name ar >> BOOST_SERIALIZATION_NVP(driver); // all versions have the follwing info ar >> BOOST_SERIALIZATION_NVP(hour); ar >> BOOST_SERIALIZATION_NVP(minute); } // starting time int hour; int minute; // only after system shipped was the driver's name added to the class std::string driver; trip_info(){} trip_info(int _h, int _m, const std::string &_d) : hour(_h), minute(_m), driver(_d) {} }; private: friend class boost::serialization::access; friend std::ostream & operator<<(std::ostream &os, const bus_schedule &bs); friend std::ostream & operator<<(std::ostream &os, const bus_schedule::trip_info &ti); std::list<std::pair<trip_info, bus_route *> > schedule; void serialize(boost::archive::polymorphic_oarchive &ar, const unsigned int version) const { ar << BOOST_SERIALIZATION_NVP(schedule); } void serialize(boost::archive::polymorphic_iarchive &ar, const unsigned int version) { ar >> BOOST_SERIALIZATION_NVP(schedule); } public: void append(const std::string &_d, int _h, int _m, bus_route *_br) { schedule.insert(schedule.end(), std::make_pair(trip_info(_h, _m, _d), _br)); } bus_schedule(){} }; BOOST_CLASS_VERSION(bus_schedule, 2) std::ostream & operator<<(std::ostream &os, const bus_schedule::trip_info &ti) { return os << '\n' << ti.hour << ':' << ti.minute << ' ' << ti.driver << ' '; } std::ostream & operator<<(std::ostream &os, const bus_schedule &bs) { std::list<std::pair<bus_schedule::trip_info, bus_route *> >::const_iterator it; for(it = bs.schedule.begin(); it != bs.schedule.end(); it++){ os << it->first << *(it->second); } return os; } void save_schedule(const bus_schedule &s, const char * filename){ // make an archive std::ofstream ofs(filename); boost::archive::polymorphic_xml_oarchive oa(ofs); oa << s; } void restore_schedule(bus_schedule &s, const char * filename) { // open the archive std::ifstream ifs(filename); boost::archive::polymorphic_xml_iarchive ia(ifs); // restore the schedule from the archive ia >> s; } int main(int argc, char *argv[]) { // make the schedule bus_schedule original_schedule; // fill in the data // make a few stops bus_stop *bs0 = new bus_stop_corner( gps_position(34, 135, 52.560f), gps_position(134, 22, 78.30f), "24th Street", "10th Avenue" ); bus_stop *bs1 = new bus_stop_corner( gps_position(35, 137, 23.456f), gps_position(133, 35, 54.12f), "State street", "Cathedral Vista Lane" ); bus_stop *bs2 = new bus_stop_destination( gps_position(35, 136, 15.456f), gps_position(133, 32, 15.300f), "White House" ); bus_stop *bs3 = new bus_stop_destination( gps_position(35, 134, 48.789f), gps_position(133, 32, 16.230f), "Lincoln Memorial" ); // make a routes bus_route route0; route0.append(bs0); route0.append(bs1); route0.append(bs2); // add trips to schedule original_schedule.append("bob", 6, 24, &route0); original_schedule.append("bob", 9, 57, &route0); original_schedule.append("alice", 11, 02, &route0); // make aother routes bus_route route1; route1.append(bs3); route1.append(bs2); route1.append(bs1); // add trips to schedule original_schedule.append("ted", 7, 17, &route1); original_schedule.append("ted", 9, 38, &route1); original_schedule.append("alice", 11, 47, &route1); // display the complete schedule std::cout << "original schedule"; std::cout << original_schedule; std::string filename("C:/Dev/XML"); filename += "/demofile.xml"; // save the schedule save_schedule(original_schedule, filename.c_str()); // ... some time later // make a new schedule bus_schedule new_schedule; std::cout << "\n\nstarting restored schedule"; restore_schedule(new_schedule, filename.c_str()); // and display std::cout << "\nrestored schedule"; std::cout << new_schedule; // should be the same as the old one. (except for the pointer values) delete bs0; delete bs1; delete bs2; delete bs3; return 0; }

2 1

Boost 32-64
by Dave Dyer 14 Jun '13

14 Jun '13

This is sort of a final report to thank the list for several good pieces of advice. I'm just completing a project which uses boost libraries to assist a project which uses shared memory to communicate between a 64 bit process and a separate 32 bit Application. Trying to use the managed version of shared memory proved to be too unreliable. Doing so is advertized as "experimental" and it proved not ready for prime time. I succeeded by using only the very simplest, unmanaged versions of boost shared memory and managing my own memory, very carefully, to be sure the shared structures were identical on the 32 and 64 bit sides of the divide.

1 0

[unordered] order in container
by gast128 14 Jun '13

14 Jun '13

Hello all, although it's called 'unordered_set', it surprised me that an unordered container could have a different ordering although its contents are the same: void f() { boost::unordered_set<int> uset1; uset1.insert(10); uset1.insert(9); uset1.insert(8); boost::unordered_set<int> uset2; uset2.insert(8); uset2.insert(9); uset2.insert(10); //uset1: 8, 9, 10 //uset2: 10, 9, 8 bool b = uset1 == uset2; //ok, they are the same } Maybe it is somewhere in the documentation, otherwise maybe add a documentation note.

3 2

[accumulator] compiler error with quantil
by Philipp Kraus 14 Jun '13

14 Jun '13

Hello, I try to create a complex accumulator. I would like to use an accumulator for a box plot with the whisker data ( http://en.wikipedia.org/wiki/Box_plot ). My typedef shows at the momen like this: typedef boost::accumulators::accumulator_set<double, boost::accumulators::stats< boost::accumulators::tag::count, boost::accumulators::tag::sum, //boost::accumulators::tag::median, boost::accumulators::tag::mean, boost::accumulators::tag::variance, boost::accumulators::tag::min, boost::accumulators::tag::max, boost::accumulators::tag::extended_p_square > > Accumulator; I would like to create the 25% & 75% quantil and replace the median with the 50% quantil, so I have defined the ctor accumulator call like this: boost::array<double, 3> probs = {0.25, 0.5, 0.75}; m_times[p_name] = Accumulator( boost::accumulators::extended_p_square_probabilities = probs ); (the median is disabled and m_times is a std::map<std::string, Accumulator>). At this point I get a compiler errors: /Developer/opt/Boost/1.53.0/include/boost/accumulators/statistics/extended_p_square.hpp: In constructor 'boost::accumulators::impl::extended_p_square_impl<Sample>::extended_p_square_impl(const Args&) [with Args = boost::parameter::aux::arg_list<boost::parameter::aux::tagged_argument<boost::accumulators::tag::accumulator, boost::accumulators::accumulator_set<double, boost::accumulators::stats<boost::accumulators::tag::count, boost::accumulators::tag::sum, boost::accumulators::tag::mean, boost::accumulators::tag::variance, boost::accumulators::tag::min, boost::accumulators::tag::max, boost::accumulators::tag::extended_p_square, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na>, void> >, boost::parameter::aux::empty_arg_list>, Sample = double]': /Developer/opt/Boost/1.53.0/include/boost/accumulators/framework/depends_on.hpp:319: instantiated from 'boost::accumulators::detail::accumulator_wrapper<Accumulator, Feature>::accumulator_wrapper(const Args&) [with Args = boost::parameter::aux::arg_list<boost::parameter::aux::tagged_argument<boost::accumulators::tag::accumulator, boost::accumulators::accumulator_set<double, boost::accumulators::stats<boost::accumulators::tag::count, boost::accumulators::tag::sum, boost::accumulators::tag::mean, boost::accumulators::tag::variance, boost::accumulators::tag::min, boost::accumulators::tag::max, boost::accumulators::tag::extended_p_square, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na>, void> >, boost::parameter::aux::empty_arg_list>, Accumulator = boost::accumulators::impl::extended_p_square_impl<double>, Feature = boost::accumulators::tag::extended_p_square]' .... I need one accumulator for all the data. I'm using Boost 1.53. How can I create working code? Thanks for help Phil

2 3

Any debugging tips for Boost Interprocess shared memory crashes?
by Warren Postma 14 Jun '13

14 Jun '13

I am a newly humbled mediocre C++ programmer, who is completely unable to figure out why Boost interprocess shared memory classes frequently freeze or crash both at creation and deletion of the manager objects, both with the persistent and the windows-only non persistent versions of the classes. Do you ever debug things and it all just gets worse and worse the longer you try to fix it? http://stackoverflow.com/questions/17100597/does-boostinterprocesswindows-s… Today I am getting crashes in the boost shared memory manager object destructor, or deadlocks in WMI calls. It's in Boost 1.53, on Visual C++ 2008, and involves DLLs. I am unable to reproduce the insanity at a top level EXE demo, and I tried to build a exe-loads DLL1, which loads DLL2, which creates boost objects, which fail when you destroy them, but I am unable to extricate it from my project. So it could be one of the lovely compiler or linker or project settings in my Visual C++ project, something about Multithreaded Debug DLL and MFC and ATL and all the billion varieties of weird RTL and heap bugs that lurk in Visual C++ runtime libraries. I am not blaming boost, but I am at wits end here. I have about 80 hours into debugging this and it's only getting worse the more I look at it. After this I promise to go away, perhaps drink myself silly, and never ever again try to use C++ or boost. Or Windows. Because for all I know this could be a windows SxS issue with Visual Studio 2008 and its lovely assortment of DLLs and runtime SxS insanity. Warren

1 0

boost 1.49.0 on Redhat 5.2 link issues
by Stefan Schwarzer 13 Jun '13

13 Jun '13

Dear everybody, we need to backport boost 1.49.0 to Redhat 5.2. b2 ; b2 install --prefix=/usr/local succeeds and installs libraries and headers in /usr/local as requested (g++ 4.1.2-42, 32 bit PAE kernel). However, we have a problem even linking a mostly trivial example: #include <boost/filesystem.hpp> int main () { copy_file(boost::filesystem::path("atest"), boost::filesystem::path("btest")); } $ g++ testBoost.cpp -lboost_filesystem -lboost_system /tmp/cc10doAS.o: In function `boost::filesystem3::copy_file(boost::filesystem3::path const&, boost::filesystem3::path const&)': testBoost.cpp: (.text._ZN5boost11filesystem39copy_fileERKNS0_4pathES3_[boost::filesystem3::copy_file(boost::filesystem3::path const&, boost::filesystem3::path const&)]+0x24): undefined reference to `boost::filesystem3::detail::copy_file(boost::filesystem3::path const&, boost::filesystem3::path const&, boost::filesystem3::copy_option::enum_type, boost::system::error_code*)' collect2: ld returned 1 exit status The symbol is present in /usr/local/lib/libboost_filesystem and ldconfig does know about its location (see below). Also, trying to link statically or adding -pthread does not change the situation. We are desperate for advice... Roald and Stefan. $ nm -C /usr/local/lib/libboost_filesystem.so | grep 'boost::filesystem3::detail::copy_file' 00010ae0 T boost::filesystem3::detail::copy_file(boost::filesystem3::path const&, boost::filesystem3::path const&, boost::filesystem3::copy_option::enum_type, boost::system::error_code*) $ cat /etc/ld.so.conf include ld.so.conf.d/*.conf /usr/local/lib

2 2

boost::thread::attributes reference overload?
by Anthony Foiani 13 Jun '13

13 Jun '13

Greetings. I have a class that wraps a boost::thread object, and I would like to specify certain thread attributes at construction time. My first attempt looked basically like this: struct my_thread { static boost::thread::attributes getThreadAttr() { boost::thread::attributes attrs; attrs.set_stack_size( 256 * 1024 ); return attrs; } my_thread( Runnable func ) : thread_( getThreadAttr(), func ) {} boost::thread thread_; }; But that fails: g++ -std=c++0x -o thread-attr thread-attr.cpp \ -lboost_thread-mt -lboost_system -pthread ... /usr/include/boost/thread/detail/thread.hpp:191:9: note: \ template argument deduction/substitution failed: thread-attr.cpp:48:42: note: cannot convert ‘my_thread::getThreadAttr()()’ (type \ ‘boost::thread::attributes {aka boost::thread_attributes}’) to type ‘boost::thread::attributes& {aka boost::thread_attributes&}’ Replacing 'getThreadAttr' with a method that returns a non-const reference to internal static variables allows the program to compile and run successfully: static boost::thread::attributes & getThreadAttr() { static boost::thread::attributes attrs; static bool init = false; if ( ! init ) { attrs.set_stack_size( 256 * 1024 ); init = true; } return attrs; } The full program, with Linux compile lines, can be found at the bottom of this message and also at: http://foiani.home.dyndns.org/~tony/boost/thread-attr.cpp I did find a closely-related question on StackOverflow: http://stackoverflow.com/questions/13868619 Where Vicente replied (http://stackoverflow.com/a/13894968/784478) The needed overload template <class F, class Arg, class ...Args> thread(attributes const& attrs, F&& f, Arg&& arg, Args&&... args) is defined only if the compiler supports variadic templates and rvalue references. This could explain your problem. I guess the documentation could be improved to signal this clearly. Please could you create a Trac ticket to follow this issue? However, the compiler I'm using (g++ 4.7.2) has supported both of these features for years. According to this page: http://gcc.gnu.org/projects/cxx0x.html g++ has supported both of these features since 4.3. Josef_K (on freenode IRC #boost channel) was kind enough to try the sample code in their own environment, and they encountered the same errors on both g++ 4.8.1 and clang 3.4. The most likely explanation is that I'm doing something stupid. If anyone has the time to hit me with the clue-by-four, I would appreciate it. There is the possibility that Boost.Thread v4 fixes this (I'm on 1_51_0, which is Boost.Thread v3.0.1). I'd rather not try to transition libraries at this point, but if it has been fixed, confirmation would be welcome. For now, I'll most likely implement the "return reference to internal static" method in my project. It's a bit racy, but since I do all my thread creation through this one routine, I should be able to manage it. Anyway. I'm left feeling that there is a gap somewhere; whether it's in my understanding, in the older version of Boost.Threads, in compiler support / quirks, or elsewhere, I don't know. Regardless, thanks for the excellent library, and happy hacking! Best regards, Anthony Foiani Sample program follows: ======================================================================== // this should work: // g++ -std=c++0x -o thread-attr thread-attr.cpp -lboost_thread-mt -lboost_system -pthread // // this explodes: // g++ -std=c++0x -o thread-attr thread-attr.cpp -DRVALUE_REFERENCE_DOOM -lboost_thread-mt -lboost_system -pthread #include <iostream> #include <boost/function.hpp> #include <boost/thread.hpp> typedef boost::function< void ( void ) > Runnable; struct my_thread { #ifdef RVALUE_REFERENCE_DOOM // this doesn't work. static boost::thread::attributes getThreadAttr() { boost::thread::attributes attrs; attrs.set_stack_size( 256 * 1024 ); return attrs; } #else // this does work, but needs more structure before it can be // considered safe. static boost::thread::attributes & getThreadAttr() { static boost::thread::attributes attrs; static bool init = false; if ( ! init ) { attrs.set_stack_size( 256 * 1024 ); init = true; } return attrs; } #endif my_thread( Runnable func ) : thread_( getThreadAttr(), func ) {} void join() { thread_.join(); } boost::thread thread_; }; void foo() { std::cout << "foo!" << std::endl; } int main( int argc, char * argv [] ) { my_thread t( foo ); t.join(); return 0; }

2 1

Re: [Boost-users] [multi_index] emplace support
by Brian Wood 13 Jun '13

13 Jun '13

> The sad reality is I have very limited time to devote to evolving the > library, so this thing, although in principle simple to implement, has > been procrastinated for years now. Maybe if you sketch the first step that needs to be done here on the list someone will do that and then you can repeat for each step. Whoever would be willing to do this should ask the questions they have here, because there are a number of others on this list who can answer at least some of the questions. A tip to someone willing to do this: Boost Container has emplace support: http://www.boost.org/doc/libs/1_53_0/doc/html/container/move_emplace.html#c… so studying that implementation might be helpful. -- Brian Wood Ebenezer Enterprises http://webEbenezer.net (651) 251-9384

1 0

Output libs to specified folder
by Christopher Pisz 12 Jun '13

12 Jun '13

How can I tell boost to put the libraries in a directory that I specify? If I change stage-dir, it still appends /lib onto it. Is this possible? I want my libraries in C:\trunk\third_party\ Not in C:\trunk\third_party\lib Here is my build script: cd ..\boost SET PATH=$(PATH);..\bjam bjam.exe --stagedir=../../third_party --with-thread toolset=msvc-9.0 link=static threading=multi runtime-link=shared variant=debug stage bjam.exe --stagedir=../../third_party --with-date_time toolset=msvc-9.0 link=static threading=multi runtime-link=shared variant=debug stage bjam.exe --stagedir=../../third_party --with-system toolset=msvc-9.0 link=static threading=multi runtime-link=shared variant=debug stage bjam.exe --stagedir=../../third_party --with-regex toolset=msvc-9.0 link=static threading=multi runtime-link=shared variant=debug stage bjam.exe --stagedir=../../third_party --with-program_options toolset=msvc-9.0 link=static threading=multi runtime-link=shared variant=debug stage bjam.exe --stagedir=../../third_party --with-filesystem toolset=msvc-9.0 link=static threading=multi runtime-link=shared variant=debug stage

1 0

[chrono] Initializing system_clock from microseconds
by Kelly, Dan 12 Jun '13

12 Jun '13

I have been having some difficulty initializing a chrono::system_clock::time_point object. Specifically, I am trying to load a time stamp from a .pcap file using libpcap. I have a structure, pcap_pkthdr, which contains two fields: struct timeval { long tv_sec; /* seconds */ long tv_usec; /* and microseconds */ }; struct pcap_pkthdr { struct timeval ts; /* time stamp */ bpf_u_int32 caplen; /* length of portion present */ bpf_u_int32 len; /* length this packet (off wire) */ }; Where tv_sec and tv_usec are seconds and microseconds respectively relative to an epoch of Jan 1, 1970. I can use system_clock::from_time_t() to initialize the time_point to an 64-bit integer seconds (std:time_t). The question is, how do I add the microseconds to this value? My latest attempt is: void my_class::calculate_packet_statistics( const struct pcap_pkthdr *header ) { frame_interval_.intervalTimeStamp_ = system_clock::from_time_t( static_cast<time_t>( header->ts.tv_sec ) ); frame_interval_.intervalTimeStamp_ += microseconds( header->ts.tv_usec ); // This is the problematic line ... } However, this appears to simply add tv_usec to the internal representation of the time_point. The internal representation appears to be in 100ns ticks with an epoch other than Jan 1, 1970. This is on a windows x64 build but the same code will have to work on Linux as well. As a side note, I later do some date calculations using system_clock::to_time_t. I lose my fractional seconds here But since I am only working with dates, this is not a problem. Dan Kelly dan.kelly(a)sig.com ________________________________ IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.

2 4

Question about the segfault in path::imbue that is being worked on at the moment
by Lars Hagström 12 Jun '13

12 Jun '13

Hi, I'm being bitten by the bug discussed here http://boost.2283326.n4.nabble.com/filesystem-segfault-in-path-imbue-after-… I'm encountering this when using boost 1.50. I have to support multiple boost versions, so I may bump into this in other versions as well. >From looking at the commit logs of boost svn I see that this is being worked on at the moment. But I would like to know what versions this bug affect, and if there are any ideas for a workaround. To me it looks like it affects most versions of boost filesystem, and I have been unable to come up with a workaround other than removing all use of filesystem in any place that could be called before main() has started. I would really like not having to do that! We use it quite a lot during static initialization... I've tried calling imbue(...) and codecvt() manually before using path, but that doesnt really help. The path_locale is in an anonymous namespace, which stops me from initializing it myself... Any other ideas? Sincerely Lars

1 0

[Interprocess] Interest in a NamedPipe component
by Geoff Shannon 11 Jun '13

11 Jun '13

Hey all, I'm in the early stages of planning an independent study for my CS program and what I'm hoping to do is write a Boost.Interprocess compatible implementation of NamedPipe. However, I don't want what I create to be too closely tied to what I personally want to use. So, if you have any possible interest in utilizing such a feature, please respond and we can chat a bit about what the desirable semantics might be. Specifically I'm interested in comments on what kind of persistence people would lke, and thoughts about whether the stream should be message oriented or not (or optionally so). (see http://www.boost.org/doc/libs/1_53_0/doc/html/interprocess/some_basic_expla… for more info about what I mean by persistence). Right now, my conception of what the key features of a NamedPipe implementation would be is a stream/message oriented communication channel between to unrelated processes. thanks! -- Geoff Nothing is ever easy.

1 0

quantil
by Philipp Kraus 11 Jun '13

11 Jun '13

Hello, I would like to create a box plot and use the static calls of the boost. Median / average etc works well, but I need also the 25% & 75% quantil of my data, I'm using a boost::accumulators::accumulator_set for calculating statistical data. Can I / How can I use this for the quantil calculation or should I do this myself? Thanks Phil

3 9

asio 1.43 ssl client certificate failure
by Stephan Menzel 11 Jun '13

11 Jun '13

Hello all, I am struggling with a bit of an esoteric question and have been debugging for days now. Basically, I am outfitting an existing app with asio based ssl HTTPS. Clients will have to use client authentication. Have my own root CA that signs both client and server certs. Extensive debugging using OpenSSL's s_client and s_server tools shows that the certificate trust chain etc is OK. Server side works fine with browsers, requests client certificate from browsers and only allows access if present. Alas, I can't get the client side to work. in boost 1.43 asio did not yet have any verification callbacks but it does have this: m_ssl_context.set_options( asio::ssl::context::tlsv1_client | asio::ssl::context::default_workarounds ); m_ssl_context.set_verify_mode( asio::ssl::context::verify_peer ); m_ssl_context.load_verify_file( myrootca ); m_ssl_context.use_certificate_file( myclient_cert, asio::ssl::context::pem ); m_ssl_context.use_private_key_file( myclient_key, asio::ssl::context::pem ); When I debug this using openssl s_server I see the connection failing with this message: ... SSL_accept:SSLv3 write certificate request A SSL_accept:SSLv3 flush data read from -0x7ff81be0 [-0x7ff8e2dd] (5 bytes => 5 (0x5)) 0000 - 16 03 01 00 07 ..... read from -0x7ff81be0 [-0x7ff8e2d8] (7 bytes => 7 (0x7)) 0000 - 0b 00 00 03 .... 0007 - <SPACES/NULS> write to -0x7ff81be0 [-0x7ff77a80] (7 bytes => 7 (0x7)) 0000 - 15 03 01 00 02 02 28 ......( SSL3 alert write:fatal:handshake failure SSL_accept:error in SSLv3 read client certificate B 2675716:error:140890C7:SSL routines:SSL3_GET_CLIENT_CERTIFICATE:peer did not return a certificate:s3_srvr.c:3274: ACCEPT A s_client or browser with the exact same keys can connect. Only asio fails and only on the client. Debugging shows that the client won't send the requested SSL certificates to the server. Also, when I register a verification callback in the impl like that: SSL_CTX *ctx = m_ssl_context.impl(); SSL *ssl = m_ssl_socket.impl()->ssl; SSL_CTX_set_client_cert_cb(ctx, &client_certificate_callback); and always return 1 in the callback, it still fails. Unfortunately I cannot upgrade to a post-war boost version and cannot touch OpenSSL either. It is on Windows here and uses OpenSSL 0.9.8i as far as I can see. Am I screwed? Or does anyone have an idea? Much appreciated? Stephan

2 2

[program_options] Can I use shorthand options with more than one char?
by Stefan Köhnen 10 Jun '13

10 Jun '13

Hello, I am currently migrating an old application with some weird command-line arguments. While using Boost program_options, I try to keep some of those arguments from the old version of the application, to assure the compatibility of some user scripts. My problem is that I couldn't find a way to add shorthand options with two or more characters. For example, if I add: ("testOption,to", "This is just a test-option") to the options_description, I only get -t as the shorthand for testOption. Is there some way to use longer shorthand options? Greetings, Stefan Köhnen

1 0

[thread] synchronized_value: value and move semantics
by Vicente J. Botet Escriba 08 Jun '13

08 Jun '13

Hi, boost::synchronized_value (not released yet [1][2][3]) is based on [4]. See below part of this paper adapted to the Boost.Thread interface. Currently boost::synchronized_value is in addition Copyable and Swappable. I was wondering if it is worth adding value and move semantics to synchronized_value. Making it EqualityComparable, LessThanComparable and Movable if the underlying type satisfy these requirements will allow to store them on a Boost.Container/C++11 container. Do you see something completely wrong with this addition? Has some of you had a need for this? Could you share the context? Best, Vicente [1] https://svn.boost.org/svn/boost/trunk/boost/thread/synchronized_value.hpp [2] https://svn.boost.org/svn/boost/trunk/libs/thread/example/synchronized_valu… [3] https://svn.boost.org/svn/boost/trunk/libs/thread/example/synchronized_pers… [4] "Enforcing Correct Mutex Usage with Synchronized Values" by Anthony Williams http://www.drdobbs.com/cpp/enforcing-correct-mutex-usage-with-synch/2252002… ------------- [section The Problem with Mutexes] The key problem with protecting shared data with a mutex is that there is no easy way to associate the mutex with the data. It is thus relatively easy to accidentally write code that fails to lock the right mutex - or even locks the wrong mutex - and the compiler will not help you. std::mutex m1; int value1; std::mutex m2; int value2; int readValue1() { boost::lock_guard<boost::mutex> lk(m1); return value1; } int readValue2() { boost::lock_guard<boost::mutex> lk(m1); // oops: wrong mutex return value2; } Moreover, managing the mutex lock also clutters the source code, making it harder to see what is really going on. The use of synchronized_value solves both these problems - the mutex is intimately tied to the value, so you cannot access it without a lock, and yet access semantics are still straightforward. For simple accesses, synchronized_value behaves like a pointer-to-T; for example: boost::synchronized_value<std::string> value3; std::string readValue3() { return *value3; } void setValue3(std::string const& newVal) { *value3=newVal; } void appendToValue3(std::string const& extra) { value3->append(extra); } Both forms of pointer dereference return a proxy object rather than a real reference, to ensure that the lock on the mutex is held across the assignment or method call, but this is transparent to the user. [endsect] [/The Problem with Mutexes] [section Beyond Simple Accesses] The pointer-like semantics work very well for simple accesses such as assignment and calls to member functions. However, sometimes you need to perform an operation that requires multiple accesses under protection of the same lock, and that's what the synchronize() method provides. By calling synchronize() you obtain an strict_lock_ptr object that holds a lock on the mutex protecting the data, and which can be used to access the protected data. The lock is held until the strict_lock_ptr object is destroyed, so you can safely perform multi-part operations. The strict_lock_ptr object also acts as a pointer-to-T, just like synchronized_value does, but this time the lock is already held. For example, the following function adds a trailing slash to a path held in a synchronized_value. The use of the strict_lock_ptr object ensures that the string hasn't changed in between the query and the update. void addTrailingSlashIfMissing(boost::synchronized_value<std::string> & path) { boost::strict_lock_ptr<std::string> u=path.synchronize(); if(u->empty() || (*u->rbegin()!='/')) { *u+='/'; } } [endsect] [/Beyond Simple Accesses] [section Operations Across Multiple Objects] Though synchronized_value works very well for protecting a single object of type T, nothing that we've seen so far solves the problem of operations that require atomic access to multiple objects unless those objects can be combined within a single structure protected by a single mutex. One way to protect access to two synchronized_value objects is to construct a strict_lock_ptr for each object and use those to access the respective protected values; for instance: synchronized_value<std::queue<MessageType> > q1,q2; void transferMessage() { strict_lock_ptr<std::queue<MessageType> > u1 = q1.synchronize(); strict_lock_ptr<std::queue<MessageType> > u2 = q2.synchronize(); if(!u1->empty()) { u2->push_back(u1->front()); u1->pop_front(); } } This works well in some scenarios, but not all - if the same two objects are updated together in different sections of code then you need to take care to ensure that the strict_lock_ptr objects are constructed in the same sequence in all cases, otherwise you have the potential for deadlock. This is just the same as when acquiring any two mutexes. In order to be able to use the dead-lock free lock algorithms we need to use instead unique_lock_ptr, which is Lockable. synchronized_value<std::queue<MessageType> > q1,q2; void transferMessage() { unique_lock_ptr<std::queue<MessageType> > u1 = q1.unique_synchronize(boost::defer_lock); unique_lock_ptr<std::queue<MessageType> > u2 = q2.unique_synchronize(boost::defer_lock); boost::lock(u1,u2); // dead-lock free algorithm if(!u1->empty()) { u2->push_back(u1->front()); u1->pop_front(); } } [endsect] [/Operations Across Multiple Objects]

2 4

[spirit] Compile error when using qi::locals<>
by Simon 07 Jun '13

07 Jun '13

Hi there, I'm pretty new to spirit and I need a semantic action to construct an object (that's fine) using a vector<double>, the vector is the problem. I'd really appreciate help with this error, or perhaps I'm not using the right technique, in which case, I'd need suggestions on how to proceed. Even if I don't use it anywhere, just adding the following to my grammar base class template parameter and adding the same to the rule declaration I need it for, it gives the monster error below. boost::spirit::qi::locals<std::vector<hs::Language::AX*> > I've also tried to make the vector a pointer, and allocate it on the first semantic action of a sequence. I've searched for an answer but found only one remote reference to boost needing to be recompiled to use c++11 features. So I did, but it didn't change anything (I use boost-1.49.0-r2). Also, I'm not sure if that is right, but my gcc command has this parameter: -std=c++0x I've put the full compile output at this address: http://next.n32.ca/locals.error.txt I will forget it there, so it should still be available in a few weeks/months... ;) And here are a few extracts of just the error lines: /usr/include/boost/spirit/home/qi/nonterminal/grammar.hpp:75:13: error: no matching function for call to 'assertion_failed(mpl_::failed************ (boost::spirit::qi::grammar<Iterator, T1, T2, T3, T4>::grammar(const boost::spirit::qi::rule<Iterator_, T1_, T2_, T3_, T4_>&, const string&) [with Iterator_ = __gnu_cxx::__normal_iterator<const char*, std::basic_string<char> >, T1_ = hs::Language::AX*(), T2_ = boost::spirit::unused_type, T3_ = boost::spirit::unused_type, T4_ = boost::spirit::unused_type, Iterator = __gnu_cxx::__normal_iterator<const char*, std::basic_string<char> >, T1 = hs::Language::AX*(), T2 = boost::spirit::locals<std::vector<hs::Language::AX*>*>, T3 = boost::spirit::unused_type, T4 = boost::spirit::unused_type, std::string = std::basic_string<char>]::incompatible_start_rule::************)(boost::spirit::qi::rule<__gnu_cxx::__normal_iterator<const char*, std::basic_string<char> >, hs::Language::AX*(), boost::spirit::unused_type, boost::spirit::unused_type, boost::spirit::unused_type>))' /usr/include/boost/proto/extends.hpp:537:29: error: use of deleted function 'boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::spirit::qi::reference<const boost::spirit::qi::rule<__gnu_cxx::__normal_iterator<const char*, std::basic_string<char> >, hs::Language::AX*(), boost::spirit::locals<std::vector<hs::Language::AX*>*>, boost::spirit::unused_type, boost::spirit::unused_type> > >, 0l>::expr()' /usr/include/boost/proto/detail/preprocessed/expr_variadic.hpp:37:12: error: 'boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::spirit::qi::reference<const boost::spirit::qi::rule<__gnu_cxx::__normal_iterator<const char*, std::basic_string<char> >, hs::Language::AX*(), boost::spirit::locals<std::vector<hs::Language::AX*>*>, boost::spirit::unused_type, boost::spirit::unused_type> > >, 0l>::expr()' is implicitly deleted because the default definition would be ill-formed: /usr/include/boost/proto/detail/preprocessed/expr_variadic.hpp:37:12: error: no matching function for call to 'boost::spirit::qi::reference<const boost::spirit::qi::rule<__gnu_cxx::__normal_iterator<const char*, std::basic_string<char> >, hs::Language::AX*(), boost::spirit::locals<std::vector<hs::Language::AX*>*>, boost::spirit::unused_type, boost::spirit::unused_type> >::reference()'

3 5

Using boost with 'c' level interfaces ?
by avib369 . 07 Jun '13

07 Jun '13

I can not find any solution where a 'c' api can update/modify a std::vector Passing a std::vector<int>/std::vector<double> to a 'c' or fortran api function, that _reads_, works like a charm. However we are out of luck, if we need the 'c' api, to populate the array. When passing a std::vector will 'kind of' work. But you can never use any of the following // 1/ size() // 2/ empty() // 3/ begin()/ end()/ rbegin()/rend() // 4/ push_back() // 5/ pop_back() You have to separately carry the size of the vector, in order to use it. You then just end up using it like a 'c' array. I thought there may have been way of updating the vectors begin/finish after the api call. But there does not appear to any way to do this. One solution would be to use 'c' array when calling the interface, and then copy to a std::vector. However this would degrade performance, when dealing large data sets. Is there any boost libraries/containers that are applicable or that can handle this issue ? It must have similar properties to a vector, like contiguous memory ? I have included a sample program below, to demonstrate. Before resorting back to 'c' array I was wondering if any one else has come across this problem ? Ta, Avi ============================================================= #include <vector> #include <string> #include <string.h> // memcopy #include <stdlib.h> // malloc #include <iostream> #include <ostream> using namespace std; void c_function_that_reads(int* array, int size_of_array) { for(int i = 0; i < size_of_array; i++) cout << array[i] << ","; cout << "\n"; } void c_function_that_writes(int* array, int size_of_array) { for(int i = 0; i < size_of_array; i++) array[i] = i; } int main(){ { cout << "\ncalling c_function_that_reads\n"; vector<int> dataVec; dataVec.push_back(1); dataVec.push_back(22); c_function_that_reads(&dataVec[0],dataVec.size()); } { cout << "\ncalling c_function_that_writes\n"; int the_size = 10; int* int_array = (int*)malloc(the_size*sizeof(int)); c_function_that_writes(int_array,the_size); // Copy into vector. vector<int> dataVec; dataVec.insert(dataVec.end(), &int_array[0], &int_array[the_size]); for(size_t i = 0; i < dataVec.size(); i++) { cout << dataVec[i] << ","; } cout << "\n"; free(int_array); } { cout << "\ncalling c_function_that_writes\n"; int the_size = 10; vector<int> dataVec; dataVec.reserve(the_size); c_function_that_writes(&dataVec[0],the_size); cout << "dataVec.size() = " << dataVec.size() << ", dataVec.capacity() = " << dataVec.capacity() << " dataVec.empty() = " << dataVec.empty() << "\n"; cout << "for(size_t i = 0; i < dataVec.size(); i++): BROKEN\n"; for(size_t i = 0; i < dataVec.size(); i++) { cout << dataVec[i] << ","; } cout << "\n"; cout << "for(size_t i = 0; i < the_size; i++): WORKS\n"; for(int i = 0; i < the_size; i++) { cout << dataVec[i] << ","; } cout << "\n\n"; cout << "for(vector<int>::iterator i = dataVec.begin(); i != dataVec.end(); i++): BROKEN\n"; for(vector<int>::iterator i = dataVec.begin(); i != dataVec.end(); i++) { cout << (*i) << ","; } cout << "\n"; dataVec.push_back(11); the_size += 1; // dataVec.pop_back(); the_size -= 1; // also broken cout << "for(size_t i = 0; i < dataVec.size(); i++): BROKEN\n"; for(size_t i = 0; i < dataVec.size(); i++) { cout << dataVec[i] << ","; } cout << "\n"; cout << "for(size_t i = 0; i < the_size; i++): BROKEN\n"; for(int i = 0; i < the_size; i++) { cout << dataVec[i] << ","; } cout << "\n\n"; cout << "for(vector<int>::iterator i = dataVec.begin(); i != dataVec.end(); i++): BROKEN\n"; for(vector<int>::iterator i = dataVec.begin(); i != dataVec.end(); i++) { cout << (*i) << ","; } cout << "\n"; // Using std::vector is ok for read only access when calling a c api function // *however* Using a c/fortrans api to *populate* a std::vector leads to issues: // // The following will not work after the api call. // 1/ size() // 2/ empty() // 3/ begin()/ end()/ rbegin()/rend() // 4/ push_back() // 5/ pop_back() // 6/ will ~vector() work since that use begin()/end() ?? // Is it worth using std::vector, since many of invariants are broken ???? // We have to carry the length separately } }

3 2

All talks for Meeting C++ 2013 are online!
by Jens Weller 06 Jun '13

06 Jun '13

1 0

Re: [Boost-users] [1.54.0] Beta 1 Available
by Cromwell Enage 06 Jun '13

06 Jun '13

Hi, all. When calling the merge() member function of a boost::heap::d_ary_heap, is the heap passed in not supposed to be emptied? Here's my test program: ['' #include <boost/heap/d_ary_heap.hpp> #include <boost/heap/binomial_heap.hpp> #include <boost/heap/fibonacci_heap.hpp> #include <boost/heap/pairing_heap.hpp> #include <boost/heap/skew_heap.hpp> #include <boost/test/minimal.hpp> template <typename Heap> void test_heap_merge_memfun() { Heap heap_1, heap_2; heap_1.push(3); heap_1.push(5); heap_1.push(1); heap_2.push(2); heap_2.push(4); heap_2.push(0); heap_1.merge(heap_2); std::cout << " heap_2"; if (!heap_2.empty()) { BOOST_CHECK(4 == heap_2.top()); heap_2.pop(); BOOST_CHECK(2 == heap_2.top()); heap_2.pop(); BOOST_CHECK(0 == heap_2.top()); heap_2.pop(); std::cout << " not"; } std::cout << " emptied." << std::endl; BOOST_CHECK(heap_2.empty()); BOOST_CHECK(5 == heap_1.top()); heap_1.pop(); BOOST_CHECK(4 == heap_1.top()); heap_1.pop(); BOOST_CHECK(3 == heap_1.top()); heap_1.pop(); BOOST_CHECK(2 == heap_1.top()); heap_1.pop(); BOOST_CHECK(1 == heap_1.top()); heap_1.pop(); BOOST_CHECK(0 == heap_1.top()); heap_1.pop(); BOOST_CHECK(heap_1.empty()); } int test_main(int argc, char** argv) { test_heap_merge_memfun< boost::heap::d_ary_heap< int , boost::heap::arity<4> , boost::heap::mutable_<true> > >(); test_heap_merge_memfun<boost::heap::binomial_heap<int> >(); test_heap_merge_memfun<boost::heap::fibonacci_heap<int> >(); test_heap_merge_memfun<boost::heap::pairing_heap<int> >(); test_heap_merge_memfun< boost::heap::skew_heap<int,boost::heap::mutable_<true> > >(); return 0; } ''] When I run this program, I see that all the other heap types empty the heap passed in. I use gcc 4.2.1 with Apple clang version 4.0 on MacOSX 10.8 Cromwell D. Enage

1 0

[Iostreams] Safely returning filtering_istream from function
by Szymon Gatner 06 Jun '13

06 Jun '13

Hi, I would like to return filtering_istream via std::unique_ptr<std::iostream> so that client code can just use iostream interface without knowing what is actual stream type. Inside the factory function filtering_istream is prepared with possible filters attached. Problem is filters are attached by reference. My question is: how to elegantly attach filters to a filtering_istream so that they live as long as filtering_istream itself? How to attach a filter via shared_ptr for example? Regards, Szymon Gatner

2 3

Trouble with posix_time
by Davies, John 06 Jun '13

06 Jun '13

I'm trying to time part of my program and coming up with something I can't explain. I don't expect great accuracy with the sample code here. But I'd like to understand what is happening. static boost::posix_time::ptime MillisecondsFromNow(int milliseconds) { return(boost::posix_time::ptime(boost::posix_time::second_clock::universal_time()) + boost::posix_time::milliseconds(milliseconds)); } Code segment: nanosecond_type const twenty_seconds(20 * 1000000000LL); cpu_timer timer; long count = 0; while(true) { boost::thread::sleep(MillisecondsFromNow(1000)); cpu_times const elapsed_times(timer.elapsed()); nanosecond_type const elapsed(elapsed_times.wall); if (elapsed >= twenty_seconds) { break; } count++; } std::cout << count << '\n'; So I'm running for 20 seconds and delaying each time for a second. So I would expect to get output of 19, maybe 20 or 18. Instead I'm getting around 38-40 I've tried .system and .user and get different values. But never something close to 20. This is on Windows. ___________________________________ John Davies Contractor Home Respiratory Care Philips Home Healthcare Solutions 1740 Golden Mile Highway Monroeville, PA 15146 Email: john.davies(a)philips.com Fax: 724-387-4109 ________________________________ The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.

2 1

[DNS] Heads up: svn.boost.org moving to a new server; IP address changing
by Beman Dawes 05 Jun '13

05 Jun '13

At 2:00 pm Eastern US time (i.e 30 minutes from now) we will switch svn.boost.org to a new server with a new IP address. It would be best to hold off on any SVN commits until after the change over, and after your DNS server has the new IP address. If command line "ping svn.boost.org" is going to [129.79.245.252], you are still getting the old IP address. Once svn.boost.org is resolving to [129.79.13.13] it should be OK to resume normal Subversion activity. Thanks, --Beman

1 2

[iostreams] C++ 11 moving semantics
by Ovanes Markarian 05 Jun '13

05 Jun '13

Hello *, I am wondering if latest boost iostreams implementation (1.53) supports C++ 11 moving semantics. I would like to create a tee_device and related stream in a separate function and hide the complexity from the user and just return a stream object which moved out of the function. Any ideas how to do that, without using heap and returning smart pointers? Thanks for your help, Ovanes

1 0

[program_options] Config file and/or response file
by Michael Powell 05 Jun '13

05 Jun '13

Hello, Couple of questions about program options config file (and/or response file). I've got an options set that is starting to get fairly verbose, it's rich, but is also impractical to expect users to type that many options. So I would like to capture some (or all) of those options in one or more different config files, depending on the options that need to be set for a given session. With config files, can the parse_config_file method build a vector of options? For instance if I define "value" as vector<int>, can I specify value=1, value=2, value=3 and expect {1,2,3}? Or does the convention go something like this, value=1 2 3, and so on? Next, how does the parse_config_file method treat boiler plate iterative sections? In other words, if I've got a pattern and would like to capture zero or more of that pattern: [pattern] name=test param=1 expected=2 actual=3 [pattern] name=result param=4 expected=5 actual=6 Those might inform a vector<pattern> type concern downstream of the parser. Possible? Third, in a response file, there is a statement about "limitations", which was left at that. Can we be more specific? What kind of limitations are we talking about? Obvious ones like the delimiters between tokens come to mind, but other than that, that's a nebulous statement at best. Thank you. Regards, Michael Powell

2 1

Nesting bind with shared_ptr<T>::operator* and ref
by Chris Stankevitz 04 Jun '13

04 Jun '13

Hello, Can you please help me uncomment out the last "bind" of the program pasted below? The problem is that it will require some kind of mechanism to dereference the shared_ptr. Thank you, Chris === #include <boost/bind.hpp> #include <boost/function.hpp> #include <boost/make_shared.hpp> #include <boost/shared_ptr.hpp> #include <boost/utility.hpp> using namespace boost; struct C : noncopyable { C() {} void f() {} }; shared_ptr<C> GetC(int) { return make_shared<C>(); } int main() { function<void(C&)> x = bind(&C::f, _1); function<void(shared_ptr<C>)> y = bind(&C::f, _1); // Call x after first computing 42, GetC, and shared_ptr::operator* x(*GetC(42)); // Same as above, but with bind and ref bind(x, ref(*GetC(42)))(); // Similar to above, but delay calling 42, GetC, shared_ptr::operator*, // and ref until later. Also use y (takes a shared_ptr) vs x (that takes // a reference) bind(y, bind(GetC, _1))(42); // Same as above, but use x vs y // todo: add call to operator* // todo: add call to ref // // bind(x, bind(GetC, _1))(42); return 0; }

2 3

[Spirit] Stack overflow, suspect infinite recursion
by Simon 03 Jun '13

03 Jun '13

Hi, I'm writing a math string parser with boost::spirit and I'm stuck on this stack overflow. I've seen this before when I wrote a rule that was misleading. It's the second time I get these and I'm really not sure how I can troubleshoot this kind of problem. Help would be greatly appreciated. I have no issues parsing the forms "A?B" (where A,B are floats and ? is an arithmetic operator +,-,*,/). No issues parsing "(A)" either... At the moment of writing this, I haven't tried but I will be trying to parse simpler forms like "(A)?B" and "A?(B)", "(A?B)", "(A?B)?C" and "A?(B?C)"... I suspect going through them will eventually help me fix the bug with the form below... Below is the final output of my program through valgrind and the rules I have are at the end of my post. I suspect the prob is in the definition for start, operation or operand (an operand may be the result of an operation and an operation is performed on operands). There may be a nasty infinite recursion between operand and operation... The resulting objects are polymorphic and they are correct (as seen when used without spirit). Simon Parsing operations such as ( A?B ) ? ( C?D ) Parsing: (0.1+1.9)+(4.2+6.1) -> (AB=2.000000, CD=10.300000, ABCD=12.300000) ==17013== Stack overflow in thread 1: can't grow stack to 0xb907cfbc ==17013== ==17013== Process terminating with default action of signal 11 (SIGSEGV) ==17013== Access not within mapped region at address 0xB907CFBC ==17013== at 0x13487A: bool boost::spirit::qi::action<boost::spirit::qi::reference<boost::spirit::qi::rule<__gnu_cxx::__normal_iterator<char const*, std::string>, std::string ()(), boost::spirit::unused_type, boost::spirit::unused_type, boost::spirit::unused_type> const>, boost::phoenix::actor<boost::phoenix::composite<boost::phoenix::assign_eval, boost::fusion::vector<boost::spirit::attribute<0>, boost::phoenix::composite<boost::phoenix::detail::new_eval<HS::Language::axIdentifier>, boost::fusion::vector<boost::spirit::argument<0>, boost::fusion::void_, boost::fusion::void_, boost::fusion::void_, boost::fusion::void_, boost::fusion::void_, boost::fusion::void_, boost::fusion::void_, boost::fusion::void_, boost::fusion::void_> >, boost::fusion::void_, boost::fusion::void_, boost::fusion::void_, boost::fusion::void_, boost::fusion::void_, boost::fusion::void_, boost::fusion::void_, boost::fusion::void_> > > >::parse<__gnu_cxx::__normal_iterator<char const*, std::string>, boost::spirit::context<boost::fusion::cons<HS::Language::axIdentifier*&, boost::fusion::nil>, boost::fusion::vector0<void> >, boost::spirit::unused_type, boost::spirit::unused_type const>(__gnu_cxx::__normal_iterator<char const*, std::string>&, __gnu_cxx::__normal_iterator<char const*, std::string> const&, boost::spirit::context<boost::fusion::cons<HS::Language::axIdentifier*&, boost::fusion::nil>, boost::fusion::vector0<void> >&, boost::spirit::unused_type const&, boost::spirit::unused_type const&) const (action.hpp:50) ==17013== If you believe this happened as a result of a stack ==17013== overflow in your program's main thread (unlikely but ==17013== possible), you can try to increase the size of the ==17013== main thread stack using the --main-stacksize= flag. ==17013== The main thread stack size used in this run was 96002048. ==17013== Stack overflow in thread 1: can't grow stack to 0xb907cfb8 ==17013== ==17013== Process terminating with default action of signal 11 (SIGSEGV) ==17013== Access not within mapped region at address 0xB907CFB8 ==17013== at 0x48224AC: _vgnU_freeres (vg_preloaded.c:58) ==17013== If you believe this happened as a result of a stack ==17013== overflow in your program's main thread (unlikely but ==17013== possible), you can try to increase the size of the ==17013== main thread stack using the --main-stacksize= flag. ==17013== The main thread stack size used in this run was 96002048. ==17013== ==17013== HEAP SUMMARY: ==17013== in use at exit: 410,754 bytes in 25,628 blocks ==17013== total heap usage: 25,847 allocs, 219 frees, 437,192 bytes allocated ==17013== ==17013== LEAK SUMMARY: ==17013== definitely lost: 409,080 bytes in 25,571 blocks ==17013== indirectly lost: 432 bytes in 27 blocks ==17013== possibly lost: 1,050 bytes in 20 blocks ==17013== still reachable: 192 bytes in 10 blocks ==17013== suppressed: 0 bytes in 0 blocks ==17013== Rerun with --leak-check=full to see details of leaked memory ==17013== ==17013== For counts of detected and suppressed errors, rerun with: -v ==17013== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) Segmentation fault Extract of the grammar: constnum = double_ [_val = new_<axConstant>(_1)]; alpha_numeric = alpha >> +(alnum); ident = alpha_numeric [_val = new_<axIdentifier>(_1)]; operand = ident | constnum | operation; addition = (operand >> lit('+') >> operand) [_val = new_<axAddition>(_1,_2)]; substraction = (operand >> lit('-') >> operand) [_val = new_<axSubstraction>(_1,_2)]; multiplication = (operand >> lit('*') >> operand) [_val = new_<axMultiplication>(_1,_2)]; division = (operand >> lit('/') >> operand) [_val = new_<axDivision>(_1,_2)]; precedence = (lit('(') >> operand >> lit(')')) [_val = new_<axPrecedence>(_1)]; operation = precedence | multiplication | division | addition | substraction; start = operation | operand; } boost::spirit::qi::rule<Iterator, AX*()> start; boost::spirit::qi::rule<Iterator, std::string()> alpha_numeric; boost::spirit::qi::rule<Iterator, axIdentifier*()> ident; boost::spirit::qi::rule<Iterator, axConstant*()> constnum; boost::spirit::qi::rule<Iterator, axOperand*()> operand; boost::spirit::qi::rule<Iterator, axOperation*()> operation; boost::spirit::qi::rule<Iterator, axAddition*()> addition; boost::spirit::qi::rule<Iterator, axSubstraction*()> substraction; boost::spirit::qi::rule<Iterator, axMultiplication*()> multiplication; boost::spirit::qi::rule<Iterator, axDivision*()> division; boost::spirit::qi::rule<Iterator, axPrecedence*()> precedence; };

2 2

Visual Studio Professional 2012
by Scott Alexander 03 Jun '13

03 Jun '13

Hi, Does Boost 1.51 support Visual Studio Professional 2012? I would like to use Boost 1.53 but the latest installer I can find is for 1.51 (from http://www.boostpro.com/download/) Where can I find and installer for the latest version? Thanks, Scott

3 2

Fwd: Compile error using BOOST_FUSION_DONT_USE_PREPROCESSED_FILES
by Fernando Gomes da Silva 03 Jun '13

03 Jun '13

Em quarta-feira, 29 de maio de 2013 17h11min09s UTC-3, Fernando Gomes da Silva escreveu: > > I'm having trouble setting the max template parameters for Boost Fusion > Tuples. > > I've read the source code and found that I can set > BOOST_FUSION_DONT_USE_PREPROCESSED_FILES and set FUSION_MAX_VECTOR_SIZE to > the given number. > > Using MSVC 2012 and using a value of 51, I get the following error: > > \boost_1_53_0\boost\fusion\container\vector\detail\vector_n_chooser.hpp(65): > error C2143: syntax error : missing ';' before '<' > \boost_1_53_0\boost\fusion\container\vector\detail\vector_n_chooser.hpp(66) > : see reference to class template instantiation > 'boost::fusion::detail::vector_n_chooser<T0,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21,T22,T23,T24,T25,T26,T27,T28,T29,T30,T31,T32,T33,T34,T35,T36,T37,T38,T39,T40,T41,T42,T43,T44,T45,T46,T47,T48,T49,T50>' > being compiled > \boost_1_53_0\boost\fusion\container\vector\detail\vector_n_chooser.hpp(65): > error C4430: missing type specifier - int assumed. Note: C++ does not > support default-int > \boost_1_53_0\boost\fusion\container\vector\detail\vector_n_chooser.hpp(65): > error C2238: unexpected token(s) preceding ';' > > Thank you for any inputs! > > Fernando >

1 0

Using boost from XCODE 4.6.1 - what are the proper build settings?
by B Hart 01 Jun '13

01 Jun '13

I downloaded boost 1.53 and extracted to Users/user/Desktop/boost_1_53_0 I built boost as static libraries following instructions at: http://libcinder.org/docs/v0.8.5/_cinder_boost.html I changed XCODE's "Build Settings" "Header Search Paths" to /Users/user/Desktop/boost_1_53_0 as well as the "Library Search Paths" to Users/user/Desktop/boost_1_53_0/stage/lib Then I build and get errors: The first error I'm getting is "has_binary_operator.hpp" Parse issue Expected member name or ';' after declaration specifiers at the line: template < typename Lhs, typename Rhs > struct operator_exists { ... Does anyone have tips for what the build settings should be? The project contains some files that are cocoa/objective C (.m) and others that are C++(.mm) using boost. I'm completely new to trying to use boost under OSX mountain lion and XCODE 4.6.1.

2 1

[mpl] Using max_element inside a fold while constructing a vector
by Brendon Costa 01 Jun '13

01 Jun '13

Hi, I have been using boost.mpl for the first time recently and have solved a number of tasks with boost.mpl now but have a problem with a bit of code I thought should be working. What is wrong with this bit of code using boost.mpl? typedef vector<int_<0>, int_<3>, int_<2> > v1; // I want to use max_element on a vector I am in the process of constructing using a fold typedef typename fold<v1, vector<int_<0> >, push_back<_1, deref<max_element<_1>::type >::type> >::type v2; // This code below compiles and runs fine to illustrate that max_element on a vector works, but is not what I am after. // I thought _1 in the max_element above would be a vector just as v1 below is, but the one below works and the one above does not. // typedef typename fold<v1, vector<int_<0> >, push_back<_1, deref<max_element<v1>::type >::type> >::type v2; I know this code is only going to create v2 like [0, 0, 0, 0] in this case but this is a smaller part of a larger expression that is failing and I cut it down to the minimum to show the problem at hand. In case it is useful I am using gcc 4.5.3 and boost 1.50

2 4

[Thread] Can't compile package_task code with 1.54
by Szymon Gatner 01 Jun '13

01 Jun '13

Hi, I just tried to compile my 1.52- based code with 1.54 beta and run into package_task compilation issue. In 1.52 I was using BOOST_THREAD_VERSION=3 define but with 1.54 I complied with =4. Test program: #define BOOST_THREAD_VERSION 4 #include <boost/thread/future.hpp> #include <boost/function.hpp> struct MyFunc { void operator()()const {} }; int main() { boost::function<void()> f; MyFunc mf; boost::packaged_task<void()> t1(f); // error 1 boost::packaged_task<void()> t2(mf); // error 2 } error 1 being: d:\devel\boost_1_54_0_beta1\boost\thread\future.hpp(2848): error C2664: 'boost::detail::task_object<F,R>::task_object(boost::detail::task_object<F,R> &)' : cannot convert parameter 1 from 'boost::function<Signature>' to 'boost::detail::task_object<F,R> &' and error 2 similarly: d:\devel\boost_1_54_0_beta1\boost\thread\future.hpp(2848): error C2664: 'boost::detail::task_object<F,R>::task_object(boost::detail::task_object<F,R> &)' : cannot convert parameter 1 from 'MyFunc' to 'boost::detail::task_object<F,R> &' (I tried with custom functor because I thought maybe error was related to boost function) Compiling with Visual Studio 2012 Update 3 Regards, Szymon Gatner

2 10

[1.54.0] Beta Release Candidates available
by Marshall Clow 01 Jun '13

01 Jun '13

Release candidate files for 1.54.0 beta 1 are available at http://boost.cowic.de/rc/ As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. This helps ensure the candidates build OK before we push them out to SourceForge. The files (and associated md5s) are: 31266b7dcc6f557ad839e4e87317cd6e *boost_1_54_0_beta1_rc1.tar.gz fbf7be9cbaf9ea6fb21ae73d0c17100d *boost_1_54_0_beta1_rc1.tar.bz2 7de4299ab69c941e83fe3fc46dddc15f *boost_1_54_0_beta1_rc1.zip c73e5118ff585d9f1d68542f96a0758a *boost_1_54_0_beta1_rc1.7z Thanks, --The release managers

4 5

[Xpressive] Nested patterns and sub-matches' semantic values
by Simon 30 May '13

30 May '13

Hi, For one part of a large project, I need to parse math and turn the "mathematical objects" into a C++ abstraction of them. Is it possible that a nested pattern hold semantic values within itself and can be queried for that value somehow? As if a match were a function of its sub-patterns' matches, if that makes sense... Code might speak better than my english: class math_number {...}; class math_addition {...}; class math_arglist {...}; class math_funcdef {...}; sregex integer = (s1= +_d) [ return math_number( as<int>(s1) ) ]; sregex addition = (s1= integer) >> '+' >> (s2= integer) [ return math_addition( as<math_number>(s1), as<math_number>(s2) ) ]; sregex arglist = (s1= identifier) >> *( ',' >> (s2= arglist)) [ std::vector<math_id> ids( as<math_arglist>(s2).begin(), as<math_arglist>(s2).end() ); ids.push_back(as<math_id>(s1)); return ids; ] sregex funcdef = ((s1= identifier) >> '(' >> (s2= arglist) >> ")=" >> (s3= addition)) [ return math_funcdef( as<math_id>(s1), as<math_arglist>(s2), as<math_addition>(s3) ) ]; I just want to avoid the funcdef above to be responsible for the construction of the various math_* objects the funcdef will hold (some of which will be complex to construct). And if I really must store the objects in an external stack, how should the parent-objects find their child-objects? Thanks, Simon

2 2

Confused with BGL-- Six Degrees of Kevin Bacon example
by lizy10b 30 May '13

30 May '13

Hi there, I am new to BGL library. I am walking through the online tutorial and just finished the "10.2. Six Degrees of Kevin Bacon". As it is said at the end of the example: "Note that vertex descriptor objects can not always be used as indices into vectors or arrays such as bacon_number. This is valid with the adjacency_list class with VertexList=vecS, but not with other variations of adjacency_list. A more generic way to index based on vertices is to use the ID property map (vertex_index_t) in coordination with the iterator_property_map.". So I turn to have a look at the iterator_property_map page and its sample. First, this sample uses VertexList=vecS too. Second, I know this sample is using iterator_property_map to build a property map, but I think the property is still indexed by the edge descriptor objects. So what is the difference? Thanks. Zhiyu LI 2013-05-29 lizy10b

2 5

[program options] parsing std::string
by Michael Powell 30 May '13

30 May '13

Hello, I want to parse std::string, perhaps into a vector<string>, but I do not want the command line argument to be positional in nature (i.e. like the examples demonstrate), because there may be a handful of parameters I need to capture into string or vector<string>. I've been able to parse integral types like int, even vector<int>, but haven't had much success with string. Possible or is this a program options "feature" and/or bug? Regards, Michael Powell

2 1

Does the Proactor of boost uses edge-triggered epoll on linux?
by Journeyer J. Joh 30 May '13

30 May '13

Hello list, I have some questions about boost's async IO implementation for linux. 1. Does it use edge-triggered epoll to implement the Proactor (in terms of Reactor)? http://www.boost.org/doc/libs/1_53_0/doc/html/boost_asio/overview/core/asyn… The guide above says that boost's Proactor is implemented in terms of Reactor when it comes to Linux. If it is based on Reactor, I guess it should be level-triggered epoll. 2. Am I right? Then my question is 3. Does boost use edge-triggered epoll in any kind of async IO on linux? 4. Isn't edge-triggered epoll a good method to implement async IO on linux? Thank you very much. Sincerely Journeyer ---------------------------------------- Journeyer J. Joh o o s a p r o g r a m m e r a t g m a i l d o t c o m ----------------------------------------

3 5

Install Boost.Build: gcc command not found (Windows)
by Tom C 29 May '13

29 May '13

I'm trying to build boost from sources following this guide: "http://www.boost.org/doc/libs/1_53_0/more/getting_started/windows.html#or-b…" I got the following outputs: here is bootstrap.log: here is my C:[...]\boost_1_53_0\tools\build\v2\user-config.jam: here is my PATH: It seems like the user-config.jam is not read by the bootstrap command. -- View this message in context: http://boost.2283326.n4.nabble.com/Install-Boost-Build-gcc-command-not-foun… Sent from the Boost - Users mailing list archive at Nabble.com.

3 2

Re: How to Boost static lib build under Mountain Lion and XCODE 4.6
by B Hart 27 May '13

27 May '13

Hi, I'm trying to install and use Boost 1_53_0 on MAC OS X Mountain Lion and use it with the latest XCODE 4.6.x. I want to port a small MS VS MFC C++ app. I developed on Windows to MAC. Specifically I need to install and build boost as static libraries. I'm completely new to programming on the MAC side of things. I understand that XCODE now uses LLVM Clang, with libc++ and not GCC. I've used GCC on Linux. I started following the instructions at: http://www.boost.org/doc/libs/1_53_0/more/getting_started/unix-variants.html but quickly ran into trouble. Does anyone have detailed instructions for how to install and compile boost statically under Mountain Lion and XCode 4.6? Below is the terminal input and output showing how far I got. Thanks. Terminal IO: ./bootstrap.sh --with-bjam=BJAM --with-toolset=TOOLSET users-Mac-mini:boost_1_53_0 user$ ./bootstrap --with-bjam=BJAM --with-toolset=TOOLSET -bash: ./bootstrap: No such file or directory users-Mac-mini:boost_1_53_0 user$ ./bootstrap.sh --with-bjam=BJAM --with-toolset=TOOLSET -n Detecting Python version... 2.7 -n Detecting Python root... /System/Library/Frameworks/Python.framework/Versions/2.7 -n Unicode/ICU support for Boost.Regex?... not found. Generating Boost.Build configuration in project-config.jam... Bootstrapping is done. To build, run: ./b2 To adjust configuration, edit 'project-config.jam'. Further information: - Command line help: ./b2 --help - Getting started guide: http://www.boost.org/more/getting_started/unix-variants.html - Boost.Build documentation: http://www.boost.org/boost-build2/doc/html/index.html users-Mac-mini:boost_1_53_0 user$ ./b2 link=static threading=multi toolset=darwin cxxflags="-arch i386 -arch x86_64" macosx-version=10.6 stage -bash: ./b2: No such file or directory

2 3

Using boost.Test check_is_small for my own
by Olaf Peter 26 May '13

26 May '13

Hello, I try to use parts of boost.test lib not for unit testing self but inside an algorithm. Anyway, at the end of header http://www.boost.org/doc/libs/1_53_0/boost/test/floating_point_comparison.h… this is written inside anonymous namespace it works obviously, but not at me. What happened here and how to fix it? Did I not read the header carefully? Thanks, Olaf ---8<---- #include <boost/test/floating_point_comparison.hpp> namespace tools { using boost::test_tools::check_is_small_t; check_is_small_t const& check_is_small = unit_test::ut_detail::static_constant<check_is_small_t>::value; } int main() { bool ok = tools::check_is_small(900, 0.1); } --->8---- test.cpp:5:30: error: 'boost::test_tools::check_is_small_t' has not been declared test.cpp:7:5: error: 'check_is_small_t' does not name a type test.cpp: In function 'int main()': test.cpp:12:15: error: 'check_is_small' is not a member of 'tools'

2 1

variant visitor using SFINAE problem
by Olaf Peter 26 May '13

26 May '13

Hi, attached my code to show my problem. It seems to work (partially) so far, but not the vector<int> where I get a compile error. This is my first try with SFINAE in that way. Are the conditions correct and robust enough? How to compile it? Did I forgot one use case? Using this small helper would simplify some post processing. Thanks, Olaf

2 4