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

[property_tree] Parsing vectors of objects
by Michael Powell 21 Jul '13

21 Jul '13

Hello, I want to parse to and from Xml (or possibly Json) using the property tree. I've got a simple POCO parsing, but now I need to include vectors of objects. Furthermore, I understand the property tree paths are pretty cumbersome. Not so much through a thin vernier, template function, something like that, but anywho... Here's the desired output I want in Xml, something like this: <output> <apples> <apple grower="red" /> <apple grower="green" /> <apple grower="golden" /> </apples> <oranges> <orange freshness="picked" /> <orange freshness="market" /> <orange freshness="store" /> </oranges> <items> <item name="" id="">1234</item> <item name="" id="">1234</item> <item name="" id="">1234</item> </items> </output> I understand the tree path might look something like this "output.apples.apple.<xmlattr>.grower", but what about the vector? Probably want to be trimming white spaces, indenting, as well. Regards, Michael Powell

2 2

Boost integration in Visual Studio 2010
by Georg.Kellerer＠lfu.bayern.de 20 Jul '13

20 Jul '13

Hi, we're using boost inour projects and all works fine. Our projects are standing under version control in a subversion repository. Our problem is that every developper had installed boost in a diferent place. Is their a way to get the reference to boost in a user speciffic configuration place? At the moment we have a fix path c:\dev\boost... but that does not fit for every developpers machine. Thanks for help, Georg ---------------------------------------------- Bayerisches Landesamt für Umwelt Referat Z6: IuK-Steuerung, Aufbau von Informationssystemen Hans-Högn-Str. 12 95030 Hof/Saale Tel.: 09281/1800-4572

6 7

[boost-users][Container] Compilation error using new "static_vector".
by Jupp Tscheak 20 Jul '13

20 Jul '13

Hello boost users, Please consider the following example: [code] #include "CGAL/Cartesian.h" #include "CGAL/Polygon_2.h" #include "boost/container/static_vector.hpp" typedef CGAL::Cartesian<double> Kernel; typedef Kernel::Point_2 Point2d; typedef CGAL::Polygon_2<Kernel, boost::container::static_vector<Point2d, 100> > Polygon2d; Polygon2d p; p = Polygon2d(); [/code] Compiling this code snippet with GCC results in following error message: [error] error: no match for 'operator=' in 'p = CGAL::Polygon_2<CGAL::Cartesian<double>, boost::container::static_vector<CGAL::Point_2<CGAL::Cartesian<double> >, 100u> >((*(const Traits*)(& CGAL::Polygon_2<CGAL::Cartesian<double>, boost::container::static_vector<CGAL::Point_2<CGAL::Cartesian<double> >, 100u> >::Traits())))' note: candidate is: CGAL-4.2/include/CGAL/Polygon_2.h:68:7: note: CGAL::Polygon_2<CGAL::Cartesian<double>, boost::container::static_vector<CGAL::Point_2<CGAL::Cartesian<double> >, 100u> >& CGAL::Polygon_2<CGAL::Cartesian<double>, boost::container::static_vector<CGAL::Point_2<CGAL::Cartesian<double> >, 100u> >::operator=(CGAL::Polygon_2<CGAL::Cartesian<double>, boost::container::static_vector<CGAL::Point_2<CGAL::Cartesian<double> >, 100u> >&) CGAL-4.2/include/CGAL/Polygon_2.h:68:7: note: no known conversion for argument 1 from 'sensor::Polygon2d {aka CGAL::Polygon_2<CGAL::Cartesian<double>, boost::container::static_vector<CGAL::Point_2<CGAL::Cartesian<double> >, 100u> >}' to 'CGAL::Polygon_2<CGAL::Cartesian<double>, boost::container::static_vector<CGAL::Point_2<CGAL::Cartesian<double> >, 100u> >&' [/error] I apologize for this concrete example using CGAL, but maybe someone has advice for me? Thanks in advance! Jupp Tscheak

2 2

Boost::thread instantiation and clean up
by Riskybiz 19 Jul '13

19 Jul '13

I have a C++ DLL written in Visual Studio for use on Windows 7 using Boost 1_53_0. The following two functions, CREATE & DESTROY, are called to launch and shutdown a simple ZeroMQ server (code below). The thread is launched and the server on that thread goes into a continuous listening loop (as intended). When it comes time to shut down the server then the thread is interrupted to cause thread termination (though I cannot tell if the interrupt is actually working as I get no output from the catch block). The boost::thread object is then deleted. Problem is that the 3rd party application which this DLL is designed for is prone to crashing after DESTROY is called and I think it's because either the boost::thread resources are not being freed/cleared up properly or the boost::thread is not interrupting. Have I properly handled thread instantiation, interruption and object destruction here? With thanks, Riskybiz. static bool createCalled = false;//initialise static variable static bool destroyCalled = false;//initialise static variable static boost::thread *serverThread = nullptr; int __stdcall CREATE() { if(createCalled == false) { createCalled = true; OutputDebugStringA("TestDataAccess: CREATE"); serverThread = new boost::thread(ListenOnReplySocket);//create instance of boost::thread object return 0; } return 1; } int __stdcall DESTROY() { if(createCalled == true && destroyCalled == false) { destroyCalled = true; OutputDebugStringA("TestDataAccess: DESTROY"); serverThread->interrupt();//set flag for interruption delete serverThread; return 0; } return 1; } Simple ZeroMQ server: #ifndef ZMQ_COMMUNICATIONS_H//if not defined already #define ZMQ_COMMUNICATIONS_H//then define it #define _WINSOCK2API_ //stops windows.h including winsock2.h #include <zmq.hpp> #include "boost\thread.hpp" int ListenOnReplySocket() { // Prepare our context and socket zmq::context_t context (1); zmq::socket_t socket (context, ZMQ_REP); socket.bind ("tcp://*:5555"); boost::this_thread::interruption_enabled(); try { while (true) { zmq::message_t request; // Wait for next request from client socket.recv (&request); char buffer[50]; int j; j = sprintf_s(buffer, 50, "TestDataAccess: ZMQComms: Hello"); OutputDebugStringA(buffer); // Do some 'work' Sleep (1000); // Send reply back to client zmq::message_t reply (5); memcpy ((void *) reply.data (), "World", 5); socket.send (reply); boost::this_thread::interruption_point();//check iterruption flag } } catch(boost::thread_interrupted) { char buffer[100]; int j; j = sprintf_s(buffer, 100, "TestDataAccess: ZMQComms: Server Thread Interrupted"); OutputDebugStringA(buffer); return 0; } } #endif

3 2

[fusion] how to get the tuple of min values of 2 tuples whatever their length?
by Frédéric Bron 18 Jul '13

18 Jul '13

I have two tuples: typedef boost::tuple<double, int, std::string> Key; Key k1, k2; I would like to get the tuple of the min values for each corresponding value between k1 and k2: Key min=Key(std::min(k1.get<0>(), k2.get<0>()), std::min(k1.get<1>(), k2.get<1>()), std::min(k1.get<2>(), k2.get<2>())); but I do not know the length of the tuple so I am looking for a generic algorithm... Is this possible with boost::fusion or boost::mpl? I have tried with boost::fusion::accumulate but I need to now in the functor the index of the value that is currently accessed to compare to the right one in k1. Frédéric

5 7

Named condition not behaving as expected
by rudasi 18 Jul '13

18 Jul '13

I have 2 processes (producer and consumer) sharing an int deque in shared memory, I have the producer process put 2 numbers in the deque and then it gets in a wait state losing its mutex lock. I then have the consumer process removing the numbers and printing them. It then does a notify on the condition which the producer is waiting on. The consumer then goes on its own wait on a second condition. After this case the producer does not wake up. I am using the same mutex between the processes. I have removed some of the code where i set up the shared memory and create the mutex and conditions. Producer process: int main() { scoped_lock<named_mutex> lock(mutex); while(1) { while (MyDeque->size() == 2) { full.wait(lock); std::cout << "unlocked producer" << std::endl; } if (MyDeque->size() == 0) { *a = 2; MyDeque->push_back(a); } if (MyDeque->size() == 1) { *b = 4; MyDeque->push_back(b); empty.notify_one(); } } } Consumer process: int main() { scoped_lock<named_mutex> lock(mutex); while(1) { //volatile int size = MyDeque->size(); while (MyDeque->size() == 0) { empty.wait(lock); } if (MyDeque->size() == 2) { std::cout << "Consumer: " << *MyDeque->front() << std::endl; MyDeque->pop_front(); } if (MyDeque->size() == 1) { std::cout << "Consumer: " << *MyDeque->front() << std::endl; MyDeque->pop_front(); full.notify_one(); } } } While debugging things seem to go ok for the first iteration, the producer puts numbers 2 and 4 on the deque then waits on the full condition. The Consumer then gets the lock, prints these numbers, does a notify_one on the full condition and then goes into a wait. After this the producer does not wake up. -- View this message in context: http://boost.2283326.n4.nabble.com/Named-condition-not-behaving-as-expected… Sent from the Boost - Users mailing list archive at Nabble.com.

1 0

[serialization] platform independence (32 & 64bit windows)
by आशीष वर्मन् 18 Jul '13

18 Jul '13

Hi We are using boost serialization our product which was 32bit only till now. Now we have started building it on 64bit as well. On finding that boost::binary_archive is not platform independent, we seem to have 2 options: 1. Use text_archive - (but are worried about performance since the serialized data is approx 500MB even after gzip compression) 2. Use the eos portable archive - (but it is updated only till boost 1.49. We are using 1.53) So my questions are: 1. One (and only one) of our archives created by our 32 bit executable is successfully read in by the 64 bit executable while the rest throw exception on reading the archive signature. If the platform is encoded in the signature, why is that one archive being read in successfully. 2. Which of the above two approaches would be better and why. Thanks in advance. Yours Sincerely Ashish Varman

3 3

Boost::Interprocess mutex with condition variable
by Riskybiz 17 Jul '13

17 Jul '13

I'm trying to get a working implementation of a boost::interprocess named_mutex with a named_condition_variable. I have created the following toy console applications to try and understand what's necessary. The console application 'Sleeper' is run first; it simply creates some resources and then goes to sleep. Then 'Waker' is run with the intention that it would cause the 'Sleeper' instance to resume execution and print out a further message. Ultimately the intention is to have one Waker process and several Sleeper processes. When each application is run in a separate terminal window then the Sleeper process sleeps and the Waker process tries to wake; but it is ineffective. Can anyone advise what is wrong here and how to get the notify_all() to take effect? Thanks Riskybiz. // Sleeper.cpp : Defines the entry point for the console application. // #include "stdafx.h" #include <boost/interprocess/managed_shared_memory.hpp> #include <boost/interprocess/sync/named_mutex.hpp> #include <boost/interprocess/sync/named_condition.hpp> #include <iostream> int _tmain(int argc, _TCHAR* argv[]) { using namespace boost::interprocess; //Clean up resources from any prior instances named_condition::remove("msm_named_condition"); named_mutex::remove("msm_named_mutex"); //shared_memory_object::remove("msm"); //Setup shared memory resources managed_shared_memory *msm = new managed_shared_memory(create_only, "msm", 10000); named_mutex *nm = new named_mutex(create_only, "msm_named_mutex"); named_condition *nc = new named_condition(create_only, "msm_named_condition"); try { scoped_lock<named_mutex> lock(*nm);//acquire scoped lock for mutex std::cout << "Going to sleep now...." << std::endl; nc->wait(lock);//induce wait std::cout << "Wide awake and back in the room" << std::endl;//print this out on waking up } catch(interprocess_exception &ipe) { std::cout << "Error in Sleeper process: interprocess_exception: "<< ipe.what() << std::endl; } //Clean up delete msm; delete nm; delete nc; return 0; } // Waker.cpp : Defines the entry point for the console application. // #include "stdafx.h" #include <boost/interprocess/managed_shared_memory.hpp> #include <boost/interprocess/sync/named_mutex.hpp> #include <boost/interprocess/sync/named_condition.hpp> #include <iostream> int _tmain(int argc, _TCHAR* argv[]) { using namespace boost::interprocess; //Setup shared memory resources managed_shared_memory *msm = new managed_shared_memory(open_only, "msm"); named_mutex *nm = new named_mutex(open_only, "msm_named_mutex"); named_condition *nc = new named_condition(open_only, "msm_named_condition"); try { scoped_lock<named_mutex> lock(*nm);//acquire scoped lock for mutex std::cout << "Going to Notify...." << std::endl; nc->notify_all();//notify to release the wait condition std::cout << "Wakey Wakey....Notified...." << std::endl; } catch(interprocess_exception &ipe) { std::cout << "Error in Waker process: interprocess_exception: "<< ipe.what() << std::endl; } //Clean up delete msm; delete nm; delete nc; return 0; }

2 1

multi_index_container with protected constructor
by Horváth Imre 17 Jul '13

17 Jul '13

Hi, I want to use boost::multi_index_container with a class that have protected constructors, but the compile fails. I think I should make multi_index_container a friend of my class, but I don't know how. #include <iostream> #include <boost/shared_ptr.hpp> #include <boost/multi_index_container.hpp> #include <boost/multi_index/ordered_index.hpp> #include <boost/multi_index/composite_key.hpp> #include <boost/multi_index/mem_fun.hpp> class Item { public: typedef boost::shared_ptr<Item> P; static P create() { return P(new Item()); } static P create(P item) { return P(new Item(item)); } protected: Item() { } Item(P item) : source(item->get_source()) , target(item->get_target()) { } public: std::string source; std::string target; std::string get_source() const {return source;} std::string get_target() const {return target;} struct key : boost::multi_index::composite_key< P, boost::multi_index::const_mem_fun<Item, std::string, &Item::get_source>, boost::multi_index::const_mem_fun<Item, std::string, &Item::get_target> >{}; typedef boost::multi_index_container< P, boost::multi_index::indexed_by< boost::multi_index::ordered_non_unique< key, boost::multi_index::composite_key_result_less<key::result_type> > > > index_t; }; int main() { Item::index_t index; Item::P t1 = Item::create(); index.insert(t1); return 0; } Thanks in advance: Imre Horvath

2 2

[Boost.Log] Example tutorial_fmt_stream.cpp does not compile
by Mario Knezović 17 Jul '13

17 Jul '13

I am trying to change date formatting exactly in the way as described in the tutorial, sub-section "Specialized formatters": http://www.boost.org/doc/libs/1_54_0/libs/log/doc/html/log/tutorial/formatt… What I want to achieve is pretty simple, change month output from the default "Abbreviated month name" (%b): [2013-Jul-08 10:51:00.989235] to "Month name as a decimal 01 to 12" (%m): [2013-07-08 10:51:00.989235] Unfortunately this does not compile, nor does the example from which the snipped is taken: "tutorial_fmt_stream.cpp". The interesting part in the example source is commented out by default. (But this was the case with other examples too.) The part I'm interested in is in line 60 (from current Boost 1.54.0): expr::format_date_time< boost::posix_time::ptime >("TimeStamp", "%Y-%m-%d %H:%M:%S") The errors I get (Win7, 64-bit, MS VC++ 2010): error C2027: use of undefined type "boost::log::v2s_mt_nt5::expressions::aux::date_time_formatter_generator_traits<T,CharT>" d:\boost\boost_1_54_0\boost\log\expressions\formatters\date_time.hpp 94 error C3861: "parse": Identifier not found. d:\boost\boost_1_54_0\boost\log\expressions\formatters\date_time.hpp 94 I hope somebody can help or point me in the right direction. Thank you! Mario Knezović

1 1

[log, spirit] phoenix version conflict
by Yi Ding 17 Jul '13

17 Jul '13

It looks like Boost.Log conflicts with Boost.Spirit because they're using different version of Boost Phoenix? Take this example file: #include <boost/log/common.hpp> #include <boost/log/sinks.hpp> #include <boost/spirit/include/karma.hpp> int main() { } We get this warning: In file included from /opt/boost_1_54_0/include/boost/log/detail/custom_terminal_spec.hpp:21, /opt/boost_1_54_0/include/boost/spirit/include/phoenix_core.hpp:13:1: warning: "BOOST_PHOENIX_DEFINE_CUSTOM_TERMINAL" redefined /opt/boost_1_54_0/include/boost/phoenix/core/terminal.hpp:22:1: warning: this is the location of the previous definition There are a bunch of errors that result as well.

2 2

How to build libboost_filesystem-vc110-mt-sgd-1_54.lib with VS2012 x64?
by Amann, Julian 17 Jul '13

17 Jul '13

I have some trouble building the boost filesystem lib using VS2012 x64. I use the following instructions to build it: 1. Download boost 1.54.0 from http://www.boost.org/ 2. Extract files (e.g. "C:\thirdparty\vs2013\x64\boost_1_54_0") 3. Start Visual Studio 2012 x64 command prompt 4. Change to boost directory (e.g. "cd C:\thirdparty\vs2010\x64\boost_1_54_0") 5. Execute .\bootstrap.bat 6. Execute b2 address-model=64 toolset=msvc-11.0 --build-type=complete stage --with-filesystem --with-signals --with-system Unfortunately the file "libboost_filesystem-vc110-mt-sgd-1_54.lib" is not build Previously I used boost 1.51.0, 1.52.0 and 1.53.0. In this releases the libboost_filesystem-vc110-mt-sgd-1_5x.lib was always build without any problems. Did anybody mange to build this lib using VS2012? Which instructions do you use to build it? Best regards, Julian

1 0

[log] operator<< best practices
by Yi Ding 16 Jul '13

16 Jul '13

I noticed boost log has a helper function for operator<< template< typename CharT, typename TraitsT, typename AllocatorT, typename T > inline basic_formatting_ostream< CharT, TraitsT, AllocatorT >& operator<< (basic_formatting_ostream< CharT, TraitsT, AllocatorT >& strm, T const& value) { strm.stream() << value; return strm; } which is useful because a lot of code has operator<< overloads specifically for std::ostream. Recently we've moved our code to use a generic template <class stream, int N> inline stream& operator<<(stream& os, const BlahClass& value) which conflicts with the boost log helper function, but is useful for our own ostream-like classes. What's the best practice here? Can we make the two mesh by using traits of some sort? Should we do all of our type to string conversions ahead of time using something like folly::to? Cheers, Yi

1 0

[Boost.Log] An update on severity level issue
by Leo Carreon 16 Jul '13

16 Jul '13

Hi all, I am still having the issue with the missing severity level string in the logs and have decided to give you my latest code. Here is my current code: #include <iostream> #include <iomanip> #include <cstdlib> #include <fstream> #include <boost/log/core.hpp> #include <boost/log/sources/global_logger_storage.hpp> #include <boost/log/sources/severity_logger.hpp> #include <boost/log/sources/record_ostream.hpp> #include <boost/log/attributes/clock.hpp> #include <boost/log/attributes/current_process_name.hpp> #include <boost/log/attributes/current_process_id.hpp> #include <boost/log/attributes/current_thread_id.hpp> #include <boost/log/utility/setup/file.hpp> #include <boost/log/utility/setup/from_stream.hpp> #include <boost/log/utility/manipulators/to_log.hpp> #include <boost/log/utility/formatting_ostream.hpp> using namespace std; namespace logging = boost::log; namespace keywords = boost::log::keywords; namespace expr = boost::log::expressions; namespace attr = boost::log::attributes; namespace src = boost::log::sources; #define LFC1_LOG_TRACE(logger) BOOST_LOG_SEV(logger, trace) << "(" << __FILE__ << ", " << __LINE__ << ") " #define LFC1_LOG_DEBUG(logger) BOOST_LOG_SEV(logger, debug) << "(" << __FILE__ << ", " << __LINE__ << ") " #define LFC1_LOG_INFO(logger) BOOST_LOG_SEV(logger, info) << "(" << __FILE__ << ", " << __LINE__ << ") " #define LFC1_LOG_WARNING(logger) BOOST_LOG_SEV(logger, warning) << "(" << __FILE__ << ", " << __LINE__ << ") " #define LFC1_LOG_ERROR(logger) BOOST_LOG_SEV(logger, error) << "(" << __FILE__ << ", " << __LINE__ << ") " static const auto RET_SUCCESS = 0; static const auto RET_FAIL = 1; static const auto LOGGING_ENVIRONMENT_NAME = "LOGGING_CONFIG_FILE_NAME"; static const auto DEFAULT_LOGGING_CONFIG_FILE_NAME = "config/LogSettings.txt"; enum ESeverityLevel { trace, debug, info, warning, error }; BOOST_LOG_ATTRIBUTE_KEYWORD(severity, "Severity", ESeverityLevel) ostream& operator<<(ostream& arStream, ESeverityLevel avLevel) { static const char* pStrings[] = { "trace", "debug", "info", "warning", "error" }; if (static_cast<size_t>(avLevel) < sizeof(pStrings) / sizeof(*pStrings)) { arStream << pStrings[avLevel]; } else { arStream << static_cast<int>(avLevel); } return arStream; } logging::formatting_ostream& operator<< ( logging::formatting_ostream& arStream, logging::to_log_manip<ESeverityLevel, tag::severity> const& arManip ) { static const char* pStrings[] = { "TRACE", "DEBUG", "INFO", "WARNING", "ERROR" }; ESeverityLevel vLevel = arManip.get(); if (static_cast<size_t>(vLevel) < sizeof(pStrings) / sizeof(*pStrings)) { arStream << pStrings[vLevel]; } else { arStream << static_cast<int>(vLevel); } return arStream; } BOOST_LOG_INLINE_GLOBAL_LOGGER_DEFAULT(SLogger, src::severity_logger<ESeverityLevel>) static void gvLoggingInit(const char* apConfigFileName = nullptr) { // Obtain the name of the logging configuration file. if (apConfigFileName == nullptr || apConfigFileName[0] == 0) { if ((apConfigFileName = getenv(LOGGING_ENVIRONMENT_NAME)) == 0 || apConfigFileName[0] == 0) { apConfigFileName = DEFAULT_LOGGING_CONFIG_FILE_NAME; } } // Open the logging configuration file. ifstream vConfigFile(apConfigFileName); if (!vConfigFile.is_open()) { // TODO: throw an exception } // Read the contents of the logging configuration file. logging::init_from_stream(vConfigFile); // Add the logging attributes that we require. auto pCore = logging::core::get(); pCore->add_global_attribute("TimeStamp", attr::local_clock()); pCore->add_global_attribute("Process", attr::current_process_name()); pCore->add_global_attribute("ProcessID", attr::current_process_id()); pCore->add_global_attribute("ThreadID", attr::current_thread_id()); pCore->set_filter(severity >= info); } int main() { auto vRetVal = RET_SUCCESS; try { gvLoggingInit(); auto& vLogger = SLogger::get(); LFC1_LOG_TRACE(vLogger) << "A trace severity message"; LFC1_LOG_DEBUG(vLogger) << "A debug severity message"; LFC1_LOG_INFO(vLogger) << "An informational severity message"; LFC1_LOG_WARNING(vLogger) << "A warning severity message"; LFC1_LOG_ERROR(vLogger) << "An error severity message"; } catch (exception& crException) { cerr << crException.what() << endl; vRetVal = RET_FAIL; } catch (...) { cerr << "Unknown exception" << endl; vRetVal = RET_FAIL; } return vRetVal; } Here is what’s in the settings file: [Core] Filter="%Severity% >= 2" DisableLogging=false [Sinks.File] Destination=TextFile FileName=log/test_logging_%N.log RotationSize=1048576 Target=logs MaxSize=10485760 ScanForFiles=All Format="%TimeStamp% [%Severity%] %Process%:%ProcessID%:%ThreadID% %Message%" As mentioned in a previous post, the issue I’m having is this is how the resulting log records look like: 2013-Jul-16 11:24:59.758177 [] test_logging:000000x9f3:0x403cc6c0 (src/test_logging.cpp, 240) An informational severity message 2013-Jul-16 11:24:59.758812 [] test_logging:000000x9f3:0x403cc6c0 (src/test_logging.cpp, 241) A warning severity message 2013-Jul-16 11:24:59.758851 [] test_logging:000000x9f3:0x403cc6c0 (src/test_logging.cpp, 242) An error severity message Note that the severity string is missing from the above log records. Does anyone know I can fix the code to make the severity string show up in the log records? Another question I have is how do I change the format of the date in the timestamp from YYY-MMM-DD to YYYY-MM-DD. I am sticking to using logging settings from a file because I want an application user to be able to control where log records go. However, I am open to the idea of setting the format within the code but at the moment there is no option of setting the format when a settings file is used. It would be nice to have a function within the logging core which allows us to obtain a pointer/reference to the existing sinks. Kind regards, Leo

1 0

Problems include the RANDOM LIBRARIES, in a console project, in Windows.
by Alberto Aliberti 16 Jul '13

16 Jul '13

I used the Random libraries of Boost collection. I have implemented it in my program. A program for the chess analysis . Now, at compile time I have no problem. Everything ok, the console project is compiled without errors. During run time, the functions of Boost Random libraries, correctly generate a random number. But after a few repetitions of the loop (from 2/3 to a few tens of loops), the program crashes. The strange thing that the crash does not occur in the functions where I use the random functions, but occurs in the chess engine that does not use these functions, and thus in theory should not be influenced by it. But if I do not use the functions of Boost library and use the basic function of C + + (rand ();) I have no problems. I work in Windows. My project is a console project compiled with VC + +2010. Also I have wrote a test program with VC + +2010, which generates a sequence of random numbers, using Boost libraries. In this case I have no problems. Only when I implement the libraries in the chess program I have problems. So it seems that your libraries are in conflict with the chess engine. What do you recommend for the search for the cause of the problem? The headers and the function use by me in my program: #include <boost/random/mersenne_twister.hpp> #include <boost/random/uniform_smallint.hpp> // initializes boost random generator seed boost::random::mt19937 gen; // random function int ransel(int minr,int maxr) { boost::random::uniform_smallint <> dist(minr, maxr); return dist(gen); } ________ Then I call the ransel() function in the loop of my program to select the chess moves.

2 2

quick threading query
by Sean Farrow 15 Jul '13

15 Jul '13

Hi all, I have a quick threading query. I'm in the process of rewriting an application to take advantage of concurrency. This application is cross-platform so I'm looking at the boost threading library to solve the issue. When the window is created I'm creating a thread, then when the user chooses to quit I need to notify the created thread to stop running. Would a future do the job, if this is the case where should this be stored in the class that represents the window or in the class that represents the thread, I'm really not wanting to store this globally. Any help appreciated. Cheers Sean.

2 1

1.54.0 breaks bcp-produced partial builds?
by Bruce Stephens 15 Jul '13

15 Jul '13

Back in 1.53.0, I could do the following: ./bootstrap.sh (cd tools/bcp; ../../b2) bin.v2/.../bcp build filesystem .../temp Then in .../temp run ./bootstrap.sh and ./b2 to build just filesystem (or whatever else I copied). In 1.54.0, the copy doesn't build: brs% ./b2 Building the Boost C++ Libraries. /auto/tmpfs/temp/tools/build/v2/build/targets.jam:397: in find-really *** argument error * rule project.is-registered-id ( id ) * called with: ( ) * missing argument id /auto/tmpfs/temp/tools/build/v2/build/project.jam:600:see definition of rule 'project.is-registered-id' being called /auto/tmpfs/temp/tools/build/v2/build/targets.jam:457: in class(a)project-target.find /auto/tmpfs/temp/tools/build/v2/build/targets.jam:841: in resolve-reference /auto/tmpfs/temp/tools/build/v2/build/targets.jam:858: in targets.generate-from-reference /auto/tmpfs/temp/tools/build/v2/build/targets.jam:1245: in generate-dependencies /auto/tmpfs/temp/tools/build/v2/build/targets.jam:1302: in class(a)basic-target.generate /auto/tmpfs/temp/tools/build/v2/build/targets.jam:757: in generate-really /auto/tmpfs/temp/tools/build/v2/build/targets.jam:729: in class(a)main-target.generate /auto/tmpfs/temp/tools/build/v2/build/targets.jam:272: in class(a)project-target.generate /auto/tmpfs/temp/tools/build/v2/build/targets.jam:874: in targets.generate-from-reference /auto/tmpfs/temp/tools/build/v2/build/targets.jam:1245: in generate-dependencies /auto/tmpfs/temp/tools/build/v2/build/targets.jam:1302: in class(a)basic-target.generate /auto/tmpfs/temp/tools/build/v2/build/targets.jam:757: in generate-really /auto/tmpfs/temp/tools/build/v2/build/targets.jam:729: in class(a)main-target.generate /auto/tmpfs/temp/tools/build/v2/build/targets.jam:874: in targets.generate-from-reference /auto/tmpfs/temp/tools/build/v2/build/targets.jam:1245: in generate-dependencies /auto/tmpfs/temp/tools/build/v2/build/targets.jam:1302: in alias-target-class.generate /auto/tmpfs/temp/boostcpp.jam:391: in build-multiple /auto/tmpfs/temp/boostcpp.jam:353: in class(a)top-level-target.generate /auto/tmpfs/temp/tools/build/v2/build/targets.jam:757: in generate-really /auto/tmpfs/temp/tools/build/v2/build/targets.jam:729: in class(a)main-target.generate /auto/tmpfs/temp/tools/build/v2/build/targets.jam:874: in targets.generate-from-reference /auto/tmpfs/temp/tools/build/v2/build/targets.jam:1245: in generate-dependencies /auto/tmpfs/temp/tools/build/v2/build/targets.jam:1302: in alias-target-class.generate /auto/tmpfs/temp/boostcpp.jam:391: in build-multiple /auto/tmpfs/temp/boostcpp.jam:353: in class(a)top-level-target.generate /auto/tmpfs/temp/tools/build/v2/build/targets.jam:757: in generate-really /auto/tmpfs/temp/tools/build/v2/build/targets.jam:729: in class(a)main-target.generate /auto/tmpfs/temp/tools/build/v2/build/targets.jam:272: in class(a)project-target.generate /auto/tmpfs/temp/tools/build/v2/build-system.jam:707: in load /auto/tmpfs/temp/tools/build/v2/kernel/modules.jam:289: in import /auto/tmpfs/temp/tools/build/v2/kernel/bootstrap.jam:139: in boost-build /auto/tmpfs/temp/boost-build.jam:17: in module scope

1 1

Re: [Boost-users] [Boost.Log] More queries
by Leo Carreon 15 Jul '13

15 Jul '13

From: Leo Carreon Sent: Saturday, July 13, 2013 3:51 PM To: Boost Users Mailing List Subject: [Boost.Log] More queries Hi everyone, As I have mentioned in a previous post, I have been trying to learn how to use Boost.Log. I have been experimenting with logging to a file with filtering and specifying the log formatting in three different ways, namely: 1. Specifying the log formatting using a lambda type expression. 2. Specifying the log formatting using a plain text string with placeholders for the attributes that I have defined. 3. Specifying the log formatting in a settings file. (However, the formatting string is exactly the same as in 2 above.) I have attached a copy of my source code and settings file. Note that I comment out parts of the source code file depending on which option I use above. The problem I’m encountering is when I use options 2 & 3 above, the severity level string does not appear in the log. But if I use option 1, the severity level string appears as expected. It is my understanding that severity level is a pre-defined attribute when using a severity_logger. Am I missing something when using options 2 & 3? If I decide to use my own severity level enumeration, what do I need to do? Kind regards, Leo Hi again everyone, I have managed to use my own severity level enumeration but the severity level string is still not appearing in the log. Regards again, Leo

2 4

boost-libs failed to be built (via pkgsrc)
by Isaac Isao Saito 15 Jul '13

15 Jul '13

Hi boost-users, during source installation of `boost-libs` (link to cvs repo[0]), I get the following at the very end of long output of bmake (`make` that's used in the package manager `pkgsrc` that I use) and build seems to fail: ...skipped <pbin.v2/libs/wave/build/gcc-4.4.2/release/link-static/threading-multi>libboost_wave.a for lack of <pbin.v2/libs/wave/build/gcc-4.4.2/release/link-static/threading-multi>instantiate_cpp_exprgrammar.o... ...skipped <pstage/lib>libboost_wave.a for lack of <pbin.v2/libs/wave/build/gcc-4.4.2/release/link-static/threading-multi>libboost_wave.a... ...failed updating 181 targets... ...skipped 280 targets... *** Error code 1 Stop. bmake: stopped in /usr/pkgsrc/devel/boost-libs *** Error code 1 I noticed, out of thousands of output lines (full output[1]), some lines of error repeatedly appear. I just except some (note that they don't occur back to back like the following): g++: unrecognized option '-pthread' ./boost/cstdint.hpp:74: error: 'intleast8_t' in namespace '::' does not name a type ./boost/cstdint.hpp:76: error: 'uintleast8_t' in namespace '::' does not name a type ./boost/chrono/detail/inlined/posix/chrono.hpp:23: error: '::clock_gettime' has not been declared ./boost/chrono/detail/inlined/posix/chrono.hpp:36: error: '::clock_gettime' has not been declared ./boost/chrono/detail/inlined/posix/process_cpu_clocks.hpp:31: error: '::sysconf' has not been declared ./boost/chrono/detail/inlined/posix/process_cpu_clocks.hpp:31: error: '_SC_CLK_TCK' was not declared in this scope /usr/qnx650/host/qnx6/x86/usr/bin/ntox86-ld: cannot find -lrt ./boost/smart_ptr/detail/yield_k.hpp:123: error: 'nanosleep' was not declared in this scope ./boost/thread/pthread/timespec.hpp:84: error: '::clock_gettime' has not been declared ./boost/thread/pthread/mutex.hpp:275: error: 'boost::chrono::steady_clock' has not been declared libs/filesystem/src/operations.cpp: In function 'bool<unnamed>::remove_directory(const boost::filesystem::path&)': libs/filesystem/src/operations.cpp:345: error: '::rmdir' has not been declared libs/filesystem/src/operations.cpp:348: error: '::unlink' has not been declared libs/filesystem/src/operations.cpp:427: error: no matching function for call to 'stat::stat(const char*, stat*)' libs/filesystem/src/operations.cpp:1003: error: '::symlink' has not been declared ``` Other `boost`-related packages (namely boost-headers, boost-jam, boost-docs, boost-build) are already built and installed. `boost-python` fails to be built, but I assume it's not depended by boost-libs. Using `QNX` 6.5.0 SDP SP1. boost seems to be 1.53.0 What could be wrong? Thank you very much. [0] http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/devel/boost-libs/#dirlist [1] http://pastebin.com/ZMU3ddXf -- Isaac

1 0

From Big-endian to Little-endian.
by Mauro Ziliani 15 Jul '13

15 Jul '13

Hi all. This is my first post. I'm working with boost::asio::ip::tcp to dialogate with a peripheral which send frames grouped in words (16 bit values). The peripheral uses a big-endian byte-order, while the host uses a little-endian byte-order. Is there some template which makes the swap automatically? Best regards, Mauro

1 0

VS2012: libboost_filesystem-vc110-mt-gd-1_54.lib missing
by Amann, Julian 15 Jul '13

15 Jul '13

Hello, I built boost 1.54.0 with Visual Studio 2012 x64. I tried to build a small demo that is using boost filesystem: ///////////////////////////////////////////////////////////////////// #include <iostream> #include <boost/filesystem.hpp> using namespace boost::filesystem; int main(int argc, char* argv[]) { if (argc < 2) { std::cout << "Usage: tut1 path\n"; return 1; } std::cout << argv[1] << " " << file_size(argv[1]) << '\n'; return 0; } ///////////////////////////////////////////////////////////////////// CMake is used to setup the corresponding project for VS2012 x64: ################################################# CMAKE_MINIMUM_REQUIRED(VERSION 2.8.9) PROJECT(FilesystemTest) set_property(GLOBAL PROPERTY USE_FOLDERS ON) SET(CMAKE_MODULE_PATH ${PROJECT_SOURCE_DIR}/build/) # Visual Studio 2010 Pro Standard: /DWIN32 /D_WINDOWS /W3 /Zm1000 /EHsc /GR SET(CMAKE_CXX_FLAGS "/DWIN32 /D_WINDOWS /W4 /Zi /EHsc /GR- /MP /openmp") SET(CMAKE_DEBUG_POSTFIX "d") FIND_PACKAGE(Boost COMPONENTS filesystem system REQUIRED) # Unicode rules! ADD_DEFINITIONS(-D_UNICODE) include_directories(${Boost_INCLUDE_DIR}) LINK_DIRECTORIES( ${Boost_LIBRARY_DIRS} ) file(GLOB FilesystemTest_SOURCES src/*.*) # Create a target for the library ADD_EXECUTABLE(FilesystemTest ${FilesystemTest_SOURCES}) ################################################# But when compiling I get 'libboost_filesystem-vc110-mt-gd-1_54.lib' is missing. Previously I used boost 1.53.0 - everything was working perfect when using boost 1.53.0. When looking into the boost 1.54 lib folder there is only a 'boost_filesystem-vc110-mt-gd-1_54.lib' and a 'libboost_filesystem-vc110-mt-sgd-1_54.lib' I compiled boost using this instructions: 1. Download boost 1.54.0 from http://www.boost.org/ 2. Extract files (e.g. "C:\thirdparty\vs2013\x64\boost_1_54_0") 3. Start Visual Studio 2012 x64 command prompt 4. Change to boost directory (e.g. "cd C:\thirdparty\vs2010\x64\boost_1_54_0") 5. Execute .\bootstrap.bat 6. Execute b2 address-model=64 toolset=msvc-11.0 --build-type=complete stage BTW: If only certain libraries (for instance filesystem) are need step 6 can be replaced by this: b2 address-model=64 toolset=msvc-11.0 --build-type=complete stage --with-filesystem --with-signals --with-system I could not figure out what is working wrong. Any ideas? Best regards Julian

1 0

issues compiling Boost 1.54 thread on AIX5.2
by Gert 15 Jul '13

15 Jul '13

Any clues here? Regards, Gert vacpp.compile.c++ bin.v2/libs/thread/build/vacpp/debug/address-model-64/link-static/runtime-link-static/threading-multi/pthread/thread.o xlC_r -c -DBOOST_ALL_NO_LIB=1 -DBOOST_SYSTEM_STATIC_LINK=1 -DBOOST_THREAD_BUILD_LIB=1 -DBOOST_THREAD_DONT_USE_CHRONO -DBOOST_THREAD_POSIX -qcpluscmt -qNOOPTimize -qnoinline -q64 -g -qfullpath -qfuncsect -qeh -qrtti -I"." -o "bin .v2/libs/thread/build/vacpp/debug/address-model-64/link-static/runtime-link-static/threading-multi/pthread/thread.o" "libs/thread/src/pthread/thread.cpp" "./boost/smart_ptr/shared_ptr.hpp", line 82.43: 1540-0403 (S) "template <class T, std::size_t N> struct boost::detail::sp_element<T [N]>" is already defined. "./boost/smart_ptr/shared_ptr.hpp", line 75.28: 1540-0425 (I) "sp_element<T []>" is defined on line 75 of "./boost/smart_ptr/shared_ptr.hpp". "./boost/smart_ptr/shared_ptr.hpp", line 131.43: 1540-0403 (S) "template <class T, std::size_t N> struct boost::detail::sp_dereference<T [N]>" is already defined. "./boost/smart_ptr/shared_ptr.hpp", line 124.28: 1540-0425 (I) "sp_dereference<T []>" is defined on line 124 of "./boost/smart_ptr/shared_ptr.hpp". "./boost/smart_ptr/shared_ptr.hpp", line 156.43: 1540-0403 (S) "template <class T, std::size_t N> struct boost::detail::sp_member_access<T [N]>" is already defined. "./boost/smart_ptr/shared_ptr.hpp", line 149.28: 1540-0425 (I) "sp_member_access<T []>" is defined on line 149 of "./boost/smart_ptr/shared_ptr.hpp". "./boost/smart_ptr/shared_ptr.hpp", line 181.43: 1540-0403 (S) "template <class T, std::size_t N> struct boost::detail::sp_array_access<T [N]>" is already defined. "./boost/smart_ptr/shared_ptr.hpp", line 174.28: 1540-0425 (I) "sp_array_access<T []>" is defined on line 174 of "./boost/smart_ptr/shared_ptr.hpp". "./boost/thread/detail/async_func.hpp", line 94.58: 1540-0711 (S) Too few template arguments have been specified. "./boost/thread/detail/async_func.hpp", line 166.54: 1540-0711 (S) Too few template arguments have been specified. "./boost/thread/detail/async_func.hpp", line 231.50: 1540-0711 (S) Too few template arguments have been specified. "./boost/thread/detail/async_func.hpp", line 291.46: 1540-0711 (S) Too few template arguments have been specified. "./boost/thread/detail/async_func.hpp", line 346.42: 1540-0711 (S) Too few template arguments have been specified. "./boost/thread/detail/async_func.hpp", line 396.38: 1540-0711 (S) Too few template arguments have been specified. "./boost/thread/detail/async_func.hpp", line 441.34: 1540-0711 (S) Too few template arguments have been specified. "./boost/thread/detail/async_func.hpp", line 481.30: 1540-0711 (S) Too few template arguments have been specified. "./boost/thread/detail/async_func.hpp", line 516.26: 1540-0711 (S) Too few template arguments have been specified. "./boost/thread/detail/async_func.hpp", line 546.22: 1540-0711 (S) Too few template arguments have been specified. "./boost/thread/cv_status.hpp", line 23.3: 1540-0219 (S) The call to "operator==" has no best match. "./boost/thread/cv_status.hpp", line 23.3: 1540-1229 (I) Argument number 1 is an rvalue of type "boost::cv_status::enum_type". "./boost/thread/cv_status.hpp", line 23.3: 1540-1229 (I) Argument number 2 is an rvalue of type "boost::cv_status::enum_type". "./boost/thread/cv_status.hpp", line 23.3: 1540-1202 (I) No candidate is better than "builtin operator==(int, int)". "./boost/thread/cv_status.hpp", line 23.3: 1540-1231 (I) The conversion from argument number 1 to "int" uses "an integral promotion". "./boost/thread/cv_status.hpp", line 23.3: 1540-1231 (I) The conversion from argument number 2 to "int" uses "an integral promotion". "./boost/thread/cv_status.hpp", line 23.3: 1540-1202 (I) No candidate is better than "boost::operator==(self_type, enum_type)". "./boost/thread/cv_status.hpp", line 23.3: 1540-1231 (I) The conversion from argument number 1 to "boost::cv_status" uses the user-defined conversion "boost::cv_status::cv_status(enum_type)" followed by "an lvalue-to-rvalue transformatio n". ... ... -- View this message in context: http://boost.2283326.n4.nabble.com/issues-compiling-Boost-1-54-thread-on-AI… Sent from the Boost - Users mailing list archive at Nabble.com.

4 4

[serialization] unregistered class exception during serialization from DLL
by Andreas Mainik 14 Jul '13

14 Jul '13

Hello All, I have some classes needed to be serialized (A.HPP und A.CPP below). The serialization happens over the pointer to the base class. The code is called in the function (FUNC.CPP below). The files A.HPP, A.CPP and FUNC.CPP are constituents of a bigger DLL-library. If my test application is linked dynamical against the DLL-libary then the code throws an exception "unregistered class - derived class not registered or exported". What is wrong in my code? The code is compiled with Visual Studio 2012 (default settings). Boost: 1.53.0 If I look into BOOST_SERIALIZATION_DECL(const extended_type_info *) extended_type_info_typeid_0::get_extended_type_info( const std::type_info & ti ) const { typeid_system::extended_type_info_typeid_arg etia(ti); const tkmap & t = singleton<tkmap>::get_const_instance(); const tkmap::const_iterator it = t.find(& etia); if(t.end() == it) return NULL; return *(it); } then I see that Ord<Options> is not registered in singleton<tkmap>::get_const_instance(). Moreover, I am not able to set breakpoint into Ord<Options>::serialize(). According to MSVC debugger the breakpoint will not be hit. Additional remarks: 1) If I uncomment the code lines in FUNC.CPP then everything works. 2) If I link the code statical to my test application then everything is also fine. -----------------------A.HPP----------------------------------------------- #include "archive.hpp" // includes the required headers struct OrdBasis { virtual ~OrdBasis() {} virtual bool is_base_of(const boost::shared_ptr<OrdBasis>& derived_ptr) { return true; } private: friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int /* file_version */){ } }; template<typename P> struct Ord; struct Options { Options() {} friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int /* file_version */){ } }; template<> class Ord<Options> : public OrdBasis { typedef Ord<Options> P; bool is_base_of(const boost::shared_ptr<OrdBasis>& derived_ptr) { const boost::shared_ptr<P> base_ptr = boost::dynamic_pointer_cast<P>(derived_ptr); bool result = (base_ptr) ? true : false; return result; } private: friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int /* file_version */){ ar & BOOST_SERIALIZATION_BASE_OBJECT_NVP(OrdBasis); } }; BOOST_CLASS_EXPORT_KEY(Ord<Options>) -----------------------A.HPP------------------------------------------- -----------------------A.CPP------------------------------------------- #include "A.hpp" BOOST_CLASS_EXPORT_IMPLEMENT(Ord<Options>) -----------------------A.CPP------------------------------------------- I serialize with following sequence ---------------------FUNC.CPP------------------------------------------ void serializeFunc() { namespace io = boost::iostreams; typedef std::vector<char> buffer_type; buffer_type buffer; buffer.reserve(2000000); { buffer.clear(); io::stream<io::back_insert_device<buffer_type> > output_stream(buffer); boost::archive::binary_oarchive oa(output_stream, boost::archive::no_header); // begin //if the following lines are commented out then everything works //boost::shared_ptr<Ord<Options>> testOptOrd(new Ord<Options>); //oa & testOptOrd; //end boost::shared_ptr<OrdBasis> testOptOrdB(new Ord<Options>); oa & testOptOrdB; } { io::basic_array_source<char> source(&buffer[0],buffer.size()); io::stream<io::basic_array_source <char> > input_stream(source); boost::archive::binary_iarchive ia(input_stream, boost::archive::no_header); boost::shared_ptr<OrdBasis> testOptOrd; // begin linked to the above code block //ia & testOptOrd; // end ia & testOptOrd; int i = 0; } } -----------------------FUNC.CPP------------------------------------ -- Using Opera's revolutionary email client: http://www.opera.com/mail/

2 3

[Boost.Geometry] - Union generates polygon with punctures
by Olivier Heriveaux 14 Jul '13

14 Jul '13

Hello ! I'm trying to use Boost.Geometry library to implement Minkowsky algorithm (i.e. polygon convolution). I try to implement it in the same way Boost.Polygon does, but during the algorithm execution, a boost::geometry::overlay_invalid_input_exception is raised. It seems that one of the input polygons to the union_ function is invalid. To understand my mistake, I outputed the operand polygons to SVG files and I discovered punctures in one of them. I believe Boost.Geometry thinks my polygon is self-intersecting (may be due to precision error with floats ?) - but this polygon itself is the result of a previous union operation. For info, I attached the SVG file (use inkscape to see it completely since segments are out of the box due to negative coordinates). I don't know if solutions to this problem exists or if the library is faulty (the bad polygon is the result of an union operation). One workaround would be to detect punctures and remove them, but it's kind of ugly imho... Some more details: - point coordinates type is float, - I use custom class instead of point_xy model, - polygon winding is counter-clockwise. Thank you in advance for any help, Olivier

2 5

[multi_index][ann] Boost.MultiIndex 1.55 preview: major update with C++11 capabilities
by Joaquín Mª López Muñoz 14 Jul '13

14 Jul '13

Dear Boost.MultiIndex user: I've completed a major update of Boost.MultiIndex retrievable from the SVN repository, trunk branch, or at: https://www.dropbox.com/s/xipv129az88vgd1/multi_index_130713.zip This update includes many C++11 capabilities (most emulated by various means in pre-C++11 compilers,) among them the following: * multi_index_container is now efficiently movable employee_set extract_employees(const std::string& db); employee_set cont=extract_employees("employees.dat"); // no data copying * Initializer lists supported (if the compiler provides them) employee_set es8{{0,"Rose",40,4512},{1,"Mary",38,3345},{2,"Jo",25,7102}}; * Emplace functions es.emplace(0,"Joe",31,1123); es.get<3>().emplace_back(3,"Judy",39,6201); * Non-copyable elements allowed typeded multi_index_container< std::unique_ptr<employee>, indexed_by<...> > employee_ptr_set; How does this update affect you? 1. Of course, you can now begin using the new capabilities, even in non-C++11 compilers with some limitations (explained at the documentation). 2. Your code can get some transparent performance gain without you doing anything es.insert(employee(4,"Jill",52,3379)); // temporary's moved rather than copied 3. The internal code has been refactored to implement the new features, and this refactoring touches on preexisting functionality, hopefully without producing regressions --this has been thoroughly tested, but: It is now #3 that worries me the most: if you use Boost.MultiIndex and have some time to test this preview with your code, please do so and report the results. The more this update is tested before the official release, the less problems it will cause (ideally none.) As the update is major, every bit of testing helps. Hope you enjoy the new features. Best regards, Joaquín M López Muñoz Telefónica Digital ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx

1 0

Boost.Log SimpleEventLog question
by Pieter 13 Jul '13

13 Jul '13

LS, I am currently configuring my logging configuration using a property tree. When I include a SimpleEventLog sink, how can I apply an event type mapping to that sink? In the stated example this is done before the sink is added to the core: typedef sinks::synchronous_sink< sinks::simple_event_log_backend > sink_t; boost::shared_ptr< sink_t > sink(new sink_t()); sinks::event_log::custom_event_type_mapping< severity_level > mapping("Severity"); // . define mapping here . sink->locked_backend()->set_event_type_mapper(mapping); // Add the sink to the core logging::core::get()->add_sink(sink); but adding the sink happens behind the scenes when using the configuration utilities. BTW, in the section "Simplified library initialization tools" of the documentation Table 1.15 seems to miss a 'Format' parameter that I assume is still needed? Many thanks, Pieter

1 0

[Boost.Log] More queries
by Leo Carreon 13 Jul '13

13 Jul '13

Hi everyone, As I have mentioned in a previous post, I have been trying to learn how to use Boost.Log. I have been experimenting with logging to a file with filtering and specifying the log formatting in three different ways, namely: 1. Specifying the log formatting using a lambda type expression. 2. Specifying the log formatting using a plain text string with placeholders for the attributes that I have defined. 3. Specifying the log formatting in a settings file. (However, the formatting string is exactly the same as in 2 above.) I have attached a copy of my source code and settings file. Note that I comment out parts of the source code file depending on which option I use above. The problem I’m encountering is when I use options 2 & 3 above, the severity level string does not appear in the log. But if I use option 1, the severity level string appears as expected. It is my understanding that severity level is a pre-defined attribute when using a severity_logger. Am I missing something when using options 2 & 3? If I decide to use my own severity level enumeration, what do I need to do? Kind regards, Leo

1 0

Re: [Boost-users] Query on Boost.Log
by Leo Carreon 13 Jul '13

13 Jul '13

From: Leo Carreon Sent: Friday, July 12, 2013 8:42 AM To: Boost Users Mailing List Subject: Query on Boost.Log Hi everyone, I’m trying to learn how to use Boost.Log from Boost 1.54.0 on Fedora 18. When I attempt to call boost::log::init_from_stream() even with BOOST_LOG_DYN_LINK defined, I get the error message”undefined reference to `void boost::log::v2_mt_posix::init_from_stream<char>(std::basic_istream<char, std::char_traits<char> >&)'” for the line where I called the function. Note that I have included the header file “boost/log/utility/setup/from_stream.hpp” and added –lboost_log to my link command line. Am I missing something. I have noticed that boost::log::init_from_stream() is a template. Is an instance of this template added into the shared library? Kind regards, Leo Hi again everyone, FYI. I built Boost 1.54.0 using the following bjam options – link=shared runtime-link=shared I have also checked the build logs from the above and discovered that not all of the .cpp files in libs/log/src have been included during the build. Kind regards, Leo

2 2

[exception] exception_ptr missing virtual base parameters
by Michael Caisse 13 Jul '13

13 Jul '13

The basic problem I'm experiencing is that getting an exception_ptr results inherited parameters getting lost when virtual inheritance is used. The code below demonstrates a simple example. "bar" is lost in the print. Changing derived_except to be: struct derived_except : base_except { int i; }; will cause the inherited values to be copied into the exception_ptr; however, this has all the standard problems associated that come with not using virtual inheritance. This looks like a bug to me. The C++11 equivalent behaves has expected and inherited values are maintained in the exception_ptr. Any thoughts? michael -------------- boost::exception_ptr version -------------- #include <boost/exception/all.hpp> #include <string> #include <iostream> struct base_except { std::string s; }; struct derived_except : virtual base_except { int i; }; int main() { derived_except e; e.i = 8; e.s = "bar"; boost::exception_ptr ptr = boost::copy_exception(e); try { boost::rethrow_exception(ptr); } catch(derived_except & e) { std::cout << "derived_except: " << e.s << " " << e.i << std::endl; } catch(...) {} return 0; } -------------- c++11 version --------------------- #include <exception> #include <string> #include <iostream> struct base_except { std::string s; }; struct derived_except : virtual base_except { int i; }; int main() { derived_except e; e.i = 8; e.s = "bar"; std::exception_ptr ptr = std::make_exception_ptr(e); try { std::rethrow_exception(ptr); } catch(derived_except & e) { std::cout << "derived_except: " << e.s << " " << e.i << std::endl; } catch(...) {} return 0; } -- Michael Caisse ciere consulting ciere.com

3 3

Re: [Boost-users] [graph] in-depth parsing and modifications of the graph
by Orianne Siret 12 Jul '13

12 Jul '13

I mean traverse when i said parse. So the problem is i can't traverse in depth-first order my graph and modify node (or edge) properties. I wrote a basic case which doesn't work. ----------------------------------------- // Begin main.cpp #include <boost/graph/adjacency_list.hpp> #include <boost/graph/depth_first_search.hpp> #include <vector> // Node properties struct MyNode { int node_id; MyNode() : node_id() {} MyNode(int id) : node_id(id) {} }; //Edge Properties struct MyEdge { int edge_id; MyEdge() : edge_id() {} MyEdge(int id) : edge_id(id) {} }; // Graph definition typedef boost::adjacency_list< boost::vecS, boost::vecS, boost::directedS, MyNode, MyEdge > MyGraph; typedef boost::graph_traits<MyGraph>::vertex_descriptor MyGraphVD; //My idiot visitor class my_dfs_visitor : public boost::default_dfs_visitor { public: template < typename Vertex, typename Graph > void discover_vertex(Vertex u, Graph & g) { // here i cant assign 0 to m node_id. however g is not cont.. I didn't find a code with a depth-first traversal and assign ment. g[u].node_id = 0; } }; int main() { MyGraph g; MyGraphVD vd0 = boost::add_vertex(MyNode(0), g); MyGraphVD vd1 = boost::add_vertex(MyNode(1), g); boost::add_edge(vd0, vd1, MyEdge(), g); boost::add_edge(vd1, vd0, MyEdge(), g); my_dfs_visitor visitor; boost::depth_first_search(g, boost::visitor(visitor)); return 0; } // end ------------------------------------------ This code doesn't work. I have the following error : ../main.cpp:35:3: erreur: assignment of member 'MyNode::node_id' in read-only object. (I do: "g++ -O3 -Wall -c -o main.o main.cpp " for compilation, i run on linux ubuntu 12.04 with gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3) I didn't find any example on the web.. Thanks for spending time on my problem. It is very nice of you. Best regards. Orianne Siret

2 1

BOOST_STATIC_ASSERT with boost::array.static_size
by Anton Daneyko 12 Jul '13

12 Jul '13

Dear boost users, could someone tell me why this short program does not compile? #include <boost/array.hpp> #include <boost/static_assert.hpp> int main(int argc, const char *argv[]) { boost::array<int, 3> a1 = {{1, 1, 1}}; BOOST_STATIC_ASSERT(a1.static_size == 3); return 0; } With g++ (4.3.4) I get the following error: tmp.cpp: In function ‘int main(int, const char**)’: tmp.cpp:7: error: ‘a1’ cannot appear in a constant-expression tmp.cpp:7: error: `.' cannot appear in a constant-expression tmp.cpp:7: error: template argument 1 is invalid With icc (12.1.6) I get the following error: tmp.cpp(7): error: this operator is not allowed in a template argument expression BOOST_STATIC_ASSERT(a1.static_size == 3); ^ tmp.cpp(7): error: incomplete type is not allowed BOOST_STATIC_ASSERT(a1.static_size == 3); ^ compilation aborted for tmp.cpp (code 2) However I can compile using IBM xlC compiler. I thought that static_size is a compile time constant and can be used in this context...

2 1

Query on Boost.Log
by Leo Carreon 11 Jul '13

11 Jul '13

Hi everyone, I’m trying to learn how to use Boost.Log from Boost 1.54.0 on Fedora 18. When I attempt to call boost::log::init_from_stream() even with BOOST_LOG_DYN_LINK defined, I get the error message”undefined reference to `void boost::log::v2_mt_posix::init_from_stream<char>(std::basic_istream<char, std::char_traits<char> >&)'” for the line where I called the function. Note that I have included the header file “boost/log/utility/setup/from_stream.hpp” and added –lboost_log to my link command line. Am I missing something. I have noticed that boost::log::init_from_stream() is a template. Is an instance of this template added into the shared library? Kind regards, Leo

1 0

Procedure entry point _ZNSt16invalid_argumentD2Ev could not be located in the dynamic link library libstdc++-6.dll
by Joe Hays 11 Jul '13

11 Jul '13

Hello all, I have a newbie question for you. I'm trying Boost for the very first time. I'm also not terribly experienced with C++. I'm using, Eclipse Kepler (latest) Mingw 3.20 (latest) Boost_1_54_0 on a 64-bit Windows 7 machine. I followed this tutorial to configure Boost to be used with Mingw and Eclipse: http://theseekersquill.wordpress.com/2010/08/24/howto-boost-mingw/ Sections 1-6 performed as expected. The 7th and final step is when a "hello world" like application finally compiles and links Boost into a .exe. I cut-n-paste the following code from Boost's Getting Started tutorial ( http://www.boost.org/doc/libs/1_54_0/more/getting_started/windows.html) <snip> #include <boost/regex.hpp> #include <iostream> #include <string> int main() { std::string line; boost::regex pat( "^Subject: (Re: |Aw: )*(.*)" ); while (std::cin) { std::getline(std::cin, line); boost::smatch matches; if (boost::regex_match(line, matches, pat)) std::cout << matches[2] << std::endl; } } </snip> The output of the build is, <snip> 12:20:46 **** Rebuild of configuration Debug for project BoostRegexExample1 **** Info: Internal Builder is used for build g++ "-Ic:\\boost_1_54_0" -O0 -g3 -Wall -c -fmessage-length=0 -o BoostRegexExample1.o "..\\BoostRegexExample1.cpp" g++ "-LC:\\boost_1_54_0\\stage\\lib" -o BoostRegexExample1.exe BoostRegexExample1.o -lboost_regex-mgw46-mt-1_54 12:20:52 Build Finished (took 5s.992ms) </snip> If I try to run that application within Eclipse the terminal simply states the application terminated. If I go to a terminal and run the .exe (using a text file as in input as directed in the Getting Started document) I get, *"Procedure entry point _ZNSt16invalid_argumentD2Ev could not be located in the dynamic link library libstdc++-6.dll"* Any ideas why this is happening? And, what I can do to get past this? Thanks, Joe

2 2

boost::uuid
by John Emmas 11 Jul '13

11 Jul '13

Hello there, I'm developing an app (originally written for Linux) which uses some UUID functionality that originally came from a set of e2fs utilities for Linux. I'm porting the app to Windows so naturally, the e2fs stuff doesn't build. I need to find a UUID implemntation that's more cross-platform - and of course, the obvious one to try is boost::uuid. I first installed boost when it was at version 1.40 (1-2 years ago?) Anyway, my installed version doesn't include UUID so I decided to update to a more recent version. The most recent Windows installer I could find was for version 1.51, from BoostPro:- http://www.boostpro.com/download/ Unfortunately, it probably isn't the absolute latest because BoostPro is apparently now discontinued - but it should be recent enough to include the UUID modules. From what I can gather, boost::uuid has been around since at least version 1.42. However, I hit a couple of problems:- 1) Firstly, I seem to get errors, no matter which mirror I use. I'll try again later, in case the errors go away. 2) Despite the errors, something does seem to get downloaded. However, rather than installing all the source files / DLLs etc, I just get a subdirectory called "lib" which contains a bunch of zip files (over 100). My original (1.40) installation seemed to unpack everything for me. 3) AFAICT even ver 1.51 doesn't include any UUID functionality. There was nothing for UUID that was selectable in the installer - and none of the modules look like UUID. I seem to have boost::regex, boost::filesystem, boost:date_time and a whole load of other stuff - but no boost::uuid :-( I then came across this web page which seems to suggest that all I need to do is add one header file to my existing installation (boost/uuid.hpp). Am I over-thinking this?? Is that all there is to it?? Thanks. John

3 3

[graph] in-depth parsing and modifications of the graph
by Orianne Siret 11 Jul '13

11 Jul '13

Hello, I would like to know if it is possible to parse a boost graph in depth while being able to modify the properties of the verices you parse ? I saw there is a in-depth parser but it seems to not allow the modifications of properties ? Thanks in advance for your help ! Orianne Siret

2 1

[asio] Incorrect reporting of bytes transferred in write handler in 1.54
by Darren 11 Jul '13

11 Jul '13

Is anybody else seeing problems with the bytes_transferred reported to the write_handler after a successful async_write? I am seeing a value of zero despite the fact that the peer receives the bytes and no error is reported to the write_handler. My example code when built against 1.54 exhibits the problem whereas building against 1.53 works correctly. I am running on Windows 7 with MSVC 2010. A couple of notes: * I only see the problem when the number of threads is > 1, even though the handlers are invoked on a strand. * Defining BOOST_ASIO_DISABLE_IOCP makes everything work properly. When running my code a failure shows itself like this: Client: Writing value 85 Server: Received 4 bytes, value 85 Client: bytesWritten = 0 In other words, the client used async_write to send 4 bytes with long value 85 the server. The server received these bytes. The client write_handler was called with no error but a bytes_transferred value of 0. Is there something I don't understand or is this a problem introduced in 1.54? #include <boost/asio.hpp> #include <boost/thread.hpp> #include <boost/thread/mutex.hpp> #include <iostream> using namespace boost::asio; const std::size_t NumThreads = 2; const unsigned short Port = 12345; // Prevent interleaved output boost::mutex logMutex; struct Server { Server(io_service& svc) : m_socket(svc), m_acceptor(svc, ip::tcp::endpoint(ip::tcp::v4(), Port)), m_buffer(0) { } void Run() { m_acceptor.accept(m_socket); // Simple blocking reads while(std::size_t bytesRead = read(m_socket, buffer(&m_buffer, sizeof(m_buffer)))) { boost::mutex::scoped_lock lock(logMutex); std::cout << "Server: Received " << bytesRead << " bytes, value " << m_buffer << std::endl; } } ip::tcp::socket m_socket; ip::tcp::acceptor m_acceptor; unsigned long m_buffer; }; struct Client { Client(io_service& svc) : m_strand(svc), m_socket(svc), m_buffer(0) { m_socket.connect( ip::tcp::endpoint(ip::address_v4::from_string("127.0.0.1"), Port)); ScheduleWrite(); } void WriteHandler(const boost::system::error_code& err, std::size_t bytesWritten) { assert(!err); if(bytesWritten != sizeof(m_buffer)) { boost::mutex::scoped_lock lock(logMutex); std::cout << "Client: bytesWritten = " << bytesWritten << std::endl; return; } ScheduleWrite(); } void ScheduleWrite() { { boost::mutex::scoped_lock lock(logMutex); std::cout << "Client: Writing value " << ++m_buffer << std::endl; } async_write(m_socket, buffer(&m_buffer, sizeof(m_buffer)), m_strand.wrap( std::bind(&Client::WriteHandler, this, std::placeholders::_1, std::placeholders::_2))); } io_service::strand m_strand; ip::tcp::socket m_socket; unsigned long m_buffer; }; int main(int argc, char* argv[]) { boost::asio::io_service svc; Server server(svc); Client client(svc); boost::thread_group threads; for(int n = 0; n < NumThreads; ++n) threads.create_thread(std::bind(&io_service::run, &svc)); server.Run(); return 0; }

2 1

Using boost with cray c++
by avib369 . 11 Jul '13

11 Jul '13

Does any one have any experience of using boost with cray C++ compiler ? Are any known problematic areas/issues ? Ok I know its not in the official list of supported compilers, but neither is the HPUX acc, which seems to work fine for most libs. Any help appreciated . Ta, Avi

2 1

[Boost.Log] Some few newbee questions
by Ovanes Markarian 10 Jul '13

10 Jul '13

Hi *, Thanks for the really great logging library. Just used it a bit and was amazed how useful and easy to use it was. As I start using it more and more I have some questions... 1. In my application I would like to start with the trivial logger and extend this logger with more options, i.e. attributes etc. Currently I see the following input when doing a trace: [2013-07-03 22:17:32.462265] [0x76f73180] [trace] thread_pool: creating 1 threads[2013-07-03 22:17:32.462303] [0x76f73180] [trace] thread_pool: created thread number: 1[2013-07-03 22:17:32.462312] [0x76f73180] [trace] thread_pool: all threads started[2013-07-03 22:17:32.462320] [0x76f73180] [trace] thread_pool: constructor finished My question is what is the second attribute? Thread id? As my code runs on a 64bit machine, that does not seem to be an address... 2. Is it possible to use a scoped logging with the trivial logger? I tried to do it as described in the example but see not output. How can I produce the output from the scoped logger? 3. In my example I wrote thread_pool prefix before each log entry. Can I do it automatically? How would I go on if I only have trivial logging? May be I misunderstand some concepts, like how to use multiple loggers and connect them with each other? Any help is very appreciated. Thanks, Ovanes

2 2

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

09 Jul '13

"It's not an easy task. You should catch the exception and then notify all connected processes that should disconnected from the segment (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, thank you for that, I see.... 1. Can I ask what mechanism you would suggest for notifying the other processes to disconnect before the grow() operation? 2. Considering how to deal with the issue of dynamically growing a shared memory vector where there is one producer process and several consumers; I hit upon the notion of having the producer process use a std::vector to conventionally store data and then using a boost shared memory segment to store a pointer to the std::vector. Consumer processes would access the boost shared memory to retrieve the pointer value thus enabling access to the std::vector data store in the producer process. This, I hoped, might remove the complexities associated with dynamically growing a shared memory segment? The big question is: would it work? Would this be a valid means of interprocess communication? Or fraught with complexities? Thanks, Riskybiz.

2 1

[msm] interrupt_state with more then one event that ends interrupt?
by Alexander Mingalev 09 Jul '13

09 Jul '13

Hi, Subj, Is that possible? for example, one event continues processing, the another one finishes the whole state-machine (some clean-up actions etc). I tried struct Interrupt : public msmf::interrupt_state< boost::mpl::vector<Foo, Bar> > {}; and struct Interrupt : public msmf::interrupt_state< msmf::ActionSequence_< boost::mpl::vector<Foo, Bar> > > {}; - has no effect. Is there another way to achieve this?

3 5

[msm] interrupt_state with more then one event that ends interrupt?
by Sam Fisher 09 Jul '13

09 Jul '13

Hi, Subj, Is that possible? for example, one event continues processing, the another one finishes the whole state-machine (some clean-up actions etc). I tried struct Interrupt : public msmf::interrupt_state< boost::mpl::vector<Foo, Bar> > {}; and struct Interrupt : public msmf::interrupt_state< msmf::ActionSequence_< boost::mpl::vector<Foo, Bar> > > {}; - has no effect. Is there another way to achieve this?

1 1

Boost.MultiIndex template substitution failure?
by fredbaba 08 Jul '13

08 Jul '13

I'm attempting to use boost::multi_index_container and it seems to be choking on the template metaprogramming magic somewhere. I'm getting a massive error dump ending in: /opt/local/include/boost/multi_index/hashed_index.hpp:743:9: error: ‘class boost::multi_index::detail::hashed_index, boost::hash, std::equal_to, boost::multi_index::detail::nth_layer<1, boost::intrusive_ptr, boost::multi_index::indexed_by >, boost::multi_index::ordered_non_unique, &md::Order::px> > >, std::allocator > >, boost::mpl::vector0, boost::multi_index::detail::hashed_unique_tag>’ has no member named ‘final_delete_node_’ this->final_delete_node_( I'm using Boost 1.53 (MacPorts) on Mac OS X.8 Mountain Lion. How do I get the following code to compile? Thanks. p.s. I originally posted this question on StackOverflow <http://stackoverflow.com/questions/17536227/boost-multiindex-template-subst…> but thought this might be a better forum. Sorry for the cross-post... #include <boost/multi_index_container.hpp> #include <boost/multi_index/hashed_index.hpp> #include <boost/multi_index/mem_fun.hpp> #include "Product.hpp" #include <iostream> int main(int argc, char* argv[]) { boost::multi_index_container< boost::intrusive_ptr<Product>, boost::multi_index::indexed_by< boost::multi_index::hashed_unique< boost::multi_index::const_mem_fun< Product, id_t, static_cast<id_t (Product::*)() const>(&Product::id) > >, boost::multi_index::ordered_non_unique< boost::multi_index::const_mem_fun< Product, price_t, static_cast<price_t (Product::*)() const>(&Product::price) > > > > cont; auto o = boost::intrusive_ptr<Product>(new Product()); o->id(1).price(price_t(14.75)); cont.insert(o); auto it = cont.get<1>().find(price_t(14.75)); if (it!=cont.get<1>().end()) std::cout << *(it); return 0; } -- View this message in context: http://boost.2283326.n4.nabble.com/Boost-MultiIndex-template-substitution-f… Sent from the Boost - Users mailing list archive at Nabble.com.

2 1

Incorrect result from mcgregor_common_subgraphs. Where can I find more example of this MCS solver?
by dante0125 08 Jul '13

08 Jul '13

Hi, I am a beginner with BGL. Currently I am using mcgregor_common_subgraphs solver to find all the common subgraphs between two graphs. The following link is the only one example showing how to use the library that I can find from the Internet. http://svn.kulitorum.com/RepSnapper/Libraries/Boost1.40/libs/graph/example/… My first question is where can I find more example of this MCS solver? My second question is why some times it can not find maximum common subgraph. By maximum I mean a common subgraph with largest number of vertices which is implemented in the code. Here I provide an example. This code is modified from mcgregor_subgraphs_example, I change the graph to undirected graph and add some vetices and edges. It is obvious that the correct answer should be of size 9. The answer return by the code missing edge 8-5 and 8-3. //======================================================================= // Copyright 2009 Trustees of Indiana University. // Authors: Michael Hansen // // Distributed under the Boost Software License, Version 1.0. (See // accompanying file LICENSE_1_0.txt or copy at // http://www.boost.org/LICENSE_1_0.txt) //======================================================================= #include <fstream> #include <iostream> #include <string> #include <boost/lexical_cast.hpp> #include <boost/graph/adjacency_list.hpp> #include <boost/graph/filtered_graph.hpp> #include <boost/graph/graph_utility.hpp> #include <boost/graph/iteration_macros.hpp> #include <boost/graph/mcgregor_common_subgraphs.hpp> #include <boost/property_map/shared_array_property_map.hpp> using namespace boost; // Callback that looks for the first common subgraph whose size // matches the user's preference. template <typename Graph> struct example_callback { typedef typename graph_traits<Graph>::vertices_size_type VertexSizeFirst; example_callback(const Graph& graph1) : m_graph1(graph1) { } template <typename CorrespondenceMapFirstToSecond, typename CorrespondenceMapSecondToFirst> bool operator()(CorrespondenceMapFirstToSecond correspondence_map_1_to_2, CorrespondenceMapSecondToFirst correspondence_map_2_to_1, VertexSizeFirst subgraph_size) { // Fill membership map for first graph typedef typename property_map<Graph, vertex_index_t>::type VertexIndexMap; typedef shared_array_property_map<bool, VertexIndexMap> MembershipMap; MembershipMap membership_map1(num_vertices(m_graph1), get(vertex_index, m_graph1)); fill_membership_map<Graph>(m_graph1, correspondence_map_1_to_2, membership_map1); // Generate filtered graphs using membership map typedef typename membership_filtered_graph_traits<Graph, MembershipMap>::graph_type MembershipFilteredGraph; MembershipFilteredGraph subgraph1 = make_membership_filtered_graph(m_graph1, membership_map1); // Print the graph out to the console std::cout << "Found common subgraph (size " << subgraph_size << ")" << std::endl; print_graph(subgraph1); std::cout << std::endl; // Explore the entire space return (true); } private: const Graph& m_graph1; VertexSizeFirst m_max_subgraph_size; }; int main (int argc, char *argv[]) { // Using a vecS graph here so that we don't have to mess around with // a vertex index map; it will be implicit. typedef adjacency_list<listS, vecS, undirectedS, property<vertex_name_t, unsigned int, property<vertex_index_t, unsigned int> >, property<edge_name_t, unsigned int> > Graph; typedef graph_traits<Graph>::vertex_descriptor Vertex; typedef graph_traits<Graph>::edge_descriptor Edge; typedef property_map<Graph, vertex_name_t>::type VertexNameMap; typedef property_map<Graph, edge_name_t>::type EdgeNameMap; // Test maximum and unique variants on known graphs Graph graph_simple1, graph_simple2; example_callback<Graph> user_callback(graph_simple1); VertexNameMap vname_map_simple1 = get(vertex_name, graph_simple1); VertexNameMap vname_map_simple2 = get(vertex_name, graph_simple2); // Graph that looks like a triangle put(vname_map_simple1, add_vertex(graph_simple1), 1); put(vname_map_simple1, add_vertex(graph_simple1), 2); put(vname_map_simple1, add_vertex(graph_simple1), 3); put(vname_map_simple1, add_vertex(graph_simple1), 4); put(vname_map_simple1, add_vertex(graph_simple1), 5); put(vname_map_simple1, add_vertex(graph_simple1), 6); put(vname_map_simple1, add_vertex(graph_simple1), 7); put(vname_map_simple1, add_vertex(graph_simple1), 8); put(vname_map_simple1, add_vertex(graph_simple1), 9); add_edge(0, 1, graph_simple1); add_edge(0, 2, graph_simple1); add_edge(0, 4, graph_simple1); add_edge(1, 2, graph_simple1); add_edge(1, 3, graph_simple1); add_edge(1, 6, graph_simple1); add_edge(2, 3, graph_simple1); add_edge(2, 4, graph_simple1); add_edge(3, 5, graph_simple1); add_edge(4, 5, graph_simple1); add_edge(5, 6, graph_simple1); add_edge(7, 8, graph_simple1); add_edge(6, 7, graph_simple1); add_edge(8, 5, graph_simple1); add_edge(8, 3, graph_simple1); std::cout << "First graph:" << std::endl; print_graph(graph_simple1); std::cout << std::endl; // Triangle with an extra vertex put(vname_map_simple2, add_vertex(graph_simple2), 1); put(vname_map_simple2, add_vertex(graph_simple2), 2); put(vname_map_simple2, add_vertex(graph_simple2), 3); put(vname_map_simple2, add_vertex(graph_simple2), 4); put(vname_map_simple2, add_vertex(graph_simple2), 5); put(vname_map_simple2, add_vertex(graph_simple2), 6); put(vname_map_simple2, add_vertex(graph_simple2), 7); put(vname_map_simple2, add_vertex(graph_simple2), 8); put(vname_map_simple2, add_vertex(graph_simple2), 9); add_edge(0, 1, graph_simple2); add_edge(0, 2, graph_simple2); add_edge(0, 4, graph_simple2); add_edge(1, 2, graph_simple2); add_edge(1, 5, graph_simple2); add_edge(2, 4, graph_simple2); add_edge(3, 5, graph_simple2); add_edge(3, 6, graph_simple2); add_edge(7, 8, graph_simple2); add_edge(1, 6, graph_simple2); add_edge(6, 7, graph_simple2); add_edge(8, 5, graph_simple2); add_edge(8, 3, graph_simple2); std::cout << "Second graph:" << std::endl; print_graph(graph_simple2); std::cout << std::endl; // Maximum subgraphs // Maximum, unique subgraphs std::cout << "mcgregor_common_subgraphs_unique:" << std::endl; mcgregor_common_subgraphs_unique (graph_simple1, graph_simple2, true, user_callback, vertices_equivalent(make_property_map_equivalent(vname_map_simple1, vname_map_simple2))); std::cin.get(); return 0; } -- View this message in context: http://boost.2283326.n4.nabble.com/Incorrect-result-from-mcgregor-common-su… Sent from the Boost - Users mailing list archive at Nabble.com.

2 2

Re: [Boost-users] boost::io_service run() never returns
by Marat Abrarov 07 Jul '13

07 Jul '13

Not sure if this can help, but there was a problem with serial port (asynchronous reading, maybe epoll-related) at Ubuntu. That problem wasn't related to Asio, it was an OS bug. Search asio-users mailing list for details. Regards, Marat Abrarov.

1 0

Different behavior of boost::serialization of strings on text archive
by Andrea Ranieri 07 Jul '13

07 Jul '13

Hi all, I'm having some issue serializing a `std::string` with `boost::serialization` on a `text_oarchive`. AFAICT, I have two identical pieces of code that behaves differently in two different programs. This is the program that I believe is behaving correctly: #include <iostream> #include <string> #include <sstream> #include <boost/archive/text_iarchive.hpp> #include <boost/archive/text_oarchive.hpp> template <typename T> void serialize_deserialize(const T & src, T & dst) { std::string serialized_data_str; std::cout << "original data: " << src << std::endl; std::ostringstream archive_ostream; boost::archive::text_oarchive oarchive(archive_ostream); oarchive << src; serialized_data_str = archive_ostream.str(); std::cout << "serialized data: " << serialized_data_str << std::endl; std::istringstream archive_istream(serialized_data_str); boost::archive::text_iarchive iarchive(archive_istream); iarchive >> dst; } int main() { std::string archived_data_str = "abcd"; std::string restored_data_str; serialize_deserialize<std::string>(archived_data_str, restored_data_str); std::cout << "restored data: " << restored_data_str << std::endl; return 0; } And this is its output: original data: abcd serialized data: 22 serialization::archive 10 4 abcd restored data: abcd (You can compile it with: `g++ boost-serialization-string.cpp -o boost-serialization-string -lboost_serialization`) This one, on the other hand, is an excerpt of the program I'm writing (derived from [boost_asio/example/serialization/connection.hpp][1]) that serializes `std::string` data converting each character in its hex representation: /// Asynchronously write a data structure to the socket. template <typename T, typename Handler> void async_write(const T& t, Handler handler) { // Serialize the data first so we know how large it is. std::cout << "original data: " << t << std::endl; std::ostringstream archive_stream; boost::archive::text_oarchive archive(archive_stream); archive << t; outbound_data_ = archive_stream.str(); std::cout << "serialized data: " << outbound_data_ << std::endl; [...] And this is an excerpt of its output: original data: abcd serialized data: 22 serialization::archive 10 5 97 98 99 100 0 The version (`10`) is the same, right? So that should be the proof that I'm using the same serialization library in both programs. However, I really can't figure out what's going on here. I've been trying to solve this puzzle for almost an entire work day now, and I'm out of ideas. For anyone that may want to reproduce this result, it should be sufficient to download the [Boost serialization example][2], add the following line connection_.async_write("abcd", boost::bind(&client::handle_write, this, boost::asio::placeholders::error)); at line 50 of `client.cpp`, add the following member function in client.cpp /// Handle completion of a write operation. void handle_write(const boost::system::error_code& e) { // Nothing to do. The socket will be closed automatically when the last // reference to the connection object goes away. } add this `cout`: std::cout << "serialized data: " << outbound_data_ << std::endl; at `connection.hpp:59` and compile with: g++ -O0 -g3 client.cpp -o client -lboost_serialization -lboost_system g++ -O0 -g3 server.cpp -o server -lboost_serialization -lboost_system I'm using `g++ 4.8.1` under `Ubuntu 13.04 64bit` with `Boost 1.53` Any help would be greatly appreciated. Best regards Avio P.s. I'm posting this because the deserialization of the `std::string`s isn't working at all! :) [1]: http://www.boost.org/doc/libs/1_53_0/doc/html/boost_asio/example/serializat… [2]: http://www.boost.org/doc/libs/1_53_0/doc/html/boost_asio/examples.html#boos…

5 4

boost::io_service run() never returns
by shunguang 06 Jul '13

06 Jul '13

I have the following simplified code to read data from a RS232 port. For some (from beginning) runs, io.run() returns immediately and m_handler() is called which is expected. but sometimes (a fresh run from beginning), io.run() goes into a inside forever loop(stacked inside forever) even for the first time called inside the while loop. And this happens randomly. What's is/are the potential problem(s) at here? Thanks. -shunguang #define BUF_SIZE 512 char data[BUF_SIZE]; void my_handler(const boost::system::error_code& err, std::size_t bytes_transferred) { printf("%d\n", bytes_transferred); if (!err){ process_data(); } } void test_serial_port( int argc, char* argv[] ) { // hard coded parameters const char *PORT = "COM1"; serial_port_base::baud_rate BAUD(9600); serial_port_base::character_size CSIZE( 8 ); serial_port_base::flow_control FLOW( serial_port_base::flow_control::software ); serial_port_base::parity PARITY( serial_port_base::parity::none ); serial_port_base::stop_bits STOP( serial_port_base::stop_bits::one ); io_service io; serial_port port( io, PORT ); // go through and set all the options as we need them // all of them are listed, but the default values work for most cases port.set_option( BAUD ); port.set_option( CSIZE ); port.set_option( FLOW ); port.set_option( PARITY ); port.set_option( STOP ); while( !kbhit() ) { io.reset(); port.async_read_some( boost::asio::buffer(data, BUF_SIZE), boost::bind(&my_handler, boost::asio::placeholders::error, boost::asio::placeholders::bytes_transferred ) ); io.run(); Sleep(300); } } -- View this message in context: http://boost.2283326.n4.nabble.com/boost-io-service-run-never-returns-tp464… Sent from the Boost - Users mailing list archive at Nabble.com.

2 4

[filesystem] current_path
by Ovanes Markarian 06 Jul '13

06 Jul '13

Hello *, I need to create a relative symlink. To do so I currently use current_path function: auto current_path = fs::current_path(); BOOST_SCOPE_EXIT(&current_path) { fs::current_path(current_path); }BOOST_SCOPE_EXIT_END fs::current_path(some_base_path_here); fs::create_symlink ( fs::path("..")/some_subdirectory/image_name.filename() , original_name.filename() ) ; Is there any better way to create a relative symlink? What happens if I call current_path(whatever) in a multi-threaded environment? Is it thread-safe or should I synchronize the access to it? Many thanks, Ovanes

1 0

[multi_index] emplace support
by Brian Wood 06 Jul '13

06 Jul '13

I'm wondering about emplace support in multi_index. Any news on that is of interest. -- Brian Ebenezer Enterprises - In G-d we trust. http://webEbenezer.net

2 2

Re: [Boost-users] Do correct instructions for MinGW install exist?
by lizy10b 06 Jul '13

06 Jul '13

Hi Kirk Joppy, I have got most of the 1.53 libraries built with MinGW, though some of them do not work correctly till now. I would like to share with you the following steps I did. 1. Add the bin folder of MinGW to your windows environment variable "PATH". 2. Open a the new commandline window, and type "bootstrap.bat mingw" in the boost souce root dir to build the b2.exe and bjam.exe. 3. Type "b2 toolset=gcc --prefix=G:\boost_1_53_0\my-build' to build the libraries. Hope it works. cheers. Zhiyu Li 2013-07-02 lizy10b 发件人： Kirk Joppy 发送时间： 2013-07-02 12:12:50 收件人： boost 抄送：主题： [Boost-users] Do correct instructions for MinGW install exist? Dear Boost users, I have recently been trying to install boost 1.53 for use with MinGW. I followed the instructions here http://www.boost.org/doc/libs/1_53_0/more/getting_started/windows.html#prep… to the letter with resulting failure. I then noticed that when running b2 install --prefix=G:\boost_1_53_0\my-build from G:\boost_1_53_0\tools\build\v2 as per the instructions, the first few lines of output read warning: No toolsets are configured warning: Configuring default toolset "msvc" warning: If the defrault is wrong, your build may not work correctly warning: Use the "toolset=xxxxx" option to override our guess warning: For more configuration options, please consult <webpage> I have consulted the recommended web page and I think I have gotten a working install. However, given that the instructions as written are incorrect I would like to ask 1. Is there a correct, definitive source of instructions for installing boost (with MinGW)? 2. Should the documentation be corrected? I think this error is important given that the section I was working from is specifically indicated to pertain to non-MSVC builds. 3. I have found several conflicting sources of information regarding how to build boost for use with static linking. StackOverflow, for example, has several posts about this, none of which agree with each other. Is there are definitive, correct source of this information? If not I suppose I will post to this mailing list asking about it. Thank you for your consideration. Regards, kjoppy _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

8 19

[MSM] Problem with passing event as a reference to base event class
by samriti katoch 05 Jul '13

05 Jul '13

Hi, I have noticed a strange problem with event processing with msm. My events derive publicly from a base events struct like this: struct BaseEvent { virtual ~BaseEvent() {} }; struct ConcreteEvent : public BaseEvent {}; I my FSM i have a transition defined for ConcreteEvent, When I do this : void foo(const BuddyEvent& event) { fsm->process_event(event); // event is of type ConcreteEvent } The fsm fires a no_transition , and I see a message saying no transition for ConcreteEvent in state X (state X has a valid transition for ConcreteEvent) However this succeeds: void foo(const BuddyEvent& event) { fsm->process_event(ConcreteEvent(0); } I am using boost-1.49 and the boost msm library that comes bundled with this. So my question is, why is msm not able to generate a valid transition for a concrete event passed as a reference to its base tyoe. Thanks!

2 1

Any special differences between unix and windows source code packages?
by lizy10b 05 Jul '13

05 Jul '13

Hi there, I would like to know are there any differences (other than compression types) between the unix platform source code package (.tar.bz2, tar.gz) and windows platform ones (.7z, .zip) ? PlatformFile unixboost_1_54_0.tar.bz2 boost_1_54_0.tar.gz windowsboost_1_54_0.7z boost_1_54_0.zip Thanks. Zhiyu Li 2013-07-02 lizy10b

5 5

mapped_file::close()
by Millman, Mark 04 Jul '13

04 Jul '13

In Windows using VisualStudio 10 I've created a mapped_file as char * OpenRW(std::string filePath ) { <<fragment >> mfp = new boost::iostreams::mapped_file_params(filePath); mfp->mode = boost::iostreams::mapped_file::readwrite; mfp->new_file_size = size; mfp->offset = 0; mf = new boost::iostreams::mapped_file(*mfp); return mf->data(); } I later close the file void Close() { <<fragment>> mf->close(); delete mfp; delete mf; } And then want to reopen it { char* fileName = filePath.c_str(); int test = _open(fileName,_O_BINARY|_O_RDWR); } but test is returned -1 -- note that I am able to open the file _O_RDONLY. If I close the application and restart it, then I can read the file _O_RDWR (i.e. test is returned with a valid handle) Is this a bug or am I doing something wrong? Thanks Mark

1 0

undefined reference to Thread ( Newbie )
by Sahil Sachdeva 04 Jul '13

04 Jul '13

Hello all, I am trying to compile and use the Boost 1.54 libraries and have run into a dead end. I compiled and installed the libraries like mentioned in the documentation: ./bootstrap.sh./b2 install I even tried a complete reinstall using: ./bootstrap.sh./b2 threading=multi install I have linked using -lboost_thread and -L<path to boost>/bin.v2/libs. boost_system is also linked in the same manner. i am still getting the following linker errors: undefined reference to boost::thread::start_thread_noexcept() undefined reference to boost::thread::join_noexcept() I am using gcc 4.6.3 on Ubuntu 12.04 in eclipse. Does anyone know how i can fix this? Best, Sahil

2 1

[Boost.Math special functions] Critical error in zeta.hpp, Boost 1.54.0
by Rainer Deyke 04 Jul '13

04 Jul '13

I'm getting compile errors when including "boost/math/special_functions/zeta.hpp" (which in turn is included indirectly by "boost/random.hpp"). This is in the recently released "boost_1_54_0.tar.bz2" under Linux Mint 16 for amd64, gcc 4.7.3. Minimal test case: #include "boost/math/special_functions/zeta.hpp" int main() {} Exact error message: In file included from source/eldwood/test/zeta.cpp:1:0: intermediate/usr_x86_64-pc-linux-gnu/include/boost/math/special_functions/zeta.hpp: In function ‘T boost::math::detail::zeta_imp(T, T, const Policy&, const Tag&)’: intermediate/usr_x86_64-pc-linux-gnu/include/boost/math/special_functions/zeta.hpp:877:24: error: ‘log_root_two_pi’ is not a member of ‘boost::math::constants’ intermediate/usr_x86_64-pc-linux-gnu/include/boost/math/special_functions/zeta.hpp:877:52: error: expected primary-expression before ‘,’ token intermediate/usr_x86_64-pc-linux-gnu/include/boost/math/special_functions/zeta.hpp:877:60: error: expected primary-expression before ‘>’ token intermediate/usr_x86_64-pc-linux-gnu/include/boost/math/special_functions/zeta.hpp:877:62: error: expected primary-expression before ‘)’ token The same error also manifests under clang. -- Rainer Deyke (rainerd(a)eldwood.com)

3 2

Boost 1.54.0: bootstrap build fails for MinGW/MSYS
by Josue Andrade Gomes 04 Jul '13

04 Jul '13

Hi, Bjam build is failing for me on MinGW/MSYS. ================================================================================ Boost 1.54.0: $ cd boost_1_54_0/tools/build/v2/engine $ ./build.sh mingw ### ### Using 'mingw' toolset. ### rm -rf bootstrap mkdir bootstrap gcc -DNT -o bootstrap/jam0 command.c compile.c constants.c debug.c execcmd.c frames.c function.c glob.c hash.c hdrmacro.c headers.c jam.c jambase.c jamgram.c lists.c make.c make1.c object.c option.c output.c parse.c pathsys.c pathunix.c regexp.c rules.c scan.c search.c subst.c timestamp.c variable.c modules.c strings.c filesys.c builtins.c class.c cwd.c native.c md5.c w32_getreg.c modules/set.c modules/path.c modules/regex.c modules/property-set.c modules/sequence.c modules/order.c execnt.c filent.c ./bootstrap/jam0 -f build.jam --toolset=mingw --toolset-root= clean ...found 1 target... ...updating 1 target... ...updated 1 target... ./bootstrap/jam0 -f build.jam --toolset=mingw --toolset-root= don't know how to make modules/set.c don't know how to make modules/path.c don't know how to make modules/regex.c don't know how to make modules/property-set.c don't know how to make modules/sequence.c don't know how to make modules/order.c ...found 126 targets... ...updating 1 target... ...can't find 6 targets... ...can't make 2 targets... failed to write command file! ================================================================================ Boost 1.53.0: $ cd boost_1_53_0/tools/build/v2/engine $ ./build.sh mingw ### ### Using 'mingw' toolset. ### rm -rf bootstrap mkdir bootstrap gcc -DNT -o bootstrap/jam0 command.c compile.c constants.c debug.c function.c glob.c hash.c hdrmacro.c headers.c jam.c jambase.c jamgram.c lists.c make.c make1.c object.c option.c output.c parse.c pathunix.c regexp.c rules.c scan.c search.c subst.c timestamp.c variable.c modules.c strings.c filesys.c builtins.c pwd.c class.c native.c md5.c w32_getreg.c modules/set.c modules/path.c modules/regex.c modules/property-set.c modules/sequence.c modules/order.c execnt.c filent.c ./bootstrap/jam0 -f build.jam --toolset=mingw --toolset-root= clean ...found 1 target... ...updating 1 target... ...updated 1 target... ./bootstrap/jam0 -f build.jam --toolset=mingw --toolset-root= ...found 50 targets... ...updating 3 targets... [MKDIR] bin.ntx86 [COMPILE] bin.ntx86\b2.exe [COPY] bin.ntx86\bjam.exe ...updated 3 targets... Any idea? Thanks & regards josue -- Josue Andrade Gomes josuegomes.com

2 2

async processing issues
by SRD 04 Jul '13

04 Jul '13

Having a tough time learning ASIO. I'm trying to have one thread constantly listen for new file monitoring events (mthread) while another thread processes one task at a time (wthread). Somehow I'm still losing events that don't get placed on the task_queue and it would seem that once an event is lost, the file_handler callback for the dir_monitor stops working thereafter for good. So I'm having a few issues with my solution. If I comment out the sleep() method below, then for some reason the first two lines that have to do with the dir_monitor immediately after the while loop quickly eat through all available memory and the program will soon crash within a minute or two. Leaving the sleep in keeps things stable, or maybe it just eats away so slowly I don't notice it. Leaving sleep() in also has the problem of *I think* causing missed file events. The f_handler() function posts tasks that I create within the dir_monitor callback back to the main thread via the io_service.post(), but if its asleep, will it be able to place objects on the main processes task_queue? I think thats one point where I'm going wrong. If anyone sees where I'm going wrong, any help much appreciated. --- static queue<TaskObj *> task_queue; boost::asio::io_service io_service; void queue_task(TaskObj *task) { // pass task back to main thread. task_queue.push(task); } void f_handler(const boost::system::error_code &ec, const boost::asio::dir_monitor_event &ev) { TaskObj task = new TaskObj(...); // create task and place on queue by posting to main process io_service.post(boost::bind(queue_task, task)); } int main(...) { boost::asio::io_service work_service; boost::asio::dir_monitor dm(io_service); dm.async_monitor(f_handler); // dir_monitor thread boost::thread mthread = boost::thread(boost::bind(&boost::asio::io_service::run, boost::ref(io_service))); // setup work to prevent premature exit shared_ptr<boost::asio::io_service::work> work(new boost::asio::io_service::work(work_service)); // worker thread boost::thread wthread(boost::bind(&boost::asio::io_service::run, boost::ref(work_service))); wthread.detach(); while (true) { io_service.reset(); dm.async_monitor(f_handler); // losing all available memory from above two lines without the sleep() below // get first task off of queue and process in worker thread task = task_queue.front(); // functor executed in seperate thread work_service.post(boost::bind(&TaskObj::do_it, task)); sleep(3); }

2 4

Confused with Depth-First-Search method, forward or cross edge found on a undirected graph ?
by lizy10b 03 Jul '13

03 Jul '13

Hi there I have a problem with the DFS method (Boost 1.53). I found when invoking the DFS method on a undirected graph, the "forward_or_cross_edge" was called more than one times. But as the document says "In an undirected graph this method is never called". http://www.boost.org/doc/libs/1_53_0/libs/graph/doc/DFSVisitor.html I performed the test based on the file_dependencies.cpp example (examples/file_dependencies.cpp; http://www.boost.org/doc/libs/1_53_0/libs/graph/doc/file_dependency_example…) 1) Change the graph type from "bidirectionalS" to "undirected". 2)Implement all the 8 DFS vistor "event methods" (Initialize Vertex, Start Vertex, Discover Vertex, Examine Edge, Tree Edge, Back Edge, Forward or Cross Edge, Finish Vertex) in the cycle_detector struct to print the vertex names, edge sources and targets. 3)comment out some code at the begining of the example cpp files as the topological_sort method raise exception upon the undirected graph. The results: the forward_or_cross_edge method was called five times. initialize_vertex: dax.h initialize_vertex: yow.h initialize_vertex: boz.h initialize_vertex: zow.h initialize_vertex: foo.cpp initialize_vertex: foo.o initialize_vertex: bar.cpp initialize_vertex: bar.o initialize_vertex: libfoobar.a initialize_vertex: zig.cpp initialize_vertex: zig.o initialize_vertex: zag.cpp initialize_vertex: zag.o initialize_vertex: libzigzag.a initialize_vertex: killerapp start_vertex: dax.h discover_vertex: dax.h examine_edge: dax.h --> foo.cpp tree_edge: dax.h --> foo.cpp discover_vertex: foo.cpp examine_edge: foo.cpp --> dax.h back_edge: foo.cpp --> dax.h examine_edge: foo.cpp --> zow.h tree_edge: foo.cpp --> zow.h discover_vertex: zow.h examine_edge: zow.h --> foo.cpp back_edge: zow.h --> foo.cpp finish_vertex: zow.h examine_edge: foo.cpp --> foo.o tree_edge: foo.cpp --> foo.o discover_vertex: foo.o examine_edge: foo.o --> foo.cpp back_edge: foo.o --> foo.cpp examine_edge: foo.o --> libfoobar.a tree_edge: foo.o --> libfoobar.a discover_vertex: libfoobar.a examine_edge: libfoobar.a --> foo.o back_edge: libfoobar.a --> foo.o examine_edge: libfoobar.a --> bar.o tree_edge: libfoobar.a --> bar.o discover_vertex: bar.o examine_edge: bar.o --> bar.cpp tree_edge: bar.o --> bar.cpp discover_vertex: bar.cpp examine_edge: bar.cpp --> dax.h back_edge: bar.cpp --> dax.h examine_edge: bar.cpp --> yow.h tree_edge: bar.cpp --> yow.h discover_vertex: yow.h examine_edge: yow.h --> dax.h back_edge: yow.h --> dax.h examine_edge: yow.h --> bar.cpp back_edge: yow.h --> bar.cpp examine_edge: yow.h --> zag.cpp tree_edge: yow.h --> zag.cpp discover_vertex: zag.cpp examine_edge: zag.cpp --> yow.h back_edge: zag.cpp --> yow.h examine_edge: zag.cpp --> boz.h tree_edge: zag.cpp --> boz.h discover_vertex: boz.h examine_edge: boz.h --> bar.cpp back_edge: boz.h --> bar.cpp examine_edge: boz.h --> zig.cpp tree_edge: boz.h --> zig.cpp discover_vertex: zig.cpp examine_edge: zig.cpp --> boz.h back_edge: zig.cpp --> boz.h examine_edge: zig.cpp --> zig.o tree_edge: zig.cpp --> zig.o discover_vertex: zig.o examine_edge: zig.o --> zig.cpp back_edge: zig.o --> zig.cpp examine_edge: zig.o --> libzigzag.a tree_edge: zig.o --> libzigzag.a discover_vertex: libzigzag.a examine_edge: libzigzag.a --> libfoobar.a back_edge: libzigzag.a --> libfoobar.a examine_edge: libzigzag.a --> zig.o back_edge: libzigzag.a --> zig.o examine_edge: libzigzag.a --> zag.o tree_edge: libzigzag.a --> zag.o discover_vertex: zag.o examine_edge: zag.o --> zag.cpp back_edge: zag.o --> zag.cpp examine_edge: zag.o --> libzigzag.a back_edge: zag.o --> libzigzag.a finish_vertex: zag.o examine_edge: libzigzag.a --> killerapp tree_edge: libzigzag.a --> killerapp discover_vertex: killerapp examine_edge: killerapp --> libzigzag.a back_edge: killerapp --> libzigzag.a finish_vertex: killerapp finish_vertex: libzigzag.a finish_vertex: zig.o finish_vertex: zig.cpp examine_edge: boz.h --> zag.cpp back_edge: boz.h --> zag.cpp finish_vertex: boz.h examine_edge: zag.cpp --> zag.o forward_or_cross_edge: zag.cpp --> zag.o !!!!!! finish_vertex: zag.cpp finish_vertex: yow.h examine_edge: bar.cpp --> boz.h forward_or_cross_edge: bar.cpp --> boz.h !!!!!! examine_edge: bar.cpp --> bar.o back_edge: bar.cpp --> bar.o finish_vertex: bar.cpp examine_edge: bar.o --> libfoobar.a back_edge: bar.o --> libfoobar.a finish_vertex: bar.o examine_edge: libfoobar.a --> libzigzag.a forward_or_cross_edge: libfoobar.a --> libzigzag.a !!!!!! finish_vertex: libfoobar.a finish_vertex: foo.o finish_vertex: foo.cpp examine_edge: dax.h --> bar.cpp forward_or_cross_edge: dax.h --> bar.cpp !!!!!! examine_edge: dax.h --> yow.h forward_or_cross_edge: dax.h --> yow.h !!!!!! finish_vertex: dax.h What is the problem? Thanks. Zhiyu 2013-06-24 lizy10b

3 23

Applied GUI on chat server/client examples of boost.asio
by Journeyer J. Joh 03 Jul '13

03 Jul '13

Hi list, This is not a question nor an answer. And not an advertisement. I made an ultra simple GUI on boost.asio example code below. http://www.boost.org/doc/libs/1_53_0/doc/html/boost_asio/examples.html My code is on github. https://github.com/Journeyer/wxboost It is implemented from wxwidgets example code for wxTextCtrl under samples/text I don't have any purpose on this post. If anyone cloned my source code and compile and runs he/she would be able to talk with me and with anyone who did the same experiment. My chat server is running until it breaks. I am doing this just for fun ^^; FYI: build environment is Ubuntu/GCC/gtk/wxwidgets/boost Windows7/MinGW/wxwidgets/boost Best regards 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 ----------------------------------------

2 2

[build] Build with multiple processes under MSVC10
by Igor R 03 Jul '13

03 Jul '13

Hello, Is the subj possible? Adding "cxxflags=/MP" to b2 line doesn't seem to work. Thanks.

2 2

single thread in loop
by SRD 03 Jul '13

03 Jul '13

I'm using boost 1.53 on windows 7. I have a main loop which runs some checks and when events are received, results in callbacks that add tasks onto a queue. I then pull a task off the queue, wish to start a thread (and only one thread) to handle the task, and continue to loop checking for certain events. And each time I go through the loop, I want to check to see if the current thread has completed before pulling off another task to process. My problem is that I'm not sure how to write the thread in to do this and not join because I have to keep looping to check for certain events. void my_callback(...); MyTask *task; while (true) { event_checks(); switch(state) { case STATE1: if (!queue.empty()) task = queue.front(); // ... break; case STATE2: // check if thread is still running, otherwise, start new thread boost::thread(&MyTask::do_it, task); // ... break; // ... } I tried things similar to the below but couldn't get that quite right. boost::thread t; while (true) { // ... if (t.timed_join(0) == false) { t = boost::thread(&MyTask::do_it, task); } // ... Any help much appreciated.

2 3

Thread pools and Boost Asio
by Rodrigo Madera 02 Jul '13

02 Jul '13

Hey there. I use Boost Asio for async code everywhere in C++, even where there is absolutely no IO whatsoever. Just (ab)using Asio "for the async of it." Searching the net for the current status of async frameworks for C++, I see that there is an unofficial (please correct me if I'm wrong) threadpool library. Will it become official? If not, does the Boost community offer something simpler than Asio for this? I just feel that I'm abusing Asio, where something simpler would suffice. And threadpool might be it. Would be nice to see if other people are async'ing out there. Best regards, Rodrigo Madera

2 1

[asio] Getting started with strand
by Michael Powell 02 Jul '13

02 Jul '13

Hello, I want to get started using asio strand if at all possible. Getting started, however, I am struggling with a couple of errors/issues. For starters: * Cannot find std::enable_shared_from_this, std::move: they do not exist in our environment. * From there a ton of what look like steady-timer-related errors. Many of the errors are linker errors I think. Symbols cannot be resolved, such like this. I am pretty sure I am linking with the correct Boost libraries (statically, multi-threaded). Possibly need to rebuild Boost with different compiler settings? Also, possibly we do not have the correct compile-time switches enabled. Possibly also not linking with the correct libraries. We are cross-compiling into ArchLinux for ARM using Sourcery CodeBench, basically a GCC 4.7.2 based environment. That or are we stuck with the old-style approach to scheduling asio io_service callbacks? Would much prefer strands if we can somehow manage it. Thank you... Regards, Michael Powell

1 2

boost 1.54 and intel compiler ?
by avib369 . 02 Jul '13

02 Jul '13

I have noticed that the Intel Compiler is no longer mentioned ? Has this compiler been dropped ? Ta, Avi

3 2

Serializing containers of movable but noncopyable types
by Daniel Mitchell 02 Jul '13

02 Jul '13

While attempting to serialize a std::vector<T>, where T is a movable but noncopyable type, I was getting blown up by the call to s.push_back() on line 65 of collections_load_imp.hpp (Boost 1.53.0). In my local copy of that header I changed s.push_back(t.reference()) to s.push_back(std::move(t.reference())). Is this a safe change? Is there a better way to handle this case?

2 2

[enable_shared_from_this] Disappeared
by Michael Powell 02 Jul '13

02 Jul '13

Hello, Where did it go from 1.53? We have not upgraded our compiler environment at all, so we are still depending on boost::enable_shared_from_this, however, this seems to have been dropped for std::enable_shared_from_this, which we do not have. Sounds like a bug report? Regards, Michael Powell

2 1

Random generators for Monte Carlo simulations
by Frédéric Bron 02 Jul '13

02 Jul '13

Hi, A collegue of mine performs Monte Carlo simulations. I made him switch with success to boost::random a few years ago. He recently found the following reference: http://www.agner.org/random and http://www.agner.org/random/ran-instructions.pdf The author proposes generators that are not implemented in boost called "Mother of All", "SFMT" and a special one that is a combination of two different generators (SFMT and Mother of All). Has anybody already done that using boost::random? Regards, Frédéric

2 1

Re: [Boost-users] [boost] Boost 1.54.0 released!
by John Maddock 02 Jul '13

02 Jul '13

The PDF build of the boost documentation (for those libraries that support it) is now at https://sourceforge.net/projects/boost/files/boost-docs/1.54.0/. Please let me know if there are any SNAFU's. Regards, John.

1 0

[zlib] Which version to use
by Michael Powell 02 Jul '13

02 Jul '13

Hello, Some of the build depends on zlib being readily available. For 1.53, I was building against zlib 1.2.7. Is that sufficient for 1.54? There is a zlib 1.2.8 available; worth upgrading to? Yes, no, possibly so? Thank you... Regards, Michael Powell

1 0

Do correct instructions for MinGW install exist?
by Kirk Joppy 02 Jul '13

02 Jul '13

Dear Boost users, I have recently been trying to install boost 1.53 for use with MinGW. I followed the instructions here http://www.boost.org/doc/libs/1_53_0/more/getting_started/windows.html#prep… to the letter with resulting failure. I then noticed that when running b2 install --prefix=G:\boost_1_53_0\my-build from G:\boost_1_53_0\tools\build\v2 as per the instructions, the first few lines of output read warning: No toolsets are configured warning: Configuring default toolset "msvc" warning: If the defrault is wrong, your build may not work correctly warning: Use the "toolset=xxxxx" option to override our guess warning: For more configuration options, please consult <webpage> I have consulted the recommended web page and I think I have gotten a working install. However, given that the instructions as written are incorrect I would like to ask 1. Is there a correct, definitive source of instructions for installing boost (with MinGW)? 2. Should the documentation be corrected? I think this error is important given that the section I was working from is specifically indicated to pertain to non-MSVC builds. 3. I have found several conflicting sources of information regarding how to build boost for use with static linking. StackOverflow, for example, has several posts about this, none of which agree with each other. Is there are definitive, correct source of this information? If not I suppose I will post to this mailing list asking about it. Thank you for your consideration. Regards, kjoppy

1 0

Boost.Test on Windows x64
by User 8583 02 Jul '13

02 Jul '13

Hello, I am trying to use Boost.Test 1.53 on a Windows 7 x64 platform and VS2012. I compiled the libraries using .\b2 variant=release link=static threading=multi runtime-link=shared toolset=msvc-11.0 address-model=64 Linking the libraries with my (x64) test program produces the following error: libboost_unit_test_framework-vc110-mt-gd-1_53.lib(unit_test_suite.obj) : fatal error LNK1112: module machine type 'X86' conflicts with target machine type 'x64' I am surprised as I have used the boost serialization library compiled with the same command line in x64 programs without such error. Any help appreciated, Bob

3 8

basic_socket.hpp line 1421
by Christopher Pisz 01 Jul '13

01 Jul '13

I am migrating a project from VS 2008 to Vs 2012 and in the process updated boost from 1.40 to 1.53. After days and weeks of project settings, editing third party source (not boost), playing with configurations, etc. I got a build! Unfortunately one of the unit tests has an unhandled exception. I debugged down into code that was foreign to me and see that someone was calling shutdown on a boost socket. Maybe they called it at the wrong time or already shut it down, or something. It isn't my code. However, this looks very suspicious to me: in boost's header basic_socket.hpp: void shutdown(shutdown_type what) { boost::system::error_code ec; this->get_service().shutdown(this->get_implementation(), what, ec); boost::asio::detail::throw_error(ec, "shutdown"); } I don't see how this would not throw? It looks like it _always_ throws? What's the deal here?

2 2

Re: [Boost-users] [program_options] copy option_description from one options_description to another
by Ghyslain Leclerc 01 Jul '13

01 Jul '13

On 2013-06-30, at 17:57 , Juraj Ivan?i? <juraj.ivancic(a)gmail.com> wrote: > > There is an 'add' overload which accepts shared_ptr. This one does not > add grouping. I hadn't noticed that. My bad. This is exactly what I needed. Solved everything for now. I thought knowing what actually solved my problem might be good to share on the mailing list. Hope this is appropriate. Sorry if it isn't. > > you get double delete crash. I hadn't thought of that. Proves I'm a physicist first and a programmer second ! Thanks for your explanation. Hopefully makes me better. Again, thanks for your time. Ghyslain

1 0

Boost 1.54.0 released!
by Marshall Clow 01 Jul '13

01 Jul '13

Release 1.54.0 of the Boost C++ Libraries is now available. These open-source libraries work well with the C++ Standard Library, and are usable across a broad spectrum of applications. The Boost license encourages both commercial and non-commercial use. This release contains five new libraries and numerous enhancements and bug fixes for existing libraries. New Libraries: Log: Logging library, from Andrey Semashev. TTI: Type Traits Introspection library, from Edward Diener. Type Erasure: Runtime polymorphism based on concepts. For details, including download links, see http://www.boost.org/users/news/version_1.54.0 You can also download directly from SourceForge: http://sourceforge.net/projects/boost/files/boost/1.54.0/ To install this release on your system, see http://www.boost.org/doc/libs/release/more/getting_started/index.html Thanks, --The Boost release team Beman Dawes Daniel James Eric Niebler Marshall Clow Rene Rivera Vladimir Prus

2 1

Counting all cliques of a given size in an undirected graph
by Andrea Cassioli 01 Jul '13

01 Jul '13

Dear all Boost users, I need to count all cliques of a given size in an undirected graph. I am using Boost Graph and I have found the Bron-Kerbosch algorithm implemented in version 1.53 but not documented. My question is two-fold: 1) why the algorithm is somehow hidden? 2) Is this algorithm able to count the occurrencies of cliques of a certain dimension or just the maximal cliques? Best, Andrea Cassioli

3 2

Problem in building the BGL Python 0.95 on Windows
by lizy10b 01 Jul '13

01 Jul '13

Hi there, I have got the latest BGL-Python 0.95 from svn (thanks to John), but I can't build it. My environment: Windows 7 x64, Python 2.66 x86, MPICH2 1.32 x86, VS2010 I have tried the following steps: 1. The boost 1.53 source code distribution dir (newly extracted from the zip package) is E:\boost_1_53_0, the BGL Python 0.95 source code dir is E:\bgl-python_svn_095 2. Add a new environment variable, name: BOOST_ROOT, value: E:\boost_1_53_0 3. Append the boost 1.53 source code distribution dir (E:\boost_1_53_0) to the environment variable "PATH" to expose later built bjam.exe file. 4. Add some lines to the file user-config.jam (E:\boost_1_53_0\tools\build\v2\user-config.jam) import toolset : using ; using python : 2.6 : "C:\\Python266" : "C:\\Python266\\include" : "C:\\Python266\\libs" ; using mpi : : <find-static-library>mpi <library-path>"D:\\Program Files (x86)\\MPICH2\\lib" <include>"D:\\Program Files (x86)\\MPICH2\\include" : "\"D:\\Program Files (x86)\\MPICH2\\mpiexec\"" ; 5. Open the vs2010 commandline window (Visual Studio Command Prompt 2010) 6. Navigate to boost 1.53 source code distribution dir to build the bjam.exe: type bootstrap.bat 7. Then navigate to the BGL-Python-0.95 source code dir and type bjam --prefix=E:\boost_1_53_0\release32 stage toolset=msvc-10.0 variant=release link=static address-model=32 architecture=x86 threading=multi runtime-link=shared install The outputs are: Jamfile.v2:198: in load-aux rule python.get-python-interpreter unknown in module Jamfile</E:/bgl-python_svn_ 095> E:/boost_1_53_0/tools/build/v2/build\project.jam:323: in load-jamfile E:/boost_1_53_0/tools/build/v2/build\project.jam:62: in load E:/boost_1_53_0/tools/build/v2/build\project.jam:168: in project.find E:/boost_1_53_0/tools/build/v2\build-system.jam:570: in load E:\boost_1_53_0\tools\build\v2/kernel\modules.jam:283: in import E:\boost_1_53_0\tools\build\v2/kernel/bootstrap.jam:142: in boost-build E:\boost_1_53_0\boost-build.jam:17: in module scope E:\bgl-python_svn_095> and the building process stopped. So what is the problem? Thanks. Zhiyu Li

2 3

[program_options] copy option_description from one options_description to another
by Ghyslain Leclerc 30 Jun '13

30 Jun '13

Hello. First post here. Not a programmer by trade, but a medical physicist, so my apologies if my question seems too much of a newbie question. And hopefully, my programing jargon won’t be too bad. I have searched on Google and played with my code all day yesterday and I have not found the answer to my problem, so I thought I would try the mailing list. We have a number of small command line utilities (approx. 10) that we are developing for our clinic. We want to try and make a base class that would contain all our usual program options in it and would allow customization for our various little programs. Thus, I need to store a options_description object with our usual options and a function in the class to add options to the stored object. That way, the interfaces would be more homogeneous and we would not need to recode all the logic of option handling for every application and maintain them all. Simply create a derived class and add a few options_description to it. Then use that class for our application. My first approach was to store a options_description object directly, but I can't seem to assign to it. So if I want to reset the object to a completely new one, for instance in a special case where the usual options don't make any sense, I run into problems. I switched to holding a pointer to it (tr1 shared_ptr). That allows me to easily change the object all together if I need to. In either case (pointer or object), my actual problem comes when I want to add options to a options_description. I can easily use the add function : myOptionsDescriptionObject.add( theOtherOptionsDescriptionObject ); but that adds empty lines in the output format and creates artificial grouping of options, which I would like to avoid if possible. That being said, given the current state of our code, I will implement this version now as this is the "best" solution that works. The way I am trying to get around that is to extract for each option_description contained in the options_description object the name, the description and the value_semantic and then use these three extracted values with the add_options() function like so: muOptionsDescriptionObject.add_options()( other.options()->name(), other.options()->semantic().get(), other.options()->description() ); Works perfectly for name and description, but fails for value_semantic. It compiles, but generates a "The program has unexpectedly finished." message. My hypothesis for what is happening is that I am using the .get() to extract the raw pointer from the shared_ptr returned, but the shared_ptr somehow deletes the memory and my pointer becomes invalid. Here is a short version of what I came up with. The problem is probably in the implementation of the function addGenOpts(). Can anybody help with this? Sorry if this is a ridiculous question or if my post makes no sense. English is not my first language. In advance, thanks. Ghyslain --------------------------- namespace bpo = boost::program_options; class BaseCli { public: BaseCli(); virtual ~BaseCli() {} void parseCmdLineOpts( int argc, const char* argv[] ); void parseCfgFileOpts(); void run(); bool checkPresent( const std::string& optionStrg ); const bpo::options_description& genOpts( ); void addGenOpts( const bpo::options_description& opts ); void setGenOpts( const bpo::options_description& opts ); private: bpo::variables_map optionsMap_; std::tr1::shared_ptr< bpo::options_description > genOpts_; //virtual void runNoInteraction_() = 0; //virtual void runWithInteraction_() = 0; }; void BaseCli::addGenOpts( const bpo::options_description& opts ) { using std::vector; using std::string; // Loop through every option in opts for( auto optIter = opts.options().begin(); optIter != opts.options().end(); ++optIter ) { ... CODE REMOVED TO SAVE SPACE ... ... SIMPLE STRING MANIPULATION STUFF ... // Combine names into program_options option string string combinedName( longName ); if ( !shortName.empty() ) { combinedName += string( "," ) + shortName; } genOpts_->add_options()( combinedName.c_str(), (*optIter)->semantic().get(), (*optIter)->description().c_str() ); } } ---------------------------

2 1

Asio and Spirit
by LeMay.Steve 30 Jun '13

30 Jun '13

Can anyone point me to a modern example or description of using Asio with Spirit to parse and asynchronous stream. I keep finding articles that say this can't be done, or at least not easily (but the comments date back to 2007). SGL

3 3

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