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

[interprocess] Determine size of managed_shared_memory
by Kai Benndorf 12 Oct '19

12 Oct '19

Hi all, I want to create a managed_shared_memory in exactly the size I needed. Therefore I do something like this: size = sizeof( common_managed_shared_memory ); size += sizeof( MyClassInSharedMem ); managed_shared_memory segment(create_only, "name", size ); MyClassInSharedMem allocates itself some memory by segment->allocate(). I added this also to the size, but get a boost::interprocess::bad_alloc exception on allocating this additional memory. Are there some magic bytes I forgot to add? Many thanks in advance Kai

3 2

boost::filtered_graph filtering on vertex color... if I only had a colormap
by Brian Davis 19 Jul '19

19 Jul '19

Lets say I have a graph g (of type graph_t) and a color map (boy I wish I had a colormap): typedef boost::property_map<graph_t, boost::vertex_color_t>::type color_map_t; or is it? auto indexmap = boost::get(boost::vertex_index, g); auto colors = boost::make_vector_property_map<boost::default_color_type>(indexmap); or maybe? auto indexmap = boost::get(boost::vertex_index, g); auto colors = boost::make_vector_property_map<boost::vertex_color_t>(indexmap); or possibly some goop found on the internet? boost::make_iterator_property_map(color_map.begin(), boost::get(boost::vertex_index, data_->g), color_map[0]) or other internet goop? typedef boost::property_map<GraphType, boost::vertex_color_t>::type color_map_t; color_map_t colorMap; boost::color_map(colorMap)) or other internet goop?? std::vector<int> colorMap(num_vertices(g), boost::white_color); so confused... (certainly not surprised why bgl is not a part of stl) Can someone help explain the various types and ways of specifying colormaps and the logic for each way and means? and a function (if I could get that far without VS syntax highlighter going bonkers and gobs of compiler errors.. you know the type): make_pretty(g, colormap ) which colors the graph colormap and a filter struct for boost::filtered_graph<Graph, EdgePredicate, VertexPredicate> (where I wonder why if I only want to filter vertices I have to set boost::keep_all for EdgePredicate... sigh... I know the answer... and also know how long it found me to find/figure out boost::keep_all - and if you are looking for boost::keep_all and found it here... your welcome ;-) ) and modifying (probably incorrectly) boost::filtered_graph example to: template <typename ColorMap> struct vertex_color_filter_eq { vertex_color_filter_eq() { } vertex_color_filter_eq(ColorMap colormap/*, boost::default_color_type c*/) : m_colormap(colormap)/*, m_c(c)*/ { } template <typename Vertex> bool operator()(const Vertex& v) const { return 0 < get(m_colormap, v); //return c < get(m_colormap, v); } ColorMap m_colormap; //boost::default_color_type m_c; }; auto indexmap = boost::get(boost::vertex_index, g); auto colors = boost::make_vector_property_map<boost::default_color_type>(indexmap); // some where here I would call make_pretty(g, colors) typedef property_map<graph_t, boost::vertex_color_t>::type ColorMap_t; vertex_color_filter<ColorMap_t> filter(colors); // boost::filtered_graph<graph_t, boost::keep_all, VertexPredicate> boost::filtered_graph<graph_t, boost::keep_all, vertex_color_filter> fg(g, filter); // Later say if I could get it compile and better if it compiled and worked I could move on and auto color = boost::red_color; typedef property_map<graph_t, boost::vertex_color_t>::type ColorMap_t; vertex_color_filter<ColorMap_t> filter(colors, color); boost::filtered_graph<graph_t, boost::keep_all, vertex_color_filter> fg(g, filter); Maybe if I color them yellow, I can then reach the wizard pull back the curtain and ask how to create a color map... If I only had a color map.

4 6

Twenty years and time to retire
by Beman Dawes 04 Oct '18

04 Oct '18

The idea behind Boost was hatched in March, 1998, and the proposal document <https://www.boost.org/users/proposal.pdf> was released May 6, 1998. That makes Boost twenty years old, and makes me twenty years older. It is high time I retire from Boost; I haven't been able to contribute for some time now. Thanks to all of you who made Boost such an overwhelming success in the past and will drive Boost forward into a bright future! --Beman

10 9

undefined reference to `boost::log::v2_mt_posix::...
by Antonis Polykratis 01 Oct '18

01 Oct '18

Hello I face this error and I cannot figure out a fix. I use bjam to build the application code, and inside site-config file, I have also the following a section where I define BOOST_ALL_DYN_LINK: ''' using gcc : : : where I have defined <define> BOOST_ALL_DYN_LINK ''' I have build boost libraries with the following command: sudo bjam toolset=gcc --with-system --with-thread --with-timer --with-chrono --with-filesystem --with-program_options --with-timer *--with-log* --with-program_options --with-date_time --with-math --with-serialization --with-regex --with-chrono --with-atomic runtime-link=shared define=*BOOST_ALL_DYN_LINK* --prefix=/opt/boost_shared install | tee output.txt I also changed some files (macro definitions and jam files) because I had an error that system and filesystem are configured to be compiled both as static and shared. I compiled them as shared. When I build the application code, I have plenty of `boost::log::v2_mt_posix::...` error messages. Could you give me some guide why this problem exist? Thanks, Antonis

2 1

error: ‘class boost::mutex’ has no member named ‘try_lock_for’
by Antonis Polykratis 28 Sep '18

28 Sep '18

Hi, I face this error, in linux, does this indicates that I have not build the library correctly? the error is in that line: boost/thread/lock_types.hpp:162:45 #ifdef BOOST_THREAD_USES_CHRONO template <class Clock, class Duration> unique_lock(Mutex& mtx, const chrono::time_point<Clock, Duration>& t) : m(&mtx), is_locked(mtx.try_lock_until(t)) { } template <class Rep, class Period> unique_lock(Mutex& mtx, const chrono::duration<Rep, Period>& d) : m(&mtx), is_locked(mtx.try_lock_for(d)) <--- here is the error { } #endif Thanks, Antonis

2 1

Boost.Units Example: Convert between nautical mile and imperial foot
by Carel Combrink 27 Sep '18

27 Sep '18

Hi, I am trying to use Boost.Units to convert between different units. I have implemented the example code for the "Radar Beam Height" [1] section but trying to convert between nautical mile and imperial foot result in a compiler error: I have: typedef boost::units::quantity<boost::units::si::length> Meters; typedef boost::units::quantity<imperial::length> Feet; typedef boost::units::quantity<nautical::length> NMiles; double func() { // Working const Meters si1(300.0*nautical::miles); const Meters si2(300.0*imperial::feet); const Feet feet1(300.0*imperial::feet); const Feet feet2(300.0*boost::units::si::meters); const NMiles mile1(300.0*nautical::miles); const NMiles mile2(300.0*boost::units::si::meters); // BROKEN const Feet feet3(300.0*nautical::miles); const NMiles mile3(300.0*imperial::feet); } The first few works, converting between meters and the new units, but converting between the two does not work. To see the issue see the code on Compiler Explorer here: https://gcc.godbolt.org/z/MpvuMy How can I get this working? [1] https://www.boost.org/doc/libs/1_68_0/doc/html/boost_units/Examples.html#bo… Regards,

3 5

Serialization with BOOST _CLASS_EXPORT_KEY() is not the same as registert_type<>()
by Kosby, Ray B. (GSFC-428.0)[COLUMBUS TECHNOLOGIES AND SERVICES INC] 25 Sep '18

25 Sep '18

Hi, I’m trying to serialize a derived object with polymorphism into a file and deserialize to a base class pointer. This works when I use the register_type function but not the BOOST_CLASS_EXPORT_KEY() and BOOST_CLASS_IMPLEMENT() macros. I need to use the macros since I am using shared libraries. Here is a sample of code to demonstrate the problem. When run it gets a unregistered class exception. I’m using RHEL 7.4 with Boost 1.53. cat testera.h #ifndef testera_h #define testera_h #include <boost/serialization/serialization.hpp> #include <boost/archive/polymorphic_oarchive.hpp> #include <boost/archive/polymorphic_iarchive.hpp> #include <boost/serialization/export.hpp> #include <boost/serialization/string.hpp> class A { private: friend class boost::serialization::access; template< class Arch > void serialize( Arch &ar, const unsigned int ver ); public: A(); virtual ~A() {} void setStr( const std::string &s ); std::string getStr(); protected: std::string myStr; }; BOOST_CLASS_EXPORT_KEY(A) #endif boost_ptr> cat testera.C #include "testera.h" BOOST_CLASS_EXPORT_IMPLEMENT(A) template void A::serialize<boost::archive::polymorphic_oarchive>( boost::archive::polymorphic_oarchive &ar, const unsigned int ver ); template void A::serialize<boost::archive::polymorphic_iarchive>( boost::archive::polymorphic_iarchive &ar, const unsigned int ver ); A::A() : myStr( "a" ) { } void A::setStr( const std::string &s ) { myStr = s; } std::string A::getStr() { return myStr; } template<class Arch> void A::serialize( Arch &ar, const unsigned int ver ) { ar & myStr; } boost_ptr> cat testerb.h #ifndef testerb_h #define testerb_h #include "testera.h" class B : public A { private: friend class boost::serialization::access; template< class Arch > void serialize( Arch &ar, const unsigned int ver ); public: B(); virtual ~B() {} void set( const int i ); int get(); protected: int myI; }; BOOST_CLASS_EXPORT_KEY(B) #endif boost_ptr> cat testerb.C #include "testerb.h" BOOST_CLASS_EXPORT_IMPLEMENT(B) template void B::serialize<boost::archive::polymorphic_oarchive>( boost::archive::polymorphic_oarchive &ar, const unsigned int ver ); template void B::serialize<boost::archive::polymorphic_iarchive>( boost::archive::polymorphic_iarchive &ar, const unsigned int ver ); B::B(): myI( 1 ) { myStr = "b"; } void B::set( const int i ) { myI = i; } int B::get() { return myI; } template< class Arch > void B::serialize( Arch &ar, const unsigned int ver ) { // boost::serialization::void_cast_register< B, A >( static_cast< B *>( NULL ), static_cast< A * >( NULL ) ); ar & boost::serialization::base_object<A>( *this ); ar & myI; } int main( int argc, char *argv[] ) { int ret = 0; B obj; B obj2; obj.set( 2 ); A *ptr = NULL; B *bptr = NULL; bptr = &obj; ptr = &obj; if( argc > 1 ) { std::string fl = argv[ 1 ]; { std::ofstream ofl( fl.c_str() ); boost::archive::polymorphic_text_oarchive toar( ofl ); boost::archive::polymorphic_oarchive *oar = &toar; /* oar->register_type(static_cast<A *>(NULL)); oar->register_type(static_cast<B *>(NULL)); */ try { *oar & obj; // *oar & ptr; } catch( std::exception &e ) { std::cerr << "Error: archive from B to file " << fl << " - " << e.what() << std::endl; ret = 1; } } if( ! ret ) { ptr = NULL; bptr = NULL; { std::ifstream ifl( fl.c_str() ); boost::archive::polymorphic_text_iarchive tiar( ifl ); boost::archive::polymorphic_iarchive *iar = &tiar; /* iar->register_type(static_cast<A *>(NULL)); iar->register_type(static_cast<B *>(NULL)); */ try { *iar & ptr; // *iar & bptr; } catch( std::exception &e ) { std::cerr << "Error: archive from file " << fl << " to B * - " << e.what() << std::endl; ret = 1; } } if( ! ret ) { // std::cout << bptr->get() << std::endl; std::cout << static_cast<B*>( ptr )->get() << std::endl; } } } return ret; } testera and testerb are compiled into a shared library with this: boost_ptr> cat Makefile_lib CXXFLAGS = -c -ggdb3 -fPIC -funswitch-loops -fgcse-after-reload -std=c++11 LDFLAGS = -std=c++11 -lboost_serialization -lboost_thread -lboost_system -lboost_filesystem OBJLOC = obj OBJS = $(OBJLOC)/testera.o \ $(OBJLOC)/testerb.o LIBRARY_NAME = libtester.so libs:$(LIBRARY_NAME) $(LIBRARY_NAME): $(OBJS) ${CXX} -shared -o $@ $(OBJS) $(OBJLOC)/%.o: ./%.C $(CXX) $(CXXFLAGS) ./$*.C -o $(OBJLOC)/$*.o tester_mn is compiled into the executable with this: boost_ptr> cat Makefile_mn CXXFLAGS = -ggdb3 -funswitch-loops -fgcse-after-reload -std=c++11 LDFLAGS = -lboost_serialization -lboost_thread -lboost_system -lboost_filesystem -L. -ltester tester_mn: tester_mn.o ${CXX} $(CXXFLAGS) $(LDFLAGS) tester_mn.C -o $@ If I were to comment out the BOOST macros and uncomment the register_type() functions from tester_mn.C everything works. Is there a way to get the macros to work? -- Ray Kosby Software Engineer Columbus Technologies and Services, Inc www.columbususa.com<http://www.columbususa.com> Office - (301) 286-5095, fax - (301) 286-7475 NASA Goddard Space Flight Center, MS 452.1 Bldg 13 Rm 141 8800 Greenbelt Rd Greenbelt, MD 20771 USA

1 0

Re: [Boost-users] [Boost.Beast] Libraries augmenting Boost.Beast
by Damian Jarek 24 Sep '18

24 Sep '18

Hi Sean, I've been recently working on a library that is supposed to abstract some of the platform-specific aspects of TLS peer verification (e.g. accessing the OS cert store) and obtaining the system proxy information. The project is in its early stages but is actively being worked on (https://github.com/djarek/ netutils). Another library you might be interested in, though still fairly experimental is Foxy (https://github.com/LeonineKing1199/f3), which abstracts away HTTP session management. Best Regards, Damian Jarek

1 0

Formal Review of Proposed Boost.Histogram Library is HALFWAY through
by Mateusz Loskot 22 Sep '18

22 Sep '18

Dear Boost Community, We've reach half-way through the formal review of Hans Dembinski's Histogram library. The review lasts until the end of September 26th. If you are interested in applications for mathematics, statistics graphics, image analysis, and such, or in the Histogram library itself, please consider reviewing the Histogram library by the end of September 26th. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

1 0

[filesystem] Library maintainers needed
by Beman Dawes 22 Sep '18

22 Sep '18

I'm retiring, so Boost.Filesystem needs one or more maintainers. This is a high complexity library, further complicated by (1) requiring both Windows and non-Windows implementation code and (2) needing a major upgrade for compatibility with the new standard library version shipped in C++17. Furthermore, there are constant Pull Requests and Issues that arise, and these almost invariably take a lot of time for the maintainer to process. My personal opinion is that Boost should deprecate the Boost library in favor of the standard library implementations, and do only minimal maintenance for several years until most users have migrated to C++17 or later. But that's up to the new maintainers to decide. Thanks, --Beman

1 0