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

exercism.io -- crowd-sourced mentorship C++ track online
by legalize+jeeves＠mail.xmission.com 22 Aug '14

22 Aug '14

[Please do not mail me a copy of your followup] Hi Boost-ers, Katrina Owens has created <http://exercism.io>, a web site designed to help programmers get better at their craft through crowd-sourced mentorship. The whole thing is free and open source and all you need to participate is a github account. I have contributed a basic set of completed exercises to enable the C++ language track. I would love for people from the boost community to participate in the C++ track. I had fun doing the initial set of exercises. Most of them could be completed in under 20 minutes, although the intention is that they increase in difficulty as you progress through them. For each exercise you are presented with the problem statement and a set of Boost.Test unit tests. The goal is to get a program that achieves the function and is expressive and readable. First you get all the tests passing in order to achieve the desired function, but then revise the code to get it to be more expressive and idiomatic in the language. It's that last part where the crowd-sourced mentorship comes into play -- once you've submitted your solution for a problem to the website, you'll be able to view the solutions other people have submitted for the same exercise in the same language. You can mentor them in how to write more expressive, idiomatic C++11 code. Who knows, maybe you'll also improve your C++11 skills by reading feedback from others on your submissions. Feel free to comment here or file an issue on the exercism.io github repository <http://github.com/exercism/exercism.io> if you think the C++ track needs more or better instructions or helpful links. -- "The Direct3D Graphics Pipeline" free book <http://tinyurl.com/d3d-pipeline> The Computer Graphics Museum <http://computergraphicsmuseum.org> The Terminals Wiki <http://terminals.classiccmp.org> Legalize Adulthood! (my blog) <http://legalizeadulthood.wordpress.com>

4 5

Serializing std::vector<double>**
by salman arshad 22 Aug '14

22 Aug '14

Hello, I want to serialize std::vector<double>**. I tried but may be I did not look into right places but I can serialize a std::vector<double>* without any problem but not a pointer to a pointer to vector. I think I am doing something really stupid here or missing something. Any help is highly appreciated. Regards, Salman Arshad

2 1

[review] Formal review period for VMD library begins today, Aug 21, and ends Sat, Aug 30
by Steven Watanabe 21 Aug '14

21 Aug '14

AMDG The formal review of the VMD library by Edward Diener starts today, Aug 21st and is scheduled to continue until Aug 30th. About VMD =============== The Variadic Macro Data library is a library of variadic macros which enhance the functionality in the Boost preprocessor library ( Boost PP ). The main focus of the library is the parsing/identifying of a subset of C++ preprocessor data types and of all Boost PP data types. This allows enhanced preprocessor metaprogramming based on the type of macro input. The library may also be seen as a repository for future enhancements to the Boost PP library functionality using variadic macros. Where to get it =============== The library is available on github at https://github.com/eldiener/variadic_macro_data Review guidelines ================= Reviews should be submitted to the developer list (boost(a)lists.boost.org) with '[vmd]' in the subject. Or if you don't wish to for some reason, you can send them privately to me. If so, please let me know whether or not you'd like your review to be forwarded to the list. For your review you may wish to consider the following questions: - What is your evaluation of the design? - What is your evaluation of the implementation? - What is your evaluation of the documentation? - What is your evaluation of the potential usefulness of the library? - Did you try to use the library? With what compiler? Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? - Are you knowledgeable about the problem domain? And finally, every review should answer this question: - Do you think the library should be accepted as a Boost library? Be sure to say this explicitly so that your other comments don't obscure your overall opinion. In Christ, Steven Watanabe

1 0

A library for "string chains"?
by legalize+jeeves＠mail.xmission.com 21 Aug '14

21 Aug '14

[Please do not mail me a copy of your followup] For a motivating example, see this gist: <https://gist.github.com/LegalizeAdulthood/7b67968bd93fbd4f9dbb> It uses boost::mapped_file to map a mail message into memory and then proceeeds to parse it. This is simply an example, but I think this hacked up parser comes fairly close to handling the full RFC2822 message, ignoring MIME extensions. <https://tools.ietf.org/html/rfc2822> I hacked it up from memory of mail message format rules and a single example message, so don't consider it production quality :-). The intention here is to parse a file without copying it's input text into any buffers. Notice that this parser builds structure from a buffer by identifying interesting substrings as (b,e) pointer pairs. A more traditional approach would have involved at least 2 more copies: one that gets the data from the file system into the stream buffer and another one that copies the data from the stream buffer into a std::string. The extra copying can take significant amounts of time when processing thousands of mail messages. Mail messages tend to be short, so mapping them into memory is not such a big deal. Obviously there is a lifetime relationship between the mapped file (the source character buffer) and the associated strings. For my use case, I'm not interested in being able to write to the strings, just read from them. (If you look closely you'll see that I "cheat" and add a few segments into my string that are associated with const char* C-style strings, but they too are read-only.) I'm interested to know if anyone is aware of a "string chain" library that provides a (read-only) API similar to std::string, but is fundamentally just managing (b,e) pointer pairs into some larger buffer. Boost.Test has a funky string class hiding in it called basic_cstring, but it wasn't created for this purpose. -- "The Direct3D Graphics Pipeline" free book <http://tinyurl.com/d3d-pipeline> The Computer Graphics Museum <http://computergraphicsmuseum.org> The Terminals Wiki <http://terminals.classiccmp.org> Legalize Adulthood! (my blog) <http://legalizeadulthood.wordpress.com>

6 12

[Serialization] 1.56.0 - unregistered_class exception while using EXPORTs
by Todd Seiler 20 Aug '14

20 Aug '14

I've been pulling my hair out for a couple of days trying to get this to work. When I serialize something from a base pointer, it throws an "unregistered_class" exception. I know the type of object that's being serialized and that class has "BOOST_CLASS_EXPORT_KEY" in the header and "BOOST_CLASS_EXPORT_IMPLEMENT" in the cpp file with the same name. In the save and load functions I also have: boost::serialization::void_cast_register( static_cast<Derived*>(NULL), static_cast<Base*>(NULL)); The base class is an abstract base class with one pure virtual function method. But here are the differences: 1) I tried using the "ASSUME_ABSTRACT....." macro. That didn't do anything for me. 2) The abstract base class also has a cpp file with some code in it. I'm not sure if that matters or not... Here's the thing. I can get the derived class's "save" method to be called with this code: std::ofstream o(case_path_ + "/" + file_name); if (o.good()) { // MUST HAVE THIS boost::serialization::void_cast_register<Derived, Base>( static_cast<Derived*>(NULL), static_cast<Base*>(NULL)); boost::archive::polymorphic_text_oarchive oa(o); boost::archive::polymorphic_oarchive & oa_interface = oa; oa_interface << base_ptr; } Having the void_cast_register() there sort of defeats the purpose though. I shouldn't need to pre-register them. In all the examples, I see the void_cast_register() inside of the "save" and "load" methods, which is what I have already. All my serialization code resides in cpp files. Also, the serialization code resides in a static lib. But the archive creation and the action to serialize is performed in a dynamic lib. I am also using polymorphic archives everywhere. I've also forced template instantiation of all serialization code and polymorphic archive interface stuff. Any clue?

3 4

[Serialization] 1.56.0 - How to serialize polymorphic base class data without derived data
by Todd Seiler 20 Aug '14

20 Aug '14

Basically, I'm looking to serialize a base class that's polymorphic, from a base class pointer, without it calling the derived class's serialize functions... Here is my setup: class RenderableMesh : public BasicMesh, public DynamicRenderable; Basically, I don't want it to serialize RenderableMesh or DynamicRenderable given a "basicMesh" pointer. The reason is because "DynamicRenderable" derives from a class inside the "Ogre3D" engine which does a bunch of memory management automatically. Basically, when I compile, it tells me it's missing operator delete, because Ogre overloads operator new or something I don't completely understand... I'm okay with serializing the BasicMesh, and then just recreating the RenderableMesh when it's deserialized. Which is what I'm going to have to do anyways because I don't want to change the Ogre3D SDK header files. It's probably super simple... If I don't implement it, it complains telling me the derived class is not registered... Which is correct. If I try to implement, it says operator delete is missing. Any ideas?

1 0

[build] Cannot build from develop anymore
by Marcel Raad 19 Aug '14

19 Aug '14

Hi, last time I tried to build Boost from develop (a few weeks ago) with MSVC, it worked perfectly. Now I get the following errors on two different Windows 7 machines with both MSVC14 CTP3 and MSVC12.3: boost/tools/build/src/build\virtual-target.jam:1099: in virtual- target.register-actual-name from module virtual-target error: Duplicate name of actual target: <pstage\lib>libboost_system-vc140- mt-1_57.lib error: previous virtual target { common%common.copy-libboost_system-vc140- mt-1_57.lib.STATIC_LIB { msvc%msvc.archive-libboost_system-vc140- mt-1_57.lib.STATIC_LIB { msvc%msvc.compile.c++-error_code.obj.OBJ { error_code.cpp.CPP } } } } error: created from ./stage-proper error: another virtual target { common%common.copy-libboost_system-vc140- mt-1_57.lib.STATIC_LIB { msvc%msvc.archive-libboost_system-vc140- mt-1_57.lib.STATIC_LIB { msvc%msvc.compile.c++-error_code.obj.OBJ { error_code.cpp.CPP } } } } error: created from ./stage-proper error: added properties: <asynch-exceptions>on error: removed properties: <asynch-exceptions>off boost/tools/build/src/build\virtual-target.jam:484: in actualize-no-scanner from module object(file-target)@14375 boost/tools/build/src/build\virtual-target.jam:134: in class@virtual- target.actualize from module object(file-target)@14375 boost/tools/build/src\build-system.jam:720: in load from module build-system boost\tools\build\src/kernel\modules.jam:289: in import from module modules boost\tools\build\src/kernel/bootstrap.jam:139: in boost-build from module boost\boost-build.jam:17: in module scope from module Does anyone have any idea what Boost.Build is trying to tell me?

1 0

Re: [Boost-users] boost serialisation, just including shared_ptr.hpp causes compile error on Linux/gcc 4.5
by avib369 . 19 Aug '14

19 Aug '14

Adding the two missing includes has indeed fixed the problem, as suggested in https://svn.boost.org/trac/boost/ticket/10348 #include <boost/serialization/singleton.hpp> #include <boost/serialization/extended_type_info.hpp> Thanks, Avi

1 0

support for OpenMPI 64bit in modular-boost?
by Alle Meije Wink 19 Aug '14

19 Aug '14

Using the git repository (currently 1.57) of modular boost in Windows 7, compiling with MinGW64 and masm/ml64 (from the WDK v7) is successful but with the following warnings at the start: (1) warning: Graph library does not contain MPI-based parallel components. note: to enable them, add "using mpi ;" to your user-config.jam (2) warning: skipping optional Message Passing Interface (MPI) library. note: to enable MPI support, add "using mpi ;" to user-config.jam. note: to suppress this message, pass "--without-mpi" to bjam. note: otherwise, you can safely ignore this message. warning: No python installation configured and autoconfiguration note: failed. See http://www.boost.org/libs/python/doc/building.html note: for configuration instructions or pass --without-python to note: suppress this message and silently skip all Boost.Python targets After installing Open MPI 64-bit ( Windows installer of version 1.6.2 http://www.open-mpi.org/software/ompi/v1.6/downloads/OpenMPI_v1.6.2-2_win64… ), including adding it to the system-wide path, I have tried to re-build boost with MPI by, after running bootstrap gcc adding the line using mpi ; to the file project-config.jam in the boost directory (there is no file user-config.jam or a directory tools/build/v2 in the latest version or so it seems). Now the b2 command produces this output: The system cannot find the path specified. The system cannot find the path specified. The system cannot find the path specified. The system cannot find the path specified. The system cannot find the path specified. MPI auto-detection failed: unknown wrapper compiler mpic++ Please report this error to the Boost mailing list: http://www.boost.org You will need to manually configure MPI support. It continues to build the boost libraries, but still without MPI support. I am advised to manually configure MPI, but I'm pretty sure that is what I have just done. (the binaries are in the directory C:\Users\amwink\usr\local\OpenMPI_v1.6.2-x64\bin -- no spaces) Does anyone know what the problem is here? Is something wrong with this particular mpic++ binary that boost cannot handle? Happy to provide outputs/logs if that helps.

2 1

boost serialisation, just including shared_ptr.hpp causes compile error on Linux/gcc 4.5
by avib369 . 18 Aug '14

18 Aug '14

I did not see boost serialisation in the list of lib that had changed. So its surprising that it now broken ? It appears simply including it cause problems #include <boost/serialization/shared_ptr.hpp> cause gcc.compile.c++ bin/gcc-4.5/debug/test/TestStr.o In file included from /var/tmp/ma0/boost/boost_1_56_0/boost/serialization/shared_ptr.hpp:28:0, from test/TestStr.cpp:27: /var/tmp/ma0/boost/boost_1_56_0/boost/serialization/shared_ptr_helper.hpp: In static member function ‘static const boost::serialization::extended_type_info* boost::serialization::shared_ptr_helper<SPT>::non_polymorphic::get_object_type(U&)’: /var/tmp/ma0/boost/boost_1_56_0/boost/serialization/shared_ptr_helper.hpp:107:22: error: ‘singleton’ is not a member of ‘boost::serialization’ /var/tmp/ma0/boost/boost_1_56_0/boost/serialization/shared_ptr_helper.hpp:110:13: error: expected ‘(’ before ‘>’ token /var/tmp/ma0/boost/boost_1_56_0/boost/serialization/shared_ptr_helper.hpp:110:14: error: ‘::get_const_instance’ has not been declared /var/tmp/ma0/boost/boost_1_56_0/boost/serialization/shared_ptr_helper.hpp: In static member function ‘static const boost::serialization::extended_type_info* boost::serialization::shared_ptr_helper<SPT>::polymorphic::get_object_type(U&)’: /var/tmp/ma0/boost/boost_1_56_0/boost/serialization/shared_ptr_helper.hpp:117:20: error: ‘singleton’ is not a member of ‘boost::serialization’ /var/tmp/ma0/boost/boost_1_56_0/boost/serialization/shared_ptr_helper.hpp:120:13: error: expected ‘(’ before ‘>’ token /var/tmp/ma0/boost/boost_1_56_0/boost/serialization/shared_ptr_helper.hpp:120:14: error: ‘::get_const_instance’ has not been declared /var/tmp/ma0/boost/boost_1_56_0/boost/serialization/shared_ptr_helper.hpp: In member function ‘void boost::serialization::shared_ptr_helper<SPT>::reset(SPT<T>&, T*)’: /var/tmp/ma0/boost/boost_1_56_0/boost/serialization/shared_ptr_helper.hpp:152:30: error: invalid use of incomplete type ‘const struct boost::serialization::extended_type_info’ /var/tmp/ma0/boost/boost_1_56_0/boost/serialization/shared_ptr_helper.hpp:42:7: error: forward declaration of ‘const struct boost::serialization::extended_type_info’ /var/tmp/ma0/boost/boost_1_56_0/boost/serialization/shared_ptr_helper.hpp:167:30: error: invalid use of incomplete type ‘const struct boost::serialization::extended_type_info’ /var/tmp/ma0/boost/boost_1_56_0/boost/serialization/shared_ptr_helper.hpp:42:7: error: forward declaration of ‘const struct boost::serialization::extended_type_info’ /var/tmp/ma0/boost/boost_1_56_0/boost/serialization/shared_ptr_helper.hpp:168:30: error: invalid use of incomplete type ‘const struct boost::serialization::extended_type_info’ /var/tmp/ma0/boost/boost_1_56_0/boost/serialization/shared_ptr_helper.hpp:42:7: error: forward declaration of ‘const struct boost::serialization::extended_type_info’ "g++" -ftemplate-depth-128 -fPIC -O0 -fno-inline -Wall -g -fPIC -DDEBUG -I"../ACore/src" -I"/var/tmp/ma0/boost/boost_1_56_0" -c -o "bin/gcc-4.5/debug/test/TestStr.o" "test/TestStr.cpp" Are there any workarounds ? Ta, Avi

4 3