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

[Serialization]: compiler error when registering derived class
by Mccall, Kurt E. (JSC-EG411) 18 Jun '15

18 Jun '15

I'm embarrassed to to ask this, but maybe someone could interpret this strange compiler error for me: I am registering a derived class everywhere that it is archived through a base class pointer: class MyDerivedClass : public MyBaseClass { … }; class AnotherClass { MyBaseClass *p; … void serialize(Archive &ar, unsigned int) { ar.register_type(static_cast<MyDerivedClass *>(NULL)); // compiler error here … ar & p; } At the line above, the error is error: no matching function for call to ‘boost::archive::xml_oarchive::register_type(AnotherClass:serialize (Archive&, unsigned int) [with Archive = boost::archive::xml_oarchive]::MyDerivedClass*)’ Does the complier think that MyDerivedClass is a member of boost::archive::xml_oarchive? Im using Boost 1.57 and gcc 4.4.7. Thanks.

1 0

[Boost] Visual Studio 2013 Debugger Visualizers
by dariomt＠gmail.com 18 Jun '15

18 Jun '15

Hi, FYI, I just found VS2013 debugger visualizers for boost here: https://visualstudiogallery.msdn.microsoft.com/61f12e7a-bc62-4b2c-b02e-d660… Just download and double-click to install. So far works like a charm! I didn't find them listed in the wiki at https://svn.boost.org/trac/boost/wiki/DebuggerVisualizers It may be a good idea to update the wiki page with the VS2013 info. Regards, Dario

3 2

[Pyhton] boost::shared_ptr problem between python modules
by Tamas.Ruszkai＠leica-geosystems.com 17 Jun '15

17 Jun '15

Hi All, I use - Visual Studio 2013 - boost 1.58 with NuGet - 64 bit Intel I have a class (called Log::FileSink) that I want to instantiate via a boost::shared_ptr. This class is derived from an abstract interface (Log::ISink) which is wrapped (Log::ISinkRealizer) boost::python::class_<Log::ISinkRealizer, boost::shared_ptr<Log:: ISinkRealizer>, boost::noncopyable>("ISink", boost::python::no_init) .def("AddEntry", boost::python::pure_virtual(&Log:: ISinkRealizer::AddEntry)) .def("ShallLog", boost::python::pure_virtual(&Log:: ISinkRealizer::ShallLog)); boost::python::class_<Log::FileSink, boost::shared_ptr<Log:: FileSink>, boost::python::bases<Log::ISink>, boost::noncopyable> ("FileSink", boost::python::init<const std::string&>()) .def("AddDomain", &Log::FileSink::AddDomain): When I create a python instance from the FileSink and I pass it to the constructor of another class inside the same module then it works fine. >>> import DiagnsoticsPy >>> logFile = DiagnsoticsPy.FileSink("system.log"); >>> logFile.AddDomain("Sensor.SensorController", DiagnsoticsPy.Severity.VerboseAndAbove); >>> logFile.AddDomain("Python.DI", DiagnsoticsPy.Severity.VerboseAndAbove); >>> logSource = DiagnsoticsPy.Source("Python.DI", logFile) boost::python::class_<Log::Source, boost::shared_ptr<Log::Source >>("Source", boost::python::init<const std::string&>()) .def(boost::python::init<const std::string&, boost:: shared_ptr<Log::ISink>>()); class DIAGNOSTICS_API Source { public: Source(const std::string& name, boost::shared_ptr<Log:: ISink> sink); }; However when I want to pass the same "logFile" instance to a method which is defined in another python module then the conversion between python and C++ fails. boost::python::class_<Sensor::SensorController, boost::shared_ptr <Sensor::SensorController>, boost::noncopyable>("SensorController", boost::python::init<boost::shared_ptr<Log::ISink>>()); class SENSORCONTROL_API SensorController : public boost:: enable_shared_from_this<SensorController> { public: explicit SensorController(boost::shared_ptr<Log::ISink> logSink); }; >>> import SensorControlPy >>> sensorController = SensorControlPy.SensorController(logFile); Python argument types in SensorController.__init__(SensorController, FileSink) did not match C++ signature: __init__(struct _object * __ptr64, class boost::shared_ptr<class Log::ISink>) If I put the all the Python bindings (also the SensorController) into the same python module then the call to the SensorController constructor works.

1 0

[Random] Change in normal_distribution behavior between Boost 1.49 and Boost 1.56
by Jonathan Jones 17 Jun '15

17 Jun '15

Hi folks, Given the same set of inputs, this program is producing different answers in Boost 1.56 as compared to Boost 1.49: #include <boost/random/mersenne_twister.hpp> #include <boost/random/normal_distribution.hpp> int main() { boost::normal_distribution<double> dist(0.0, 1.0); boost::mt19937 gen(0); for (int ii=1; ii <= 5; ++ii) { printf("%2d) %g\n", ii, dist(gen)); } } I've isolated this to a change in the implementation of normal_distribution between these two versions (mt19937 is producing the same sequence of numbers with the same starting seed). My question is, is there any guarantee that this distribution is going to produce the same answers across different versions of Boost, given the same starting seed (zero in this case)? Thanks, Jon

2 1

Building boost with clang on windows
by Ernest Zaslavsky 16 Jun '15

16 Jun '15

Any progress with it? Last time I tried to build boost 1.58 with clang 3.6.1 it didn't do it out of the box [Read More]<http://feeds.feedburner.com/~r/sizmek-blog/~6/1> [http://www.sizmek.com/Sizmek.png]<http://www.sizmek.com/>

1 0

Re: [Boost-users] [Serialization] Non-default constructor and template class
by Mccall, Kurt E. (JSC-EG411) 15 Jun '15

15 Jun '15

> you should be able to simply define a private default constructor, if boost::serialization::acess is declared as a friend of your class. There is no need to initialize variables > that are in your serialize() function, as Boost.Serialization should set > their values after default construction. So in most cases the default constructor may be empty and > is trivial to implement, while it can not be called by any external entity (except if it is also declared „friend“). Thanks Beet, That makes it sound like overriding load_construct_data() and save_construct_data() is almost never necessary. In what cases would it be needed? Kurt

1 0

C# application crashes due exception in exception_ptr.hpp
by Markus Pieper 15 Jun '15

15 Jun '15

Hi there, I´m new to boost so this might be a silly question. We have a simulation that is written in C++ and compiled as a static lib. It uses a few boost (v1.56) functions like thread. My job is to create a WPF GUI, that uses this lib. For that, I created a C++ CLR DLL which interacts as a wrapper between .NET GUI and the unmanaged libs. Everything works fine but closing my program results in a crash. This crash is described here: http://stackoverflow.com/questions/8144630/mixed-mode-c- cli-dll-throws-exception-on-exit And someone replied, that the reason for this lies in the exception_ptr.hpp beacause a "static exception_ptr ep" is being used instead of "exception_ptr ep". When I delete the static attribute, my program ends normally without the crash. My understanding of C++ is not that big, so I can´t say why it crashes here. But the boost programmers have a reason to do so. I also followed These advices (http://thread.gmane.org/gmane.comp.lib.boost.user/44515) but with no further luck. Best regards, Markus

3 4

c++14 support
by Freddy Martinez Garcia 14 Jun '15

14 Jun '15

hi guys, I’m new with boost... can anyone tell me if boost library can be compiled with c++14 support ?? in that case, how can I do that ?? best regards ============================================= "El tamaño de tus logros depende del tamaño de tus metas." C++ and Qt Senior Developer Lic. Computer Science Buenos Aires, Argentina

4 5

How do I use the output of -showme:link and -showme:compile to customize my boost mpi build?
by Cook, Rich 13 Jun '15

13 Jun '15

Hello, Apologies if this is redundant. I have not heard back so I thought I would try to restate my question more clearly in case it was overlooked. Hopefully I don't seem impatient, but I have a customer waiting on me and I'm not sure if I can help them. In an earlier thread, titled "Cannot build boost with MPI using Intel openMPI wrapper", Alain Miniussi suggested I execute the following commands: $/usr/local/tools/openmpi-intel-debug-1.8.4/bin/mpicxx --showme:compile $/usr/local/tools/openmpi-intel-debug-1.8.4/bin/mpicxx --showme:link I have done so and they appear to give me sane output: rcook@rzgpu2 (~ ): /usr/local/tools/openmpi-intel-debug-1.8.4/bin/mpicxx --showme:compile -I/usr/local/tools/openmpi-intel-debug-1.8.4/include/openmpi/opal/mca/hwloc/hwloc191/hwloc/include -I/usr/local/tools/openmpi-intel-debug-1.8.4/include/openmpi/opal/mca/event/libevent2021/libevent -I/usr/local/tools/openmpi-intel-debug-1.8.4/include/openmpi/opal/mca/event/libevent2021/libevent/include -I/usr/local/tools/openmpi-intel-debug-1.8.4/include -I/usr/local/tools/openmpi-intel-debug-1.8.4/include/openmpi -pthread My question is now, how do I use this output to configure boost to properly build using my Intel MPI wrappers? Currently, I'm seeing this in my output: ==============MPI Auto-configuration=============== MPI auto-detection failed: unknown wrapper compiler /usr/local/tools/openmpi-intel-debug-1.8.4/bin/mpiCC Please report this error to the Boost mailing list: http://www.boost.org<http://www.boost.org/> You will need to manually configure MPI support. MPI launcher: mpirun -np ==================================================== Thanks so much for any help. -- ✐Richard Cook ✇ Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ☎ (office) (925) 423-9605 ☎ (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL)

2 1

future: unreferenced formal parameter 'lk'
by forumer＠smartmobili.com 13 Jun '15

13 Jun '15

Hello, I am using boost 1.58 and when I compile my project I have this annoying warning: Warning 4 warning C4100: 'lk' : unreferenced formal parameter C:\proj\boost\include\boost\thread\future.hpp When I look at source code I can see that lk is not used: future_state::state get_state(boost::unique_lock<boost::mutex>& lk) const { if(!done) { return future_state::waiting; } else { return future_state::ready; } } It would be great to fix it for the next release. Thanks

3 2