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

[gsoc15] This year's GSoC students
by Niall Douglas 27 Apr '15

27 Apr '15

Dear Boost, It is our pleasure to announce this year's winning GSoC students and projects: 1. Damian Vicino Topic: Safe Float (boost::safe_numerics<float>) Mentor: Robert Ramey 2. Rajaditya Mukherjee Topic: Boost uBLAS EigenSolver Mentor: David Bellot 3. Anurag Ghosh Topic: Boost Document Library Mentor: Antony Polukhin 4. Nikhar Agrawal Topic: Boost.Fixed-Point Mentor: Paul A. Bristow 5. Benedek Thaler Topic: Enhanced vector and deque containers Mentor: Thorsten Ottosen 6. Louis Dionne Topic: Improved compile-time associative data structures for Hana Mentor: Joel Falcou 7. Jakub Szuppe Topic: Improving Boost.Compute Mentor: Kyle Lutz Congratulations to these students for passing an exceptionally tough contest this year, and our thanks to the above mentors for making themselves available. Finally, thank you Google for another year of funding and to those open source orgs who released duplicate students to us, we appreciate it! Niall and Boris --- Boost C++ Libraries Google Summer of Code 2015 admin https://svn.boost.org/trac/boost/wiki/SoC2015

1 0

Re: [Boost-users] boost examples
by Max 27 Apr '15

27 Apr '15

----- Original Message ----- From: mloskot <mateusz(a)loskot.net> To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] boost examples Date: 2015-04-24 18:01 mloskot wrote > On 23 April 2015 at 11:44, Trek < > trek830@ > > wrote: >> Is there a central link where all official boost examples are hosted? > > No. You may check http://theboostcpplibraries.com/ for unofficial ones. ----- -- Mateusz Loskot, http://mateusz.loskot.net Charter Member of OSGeo, http://osgeo.org Member of ACCU, http://accu.org The book, Beyond the C++ Standard Library, also used to be a very good starting point of my understanding the boost libraries. Max

1 0

[Pyhton] (re)binding class instance in python object
by Tamas.Ruszkai＠leica-geosystems.com 27 Apr '15

27 Apr '15

Hi, I have a plain C++ class which I want to exposed to python. The pyhton object accesses the C++ class via smart pointer. class Sensor : public boost::enable_shared_from_this<Sensor> { public: Sensor(int port); ~Sensor() void Open(); void SendCommand(const std::string& command); void Close(); private: int _port; }; auto sensorClassTypeObject = boost::python::class_<Sensor, boost:: shared_ptr<Sensor>>("Sensor", boost::python::init<int>()) .def("Open", &Sensor::Open) .def("SendCommand", &Sensor::SendCommand) .def("Close", &Sensor::Close); The question is: if I already have one instance of the C++ class (in a dependency injection container) then how can I create in the C++ part an instance of the python wrapper so that it does not create a new instance of Sensor, but uses my existing Sensor instance? Then I would put this instance into one of the python modules (this part would be made in C++) inside the python interpreter to be able to access it via script. Something like that: shared_ptr<Sensor> sensorInstance = DIContainer.Resolve<Sensor>(); boost::object pythonInstance = sensorClassTypeObject(sensorInstance); pythonInterpreterWrapper.AddToModule("__main__", pythonInstance); Best Regards, Tamas

1 0

[msm] Event does not get processed after exiting an interrupt state
by Chrisopher Vogl 27 Apr '15

27 Apr '15

Hi all! I got a state machine with 2 regions. The second region has two states ("Run" and "Interrupt"), one is an interrupt state. The region starts in the non interrupt state, just like in the MSM example "Orthogonal regions, terminate state, event deferring". The event called Ev_Resume leads to a transition from state Interrupt back to state Run. In on_entry() of Run I fire an event which never gets processed. Is at that time the FSM still interrupted, i.e. event processing still blocked? Christopher

2 1

Re: [Boost-users] [boost] [test] boost.test owner unresponsive to persistent problems for multiple years
by Paul A. Bristow 24 Apr '15

24 Apr '15

> -----Original Message----- > From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Richard > Sent: 17 March 2015 17:20 > To: boost(a)lists.boost.org > Subject: Re: [boost] [test] boost.test owner unresponsive to persistent problems for multiple years > > Another quarter has gone by and another Boost release is prepared for beta and I see *no* changes to > Boost.Test listed in the release notes.> > So here we are, waiting another 3 months for *simple* changes to be reflected in this library while the > maintainer insists that the fixes are available, yet they continue not to be deployed into any shipping release. It is indeed really deplorable that we don't have Boost.Test updates in a release. Though in mitigation I note that we are really struggling to get out a GIT-driven release at all, (and some of the new troubles are with asynch-exceptions in Boost.Test. See this thread Re: [boost] Running b2 on develop needs asynch-exceptions=on.) However, Richard's hard work on improved docs have been refined and completed by Raffi Enficiaud. Many bug fixes are in the develop branch (including some very new and prompt bug fixes, for example https://svn.boost.org/trac/boost/ticket/11054) I also understand that the fear of Boost.Test updates causing trouble with other libraries, and worse with users test, is a cause for caution in a release version. So it would be really good if *lots more users could download and use the version in the Boost.Test develop branch* so we can get current user feedback. (My experience is good using this, and the test matrix is also good). You can download just Boost.Test either using GIT or as a zip from https://github.com/boostorg/test/tree/develop and substitute it for the contents of the current release modular-boost/libs/test folder (Don't forget to rebuild the Boost.Test library unless you only use the included version). If nothing else, you will find Raffi's shiny new Boostbook docs finally allow you to find what you want to know without frustration. I'd very much like to see this new docs version in the 1.58 documentation release (despite any new features not being in the code release). Paul --- Paul A. Bristow Prizet Farmhouse Kendal UK LA8 8AB +44 (0) 1539 561830

5 5

[log] Possible to explicitly disable AVX2?
by Jason Roehm 24 Apr '15

24 Apr '15

I am building Boost.Log on a relatively new machine whose compiler and CPU both support the AVX2 instruction set. Boost.Log detects this at build time and configures its compiler flags accordingly to use the AVX2 instruction set. I'd like to use the resulting binaries, however, on older systems that do not have AVX2 support. Is it possible to explicitly disable this at build time? I didn't see any mention of it in the documentation, and my attempts to parse the Jamfile's intentions were not successful. Thank you. Jason

1 0

[nowide] Cannot end input using ^Z/^D on Windows
by Yuan Yao 24 Apr '15

24 Apr '15

3 2

boost examples
by Trek 24 Apr '15

24 Apr '15

Is there a central link where all official boost examples are hosted? thanks,

3 2

Boost.Thread Continuation future with executor blocking in destructor
by Konrad Zemek 23 Apr '15

23 Apr '15

Hi, When creating a continuation future with future<>::then(), and the policy is boost::launch::async, the created future's destructor blocks, like a future created by boost::async, and probably for the same reasons (as outlined by the standardization committee in n3679). The same behavior is coded into continuation futures' destructor when using an executor. Why is it needed here? The situation with executor-run continuations is a little different, as even when the future is destroyed, the lifetime of running job is still bound to the executor. My use case: I've coded a network communication stack that returns to the caller a future<NetworkResponse>. I've previously used std::async(std::launch::deferred, ...) to transform the future's content before returning it to the caller (bytes -> protobuf -> internal object), and I consider such manipulation of a future value to be a very powerful feature. I've used std::launch::deferred to reduce the number of running threads, but the downside is that the client can't wait for the future value with a timeout. On the other side of the spectrum is std::launch::async, which would run a new thread - per pending communication - that would do little more than block. boost::future<>::then is a fantastic fit for my use case, as I can use my boost::asio::io_service as an executor and let my communication stack's threads do the work without having them block on future.get() to first retrieve the result. The caller can then call future<>::wait_for() to wait for the reply with a custom timeout. This being network communication, though, a reply message may never arrive - the corresponding promise will eventually be destroyed by the stack, but I can't have users block on the future's destructor until that happens, after they have already decided that the reply is no longer worth waiting for. Please advise if there's a workaround for this behavior that doesn't involve me distributing a custom version of Boost.Thread with my binaries? :) Konrad

5 6

[asio] What are the enhancements for Asio in 1.58
by Aaron Levy 22 Apr '15

22 Apr '15

I am sorry if this has been already asked. Wanted to get a head start on Asio 1.58, having heard that it's a significantly enhanced library. -- Aaron Levy aaron.levy(a)yandex.com

3 2