- Boost-users - lists.boost.org

Re: [Boost-users] Do we have plan to support VS 2017?
by senthil vel 29 Nov '16

29 Nov '16

Hi All, I am using VS 2017 for my software development.The last official release of boost ( boost_1_62_0 ) supports VS 2015. When will we get VS 2017 supported boost library? Is there any workaround, till we get the support? Regards, Senthil

2 1

[Boost.DateTime] How to bypass checks in boost::gregorian::date constructor
by dariomt＠gmail.com 28 Nov '16

28 Nov '16

>From the docs I see: "date(greg_year, greg_month, greg_day) Construct from parts of date. Throws bad_year, bad_day_of_month, or bad_day_month (derivatives of std::out_of_range) if the year, month or day are out of range." In my use case, I know for sure that the year, month and date are all in the valid range of values, so all the validity checks done by the library become redundant. Is it possible to somehow bypass those checks?

1 0

Re: [Boost-users] Building Boost 1.62 With Visual Studio 2017 RC
by Trueman, Chris 24 Nov '16

24 Nov '16

1 0

Building Boost 1.62 With Visual Studio 2017 RC
by Trueman, Chris 24 Nov '16

24 Nov '16

2 1

Assertion failure in r_c_shortest_paths.hpp
by Amit Prakash Ambasta 23 Nov '16

23 Nov '16

Hi, I have a sample r_c_shortest_paths use case demonstrated below. However on executing this code, assertion error occurs at /usr/include/boost/graph/r_c_shortest_paths.hpp:473: Assertion `p_cur_label->b_is_valid' failed. I've referred to the prior issue reported at https://svn.boost.org/trac/boost/ticket/11723 However, against his example specified, I can not reproduce the error.

1 0

[release] Boost 1.63.0 Beta 1
by Marshall Clow 21 Nov '16

21 Nov '16

The first beta packages for 1.63.0 beta 1 are now available: <https://sourceforge.net/projects/boost/files/boost/1.63.0.beta.1/> The SHA256 checksums are as follows: 3dbc1bca10941710755c13a00b1ae56d2d37fe90bbadcf9746203194f9d33e3a boost_1_63_0.7z c8b986fd57e436fd88dbc70e51d3e21efa2be3bdf835fa499b2cf6c0a8cc2985 boost_1_63_0.tar.bz2 745d99e4be9c0f324ec7ba15b7d228fd780067f2e8aeae2f16660a4cf6e6a051 boost_1_63_0.tar.gz e66bd6e2f637148c314398b92bc1f3cbdc777ee282f9de7885697afad3d9c202 boost_1_63_0.zip As always, the release managers would appreciate it if you download the archive of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. Thanks! -- The release managers

3 4

beginner boost::statechart questions
by Bedeho Mender 20 Nov '16

20 Nov '16

Hi, I have a few questions about the statechart library. 1) I would like to pass around a representation of the current configuration of a machine, to allow inspection of local variables and active states. The easiest approach would be to just pass around a copy of the machine, but this is not possible since the state_machine class is noncopyable. An alternative could have been to pass around a constant ref/ptr to the machine, but this is also not workable because the inspection will happen in another thread, and synchronisation is not feasible. Any suggestions? One alternative is to create a new snapshot representation, but it will be a headache to keep in synch with the primary machine. 2) A related question is whether there is a good way to start a machine in a given configuration? Using a sequence of events works in principle, but its a very impractical way to do so. For example if one wishes to restore a configuration from a prior session, then the client code has to log the full event history, and it may have a very hard time determining how many events need to be logged to reconstruct the given configuration. Logging and storing *all* events from the prior session will in many cases be wasteful, or even infeasible. 3) Suppose a machine makes a certain callback to client code in a set of different reactions. It would be nice if the client could inspect the currently active state, from which the given reaction is originating. However, my understanding is that the machine is unstable when processing a reaction, hence this is not possible. Is there a way around this? Best Bedeho Mender ᐧ

1 0

[geometry] Cannot compile boost::geometry::intersection
by Stanley Friesen 17 Nov '16

17 Nov '16

I am using boost library version 1.54 with gcc --std=c++11. I am trying a simple use of geometry::intersection as follows: #include <boost/geometry.hpp> #include <boost/geometry/geometries/point_xy.hpp> #include <boost/geometry/geometries/polygon.hpp> #include <boost/geometry/geometries/adapted/boost_polygon.hpp> using namespace boost::geometry; ...... typedef model::d2::point_xy<double> point_xy; model::polygon<point_xy> clipBounds; // add points to clipBounds model::polygon<point_xy> area; // add points to area model::polygon<point_xy> result; if(boost::geometry::intersection(area, clipBounds, result)) { std::cout << std::endl << "Boost intersection, size = " << num_points(result) << std::endl; } If I comment out the call to intersection, everything compiles. With it I get: In file included from /usr/include/boost/serialization/level.hpp:28:0, from /usr/include/boost/serialization/nvp.hpp:31, from ...: /usr/include/boost/mpl/eval_if.hpp: In instantiation of ‘struct boost::mpl::eval_if_c<false, boost::range_const_iterator<boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double, boost::geometry::cs::cartesian> > >, boost::range_mutable_iterator<boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double, boost::geometry::cs::cartesian> > > >’: /usr/include/boost/range/iterator.hpp:63:63: required from ‘struct boost::range_iterator<boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double, boost::geometry::cs::cartesian> > >’ /usr/include/boost/range/value_type.hpp:30:12: required from ‘struct boost::range_value<boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double, boost::geometry::cs::cartesian> > >’ /usr/include/boost/geometry/algorithms/intersection.hpp:97:64: required from ‘static bool boost::geometry::dispatch::intersection<Geometry1, Geometry2, Tag1, Tag2, Reverse>::apply(const Geometry1&, const Geometry2&, GeometryOut&, const Strategy&) [with GeometryOut = boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double, boost::geometry::cs::cartesian> >; Strategy = boost::geometry::strategy_intersection<boost::geometry::cartesian_tag, boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double, boost::geometry::cs::cartesian> >, boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double, boost::geometry::cs::cartesian> >, boost::geometry::model::d2::point_xy<double, boost::geometry::cs::cartesian>, void>; Geometry1 = boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double, boost::geometry::cs::cartesian> >; Geometry2 = boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double, boost::geometry::cs::cartesian> >; Tag1 = boost::geometry::polygon_tag; Tag2 = boost::geometry::polygon_tag; bool Reverse = false]’ /usr/include/boost/geometry/algorithms/intersection.hpp:201:67: required from ‘bool boost::geometry::intersection(const Geometry1&, const Geometry2&, GeometryOut&) [with Geometry1 = boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double, boost::geometry::cs::cartesian> >; Geometry2 = boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double, boost::geometry::cs::cartesian> >; GeometryOut = boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double, boost::geometry::cs::cartesian> >]’ /home/stanley/workspace/worldmodel/metric/map/GISCache.cpp:2492:62: required from here /usr/include/boost/mpl/eval_if.hpp:60:31: error: no type named ‘type’ in ‘boost::mpl::eval_if_c<false, boost::range_const_iterator<boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double, boost::geometry::cs::cartesian> > >, boost::range_mutable_iterator<boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double, boost::geometry::cs::cartesian> > > >::f_ {aka struct boost::range_mutable_iterator<boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double, boost::geometry::cs::cartesian> > >}’ typedef typename f_::type type; Since my code is virtually identical to the sample code in the documentation, I am very puzzled by this. What have I missed? How do I get this to compile? (I do find it odd that this error refers to boost/serialization rather than boost/geometry, but I suppose that has to do with the order of inclusion). -- View this message in context: http://boost.2283326.n4.nabble.com/geometry-Cannot-compile-boost-geometry-i… Sent from the Boost - Users mailing list archive at Nabble.com.

2 4

[statechart] Pass event data to state constructor using triggering_event
by ramonpadilla1＠yahoo.co.uk 16 Nov '16

16 Nov '16

I would like to be able to communicate the data from an event to a state that gets constructed as a result of a transition. From this post in 2009 and this one in 2010 the use of triggering_event() is suggested. However, I can't find an example anywhere that demonstrates how to use it. Can anyone help? Links in the message | Google Groups | | | | Boost - Users - [statechart] Passing pa... | |

1 0

[statechart] Passing parameters from event to State Local Storage
by Christophe Bourez 16 Nov '16

16 Nov '16

I need to maintain a parameter into the state local storage. This parameter is initially contained in the event that causes the transition to the target state. I give hereafter a small illustrative example. typename sc = boost::statechart; class EvTest : public sc::event<EvTest> { public: EvTest(std::size_t val) : value(val) {} std::size_t getValue() const { return this->value; } private: std::size_t value; }; class MyStateMachine; class StSource; class StTarget; class StSource : public sc::simple_state<StSource, MyStateMachine> { public: typedef sc::custom_reaction<EvTest> reactions; sc::result react(const EvTest &event) { // How to pass event.getValue() to the target state ? transit<StTarget>(); } }; class StTarget : public sc::simple_state<StTarget, MyStateMachine> { public: StTarget(std::size_t val) : val(value) {} private: std::size_t value; }; Thanks, Christophe

5 6