Geometry Boost List: Re: [geometry] bug in 07_b_graph_route_example.cpp

Subject: Re: [geometry] bug in 07_b_graph_route_example.cpp
From: Menelaos Karavelas (menelaos.karavelas_at_[hidden])
Date: 2015-06-16 18:37:23

Hi Andrew.

On 16/06/2015 09:45 μμ, Andrew Hundt wrote:
>
>
> On Mon, Apr 6, 2015 at 4:53 PM, Andrew Hundt <athundt_at_[hidden] 
> <mailto:athundt_at_[hidden]>> wrote:
>
>     In build_route():
>
>     https://github.com/boostorg/geometry/blob/master/example/07_b_graph_route_example.cpp#L237
>
>     https://github.com/boostorg/geometry/blob/master/example/07_b_graph_route_example.cpp#L240
>
>     The ordering that is output is flipped between each
>     add_edge_to_route call.
>
>     I believe the correct order is:
>
>         add_edge_to_route(graph, pred, vertex2, route);
>         while (pred != vertex1)
>         {
>             add_edge_to_route(graph, predecessors[pred], pred, route);
>             pred = predecessors[pred];
>         }
>
>     This still leaves duplicate points which may be a bit wasteful but
>     at least it doesn't seem like any steps will be backwards!
>
>     Also, I'm a little sad the github issues are gone, they are very
>     convenient and easy to use. Should I report this under the old svn
>     trac issues?
>
>

Issues are indeed disabled for the Boost.Geometry repository, so your 
only option currently is to report this in Trac.

BTW, do members of this list have an opinion about GitHub issues? Should 
we use them instead of Trac?

- m.

> I wanted to follow up on this since I haven't heard anything.
>
>
> Cheers!
> Andrew Hundt
>
>
> _______________________________________________
> Geometry mailing list
> Geometry_at_[hidden]
> http://lists.boost.org/mailman/listinfo.cgi/geometry