Boost C++ Libraries: Ticket #5730: strategy selection error in the distance function https://svn.boost.org/trac10/ticket/5730 <p> file : \boost\geometry\algorithms\distance.hpp </p> <p> line : 134 </p> <p> before (bug ?) : return_type const ds = ps_strategy.apply(point, *prev, *it); </p> <p> after (patched) : return_type const ds = eps_strategy.apply(point, *prev, *it); </p> <p> from the line 125, 128 and 139 eps_strategy seems the more appropriate. </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/5730 Trac 1.4.3 Barend Gehrels Sat, 03 Sep 2011 13:03:47 GMT milestone changed https://svn.boost.org/trac10/ticket/5730#comment:1 https://svn.boost.org/trac10/ticket/5730#comment:1 <ul> <li><strong>milestone</strong> <span class="trac-field-old">To Be Determined</span> → <span class="trac-field-new">Boost 1.48.0</span> </li> </ul> <p> There is indeed something wrong here. But it is not as simple as changing this line only. Will look at it soon. </p> Ticket Mateusz Loskot Thu, 06 Oct 2011 16:46:33 GMT <link>https://svn.boost.org/trac10/ticket/5730#comment:2 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/5730#comment:2</guid> <description> <p> Is this new report related <a class="closed ticket" href="https://svn.boost.org/trac10/ticket/5954" title="#5954: Bugs: distance_pythagoras skips sqrt() step (closed: fixed)">#5954</a> ? </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Barend Gehrels</dc:creator> <pubDate>Fri, 24 Feb 2012 12:39:37 GMT</pubDate> <title>status changed; resolution set https://svn.boost.org/trac10/ticket/5730#comment:3 https://svn.boost.org/trac10/ticket/5730#comment:3 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">fixed</span> </li> </ul> <p> This was indeed a problem. Actually it was more severe than I first thought. A patch was supplied recently and is applied now. The additional issue was that after that patch the unit test did not run anymore, and that is fixed as well. Sorry that this was delayed. </p> Ticket