Subject: Re: [geometry] Run-Time specified geometries
From: Mateusz Loskot (mateusz_at_[hidden])
Date: 2013-10-25 19:08:54
On 25 October 2013 16:58, Samuel Debionne
>> To know which algorithms are migrated, just grep
>> boost/geometry/algorithms for "resolve_variant".
> For the records :
> * append
> * area
> * buffer
> * centroid
> * clear
> * convert
> * convex_hull
> * correct
> * equals
> * length
> * num_points
Nice one, thanks!
>> No API change is expected to happen once an algorithm is migrated (only
>> internal refactorings will happen) so I assume you can safely start
>> using those that are migrated even though it's not yet documented.
> To give it a shot I try to add variant support to "distance" taking
> "correct" as an example. Binary operation are more challenging since
> support for combinations (variant, variant), (non-variant, variant),
> (variant, non-variant) needs to be implemented. Moreover, if the variant
> has 2d and 3d points, the dimension of both geometry must be checked to
> be the same. That raise the question how to report runtime errors ?
> Exception ?
IMHO, any issue that can't be reported at compile-time as static check,
qualifies as an exception at run-time.
AFAIR, we've agreed for Boost.Geometry to throw on errors.
-- Mateusz Loskot, http://mateusz.loskot.net
Geometry list run by mateusz at loskot.net