
2014-02-27 18:32 GMT+01:00 Nathan Hurst <njh@...1927...>:
On Thu, Feb 27, 2014 at 06:15:55PM +0100, Krzysztof Kosi??ski wrote:
CGAL evaluates things in arbitrary precision floating point arithmetic (using the MPFR library) if the result in doubles is ambiguous, which guarantees accurate results in edge cases. If the boolean algorithms depend on this, then it will be hard to extract all the necessary things into 2Geom, though I have not checked this yet. If they don't, it should be fairly simple.
Does the fact that 2Geom is templated across the numerical type help at all?
Is it? I don't see it. Points, matrices, fragments, etc. always use doubles. Some classes use Coord, which is a typedef of double, but others don't.
In any case, CGAL would be completely hidden from the user of 2Geom. Those two libraries have substantially different goals - CGAL emphasizes robustness and generality, while 2Geom emphasizes ease of use. If we could use some of CGAL's algorithms through the user-friendly 2Geom APIs we could have the best of both worlds.
Regards, Krzysztof