Demian Nave wrote:
Arash Partow wrote:
Writing a geometry library is hard, look at CGAL over $1million Euros in funding, both commercial and academic wings and look at the monstrosity they have produced. If you can determine the intersection point of 2 line segments in under 15lines of code using CGAL I take my hat off to you :>
As someone who has *tried* to use CGAL to do intersections and a variety of other operations in under 15 lines of code, I second this statement. My only advice: don't let a Boost geometry library turn into CGAL. :-)
I happen to be one of the CGAL developers, so, given this (implicit) intersection example, how *exactly* would you prefer it to be like? Maybe you are just not using the library correctly? If not, how would you simplify it? P.S: We (the CGAL developers) are well aware of a couple of pending improvements to ease the user experience, but I get the feeling that some users just don't understand the inherent complexity that comes from our fundamental goal of robustness. Best Fernando Cacciola GeometryFactory