[test][algorithms] add unit test for num_segments algorithm
[algorithms][num_segments] add num_segments algorithm: computes
the number of segments in a geometry (including geometry variants)
[algorithms][num_segments] add doxy/qbk documentation
[geometry] include algorithm num_segments
[test][algorithms] include unit test for num_segments in Jamfile
[doc][num_segments] add group for num_segments algorithm
[doc] add num_segments algorithm
[doc] add num_segments algorithm
[doc] add qbk documentation for num_segments algorithm
[doc][support status] add num_segments algorithm
[doc][examples] add example for num_segments algorithm
Merge branch 'develop' of https://github.com/boostorg/geometry into feature/num_segments
Merge branch 'develop' of https://github.com/boostorg/geometry into feature/num_segments
[doc][examples][num_segments] use an open polygon instead of a closed one;
call also num_segments with the second (optional) argument set to true;
Merge branch 'develop' of https://github.com/boostorg/geometry into feature/num_segments
Merge branch 'develop' of https://github.com/boostorg/geometry into feature/num_segments
[strategies] Add missing include to point_in_poly_winding
[algorithms][intersects] change robustness policy to no_rescale_policy
Merge pull request #118 from mkaravel/fix/intersects-no-rescale

[algorithms][intersects] change robustness policy to no_rescale_policy
[algorithms][get_turn_info] fix bug reported by Jeremy Murphy on
the boost mailing list; in collinear_opposite the set_tp method
was assuming that all point types passed to it are the same; this
is not the case: there are two different point types; the problem
appeared when using point_xy in rtree and running intersects queries;
in this case get_turn_info was instantiated with two different point types,
the one used by the user and the one used by the rtree to store boxes,
which were different.