Just realized the my the visitor of the surface sweep has never been published, so changes to it are not concidered as breaking backward compatibilty

This commit is contained in:
Efi Fogel 2025-09-06 20:56:06 +03:00
parent f8c9340c1c
commit 4a6d766d8c
1 changed files with 3 additions and 5 deletions

View File

@ -159,14 +159,12 @@ Release date: July 2025
- Optimized `do_intersect()`: (i) made it robust even with an inexact-predicate kernel, and (ii) made it quit
once an intersection is detected. (In the past, the intersection was computed in one phase and examined in a
subsequent phase.) This optimization break backward compatibility in two places:
1. The variants of the free function `do_intersect()` that accept a third optional parameter, namely UsePolylines,
subsequent phase.) This optimization somehow breaks backward compatibility as follows.
The variants of the free function `do_intersect()` that accept a third optional parameter, namely UsePolylines,
which determines whether the boundaries of the input polygons are treated as cyclic sequences of
(`x`-monotone) segments or as a cyclic sequences of (`x`-monotone) polylines, do not accept this third
parameter any longer. (This third optional parameter was introduced a few years ago, and now abandoned for
parameter any longer. (This third optional parameter was introduced a few years ago, and now abandoned only for
`do_intersect()`.)
2. One of the visitor overloaded functions `update_event()` of the surface sweep visitor now accepts a fifth
parameter, namely, the multiplicity.
## [Release 6.0.1](https://github.com/CGAL/cgal/releases/tag/v6.0.1)