From 4a6d766d8cd128357120dd1a73bc803e8fb98017 Mon Sep 17 00:00:00 2001 From: Efi Fogel Date: Sat, 6 Sep 2025 20:56:06 +0300 Subject: [PATCH] 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 --- Installation/CHANGES.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/Installation/CHANGES.md b/Installation/CHANGES.md index 39dbf87a208..95e9e63a633 100644 --- a/Installation/CHANGES.md +++ b/Installation/CHANGES.md @@ -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)