Added a precondition for merge_edge(e1, e2) that requires that two
halfedges have the same direction.
## Summary of Changes
The title says it all
## Release Management
* Affected package(s): Arrangement_on_surface_2
* Issue(s) solved (if any): fix#8659
* Feature/Small Feature (if any):
* Link to compiled documentation:
* License and copyright ownership: TAU
Spelling correction
As this is a spelling correction is in code (and outside my normal realm
of PRs) I created a separate PR for it. I cannot test it, b I'm quite
confident that it won't lead to problems. I think the old name contained
a typo.
Spelling correction
As this is a spelling correction is in code (and outside my normal realm of PRs) I created a separate PR for it.
I cannot test it, b I'm quite confident that it won't lead to problems. I think the old name contained a typo.
The formula in Documentation/doc/biblio/cgal_manual.bib
```
@article{cgal:cgm-fobbo-11,
title={Fast Oriented Bounding Box Optimization on the Rotation Group $\SO(3, \mathrm{R})$},
author={Chang, Chia-Tche and Gorissen, Bastien and Melchior, Samuel},
```
renders incorrectly (see Optimal_bounding_box/citelist.html) as there is
no command `\SO` in LaTeX
The formula in doc/Kernel_d/CGAL/Kernel_d/Aff_transformation_d.h
```
\pre \f$ sin_num^2 + cos_num^2 = den^2\f$ and \f$ 0 \leq e_1 < e_2 < d\f$.
```
renders in an unexpected way (see
Kernel_d/classCGAL_1_1Aff__transformation__d.html) as the `_` is seen as
subscript operator in LaTeX
## Summary of Changes
Solve a bug for CMap and GMap when we iterate on an empty map with an
iterator that needs to mark cells, and when using index version.
## Release Management
* Affected package(s): CMap GMap
- compare doxygen version with the available directories on disk and
(try to) use the most appropriate one
- give a warning when there are more directories than expected (already
present), though `FATAL` should probably be `FATAL_ERROR` though the
latest will give problems when adding a new version to the directory
list for testing. Changed the message to a `WARNING`
It is not clear to me that this is the right thing to do:
- it is done for some classes
- but in some test, a comment mention that it should be uninitialized
(the test works if init to -1 but not to 0).
- Base_time_stamper is doing an init to -2
## Release Management
* Affected package(s):
* Issue(s) solved (if any): fix#7781#7782
* Feature/Small Feature (if any):
* Link to compiled documentation (obligatory for small feature) [*wrong
link name to be changed*](httpssss://wrong_URL_to_be_changed/Manual/Pkg)
* License and copyright ownership:
Andreas Fabri
Sven Oesau
Sebastien Loriot
albert-github
Efi Fogel
Guillaume Damiand