> In file included from /home/cgal_tester/build/src/cmake/platforms/CentOS5/src/CGAL/all_files.cpp:4:
> /mnt/testsuite/src/CGAL/Turkowski_numeric_solver.cpp:26:7: warning: no newline at end of file
> In file included from /home/cgal_tester/build/src/cmake/platforms/CentOS5/src/CGAL/all_files.cpp:21:
> /mnt/testsuite/src/CGAL/numeric_solvers_support.cpp:27:7: warning: no newline at end of file
> In file included from /home/cgal_tester/build/src/cmake/platforms/CentOS5/src/CGAL/all_files.cpp:25:
> /mnt/testsuite/src/CGAL/JAMA_numeric_solver.cpp:26:7: warning: no newline at end of file
This macro is always defined. Its value will be true when assertions are defined
and false when assertions are not defined. This macro can then be used in place
of a true false constant, such as is needed for CGAL_NOEXCEPT.
This macro is available for future compatibility with c++11, which
by default marks destructors noexcept(true). Some destructors
in CGAL do throw exceptions an so should be marked noexcept(false).
Since noexcept is not available in c++0x and below the macro is
disabled when CGAL_CXX11 is not defined since it is not required.
There was a warning with gcc 4.1.2, on CentOS 5:
```
In file included from /mnt/testsuite/include/CGAL/Kinetic/Active_objects_vector.h:27,
from /mnt/testsuite/include/CGAL/Kinetic/Exact_simulation_traits.h:27,
from /home/cgal_tester/build/src/cmake/platforms/CentOS5/test/Kinetic_data_structures/Delaunay_triangulation_3.cpp:7:
/mnt/testsuite/include/CGAL/Kinetic/internal/debug_counters.h:79:33: warning: no newline at end of file
```
When including CGAL/Polynomial/CORE_Expr_root_stack.h in a header file
that in turn gets included in multiple .cpp files, code from
CORE_Expr_root_stack.h ends up in multiple object files and causes
linking problems:
multiple definition of `CGAL::POLYNOMIAL::operator<<(std::ostream&, CGAL::POLYNOMIAL::CORE_Expr_root_stack const&)'
multiple definition of `CGAL::POLYNOMIAL::internal::operator*(CORE::BigRat const&, CGAL::POLYNOMIAL::internal::CORE_polynomial const&)'
Work around this issue by declaring both operators inline.