mirror of https://github.com/CGAL/cgal
Capitalized headings
This commit is contained in:
parent
bf2603fee8
commit
c04f69ed64
|
|
@ -63,7 +63,7 @@ be the case, due to round off errors.
|
|||
So, exactness checks should only be turned on if the computation is done
|
||||
with some exact number type.
|
||||
|
||||
\section{Altering the failure behaviour}
|
||||
\section{Altering the Failure Behaviour}
|
||||
|
||||
As stated above, if a postcondition, precondition or assertion is
|
||||
violated, the program will abort (stop and produce a core dump).
|
||||
|
|
@ -101,7 +101,7 @@ The only difference is that for warnings the default value is
|
|||
set_warning_behaviour(Failure_behaviour eb);}
|
||||
\ccGlueEnd
|
||||
|
||||
\section{Control at a finer granularity}
|
||||
\section{Control at a Finer Granularity}
|
||||
|
||||
The compile time flags as described up to now all operate on the whole
|
||||
library.
|
||||
|
|
@ -116,7 +116,7 @@ The name of a particular module is documented with that module.
|
|||
|
||||
\begin{ccAdvanced}
|
||||
|
||||
\section{Customising how errors are reported}
|
||||
\section{Customising how Errors are Reported}
|
||||
|
||||
Normally, error messages are written to the standard error output.
|
||||
It is possible to do something different with them.
|
||||
|
|
|
|||
Loading…
Reference in New Issue