Docs/defensive-coding-guide
2
0
Fork 0
Code Issues 3 Pull requests 1 Projects Releases Packages Wiki Activity Actions

Update C-Language.xml - Title Case

Browse source
This commit is contained in:
Mirek Jahoda 2017-10-23 14:42:25 +00:00
parent 2c48effda9
commit 6f40b81eb0
1 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

10
en-US/C-Language.xml
View file

@ -2,14 +2,14 @@
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
<section id="sect-Defensive_Coding-C-Language">
<title>The core language</title>
<title>The Core Language</title>
<para>
C provides no memory safety. Most recommendations in this section
deal with this aspect of the language.
</para>
<section id="sect-Defensive_Coding-C-Undefined">
<title>Undefined behavior</title>
<title>Undefined Behavior</title>
<para>
Some C constructs are defined to be undefined by the C standard.
This does not only mean that the standard does not describe
@ -32,7 +32,7 @@
</section>
<section id="sect-Defensive_Coding-C-Pointers">
<title>Recommendations for pointers and array handling</title>
<title>Recommendations for Pointers and Array Handling</title>
<para>
Always keep track of the size of the array you are working with.
Often, code is more obviously correct when you keep a pointer
@ -75,7 +75,7 @@
</section>
<section id="sect-Defensive_Coding-C-Arithmetic">
<title>Recommendations for integer arithmetic</title>
<title>Recommendations for Integer Arithmetic</title>
<para>
Overflow in signed integer arithmetic is undefined. This means
that it is not possible to check for overflow after it happened,
@ -174,7 +174,7 @@
</section>
<section id="sect-Defensive_Coding-C-Globals">
<title>Global variables</title>
<title>Global Variables</title>
<para>
Global variables should be avoided because they usually lead to
thread safety hazards. In any case, they should be declared