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

Update Tasks-Library_Design.xml - typos, title case

Browse source
This commit is contained in:
Mirek Jahoda 2017-10-23 15:33:09 +00:00
parent 6eb9344ea0
commit d0c00172ee
1 changed files with 6 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

12
en-US/Tasks-Library_Design.xml
View file

@ -4,16 +4,16 @@
<chapter id="chap-Defensive_Coding-Tasks-Library_Design">
<title>Library Design</title>
<para>
Throught this section, the term <emphasis>client code</emphasis>
Through this section, the term <emphasis>client code</emphasis>
refers to applications and other libraries using the library.
</para>
<section>
<title>State management</title>
<title>State Management</title>
<para>
</para>
<section>
<title>Global state</title>
<title>Global State</title>
<para>
Global state should be avoided.
</para>
@ -77,7 +77,7 @@
</section>
<section>
<title>Object orientation</title>
<title>Object Orientation</title>
<para>
Classes should be either designed as base classes, or it should
be impossible to use them as base classes (like
@ -147,7 +147,7 @@
</section>
<section>
<title>Process attributes</title>
<title>Process Attributes</title>
<para>
Several attributes are global and affect all code in the
process, not just the library that manipulates them.
@ -179,7 +179,7 @@
Library code should avoid manipulating these global process
attributes. It should not rely on environment variables, umask,
the current working directory and signal masks because these
attributes can be inherted from an untrusted source.
attributes can be inherited from an untrusted source.
</para>
<para>
In addition, there are obvious process-wide aspects such as the