Mirrors_Framework/nuttx
1
0
Fork 0
mirror of https://github.com/apache/nuttx.git synced 2026-06-07 09:18:00 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Run codespell -w with the latest dictonary again

Browse Source 
Signed-off-by: Xiang Xiao <xiaoxiang@xiaomi.com>
This commit is contained in:
Xiang Xiao
2020-02-23 16:50:23 +08:00
committed by Abdelatif Guettouche
parent 55a7dfc9a7
commit cde88cabcc
1532 changed files with 3117 additions and 3117 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Documentation/NuttXCCodingStandard.html
+5 -5
View File
@@ -506,7 +506,7 @@
<p>
<b>Indentation</b>
Comments should, typically, be placed before the code section to which they apply.
The comment identation should be the same as the follow identation rules as the following code (if applicable).
The comment indentation should be the same as the follow indentation rules as the following code (if applicable).
</p>
<p>
@@ -803,7 +803,7 @@ void some_function(void)
</li>
<li>
<b>Compound Statements</b>.
Within this document, an opening left brace followed by a sequence of statments, and ending with a closing right brace is referred to as a <i>compound statement</i>.
Within this document, an opening left brace followed by a sequence of statements, and ending with a closing right brace is referred to as a <i>compound statement</i>.
</li>
<li>
<b>Nested Compound Statements</b>.
@@ -984,7 +984,7 @@ int animals(int animal)
<p>
<b>Indentation Unit</b>.
Indentation is in units of two spaces; Each indentation level is twos spaces further to the right than the preceding identation levels.
Indentation is in units of two spaces; Each indentation level is twos spaces further to the right than the preceding indentation levels.
TAB characters may not be used for indentation.
</p>
<center><table width="60%" border=1>
@@ -1791,7 +1791,7 @@ enum xyz_state_e
</li>
<li>
<b>Prefix</b>.
Each related macro value should begin with an upper-case prefix that identifies the value as part of a set of values (and also to mimimize the likelihood of naming collisions).
Each related macro value should begin with an upper-case prefix that identifies the value as part of a set of values (and also to minimize the likelihood of naming collisions).
</li>
<li>
<b>Single space after <code>#define</code></b>.
@@ -2077,7 +2077,7 @@ ptr = (FAR struct somestruct_s *)value;
<li>
<b>First definition or statement in column 3</b>.
The first data definitions or statements in the function body are idented by two spaces.
Standards for statements are covered in the <a href="#statements">following paragaraph</a>
Standards for statements are covered in the <a href="#statements">following paragraph</a>
</li>
<li>
<b>Local variables first</b>.