sergiotarxz/nuttx
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Add support for TM4C GPIOs

Browse Source
This commit is contained in:
Gregory Nutt 2014-03-10 08:12:35 -06:00
parent e208b50b63
commit ff13e4b75a
1 changed files with 11 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
Documentation/NuttXCCodingStandard.html
View File

@ -12,7 +12,7 @@
<h1><big><font color="#3c34ec">
<i>NuttX C Coding Standard</i>
</font></big></h1>
<p>Last Updated: February 6, 2014</p>
<p>Last Updated: March 9, 2014</p>
</td>
</tr>
</table>
@ -1747,17 +1747,26 @@ ptr = (FAR struct somestruct_s *)value;
</li>
<li>
<b>Braces in column 1</b>
The opening and close braces of the compound statement mst be placed in column one.
The opening and close braces of the compound statement must be placed in column one.
</li>
<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>
</li>
<li>
<b>Local variables first</b>.
Because NuttX conforms to the older C89 standard, all variables that have scope over the entire compound statement must be defined at the beginning of the compound statement.
A single blank line must follow the local variable definitions.
</li>
<li>
<b>Long functions are discouraged</b>.
As a rule of thumb, the length of a function should be limited so that it would fit on a single page (if you were to print the source code).
</li>
<li>
<b>Space after the function boady</b>
A one (and only one) blank line must follow the closing right brace of the function body.
</li>
</ul>
<h2><a name="retvalues">Returned Values</a></h2>