From ff13e4b75aed925edb996ea376d114af1262edd1 Mon Sep 17 00:00:00 2001 From: Gregory Nutt Date: Mon, 10 Mar 2014 08:12:35 -0600 Subject: [PATCH] Add support for TM4C GPIOs --- Documentation/NuttXCCodingStandard.html | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/Documentation/NuttXCCodingStandard.html b/Documentation/NuttXCCodingStandard.html index 946c63763d..0693efc50f 100755 --- a/Documentation/NuttXCCodingStandard.html +++ b/Documentation/NuttXCCodingStandard.html @@ -12,7 +12,7 @@

NuttX C Coding Standard

-

Last Updated: February 6, 2014

+

Last Updated: March 9, 2014

@@ -1747,17 +1747,26 @@ ptr = (FAR struct somestruct_s *)value;
  • Braces in column 1 - 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.
  • First definition or statement in column 3. The first data definitions or statements in the function body are idented by two spaces. Standards for statements are covered in the following paragaraph
    • +
  • + Local variables first. + 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. +
  • Long functions are discouraged. 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).
    • +
  • + Space after the function boady + A one (and only one) blank line must follow the closing right brace of the function body. +

    • Returned Values