Changes between Version 12 and Version 13 of Developer/Coding/Conventions


Ignore:
Timestamp:
Mar 7, 2013, 1:08:51 AM (7 years ago)
Author:
Gedare
Comment:

/* Source Code Style */

Legend:

Unmodified
Added
Removed
Modified
  • Developer/Coding/Conventions

    v12 v13  
    5555 *  Use two spaces for indentation, four spaces for hanging indentation.
    5656 *  Adhere to a limit of 80 characters per line.
    57  *  Pay attention to warnings.
     57 *  Pay attention to warnings. Strive to eliminate them.
    5858 *  Check all return statuses.
    59  *  Favor C over assembly language and use inline assembly.
     59 *  Favor C over assembly language, and use inline assembly when possible.
    6060 *  Share code with other targets where possible.
    61  *  Think portable -- RTEMS supports a lot of target hardware.
    62  *  Simple code is easier to debug and easier to read than clever code.
     61 *  Think portable! RTEMS supports a lot of target hardware.
     62 *  Keep it simple! Simple code is easier to debug and easier to read than clever code.
    6363
    6464When in doubt, use the source code in ''cpukit/rtems'' as a style reference.