Changes between Version 49 and Version 50 of Developer/Coding/Conventions


Ignore:
Timestamp:
May 30, 2014, 6:02:12 PM (5 years ago)
Author:
Gedare
Comment:

/* Maintainability */ New section.

Legend:

Unmodified
Added
Removed
Modified
  • Developer/Coding/Conventions

    v49 v50  
    7474 *  For integer primitives, prefer to use precise-width integer types from stdint.h.
    7575 *  Write code that is 16-bit, 32-bit, and 64-bit friendly.
     76= Maintainability =
     77
     78 *  Minimize modifications to third party code.
     79 *  Keep it simple! Simple code is easier to debug and easier to read than clever code.
     80 *  Share code with other architectures, cpus, and BSPs where possible.
     81 *  Do not duplicate standard OS or C Library routines.
    7682= Miscellaneous =
    7783
    7884 *  Use algorithms with the lowest order of execution. By favoring O(constant) over O(n) algorithms, RTEMS works hard to ensure deterministic execution times as much as possible.
    7985 *  If you need to temporarily change the execution mode of a task/thread, restore it.
    80  *  Minimize modifications to third party code.
    81  *  Keep it simple! Simple code is easier to debug and easier to read than clever code.
    82  *  Share code with other architectures, cpus, and BSPs where possible.
    83  *  Do not duplicate standard OS or C Library routines.
    8486 *  If adding code to ''cpukit'' be sure the filename is unique since all files under that directory get merged into a single library.
    8587 *  Limit execution times in Interrupt and Timer Service Routines (TSRs). TSRs scheduled by rtems_timer_fire_XXX run in the context of the clock tick ISR while TSRs scheduled by rtems_timer_server_fire_XXX run in the context of a dedicated Timer Server task.  Either way, excessive execution times could have a negative impact on the system performance.