Changes between Version 11 and Version 12 of Developer/Coding/NamingRules


Ignore:
Timestamp:
Nov 22, 2014, 4:47:04 AM (5 years ago)
Author:
Chris Johns
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Developer/Coding/NamingRules

    v11 v12  
    2525= RTEMS internal interfaces =
    2626
    27 = SuperCore =
     27== Super Core ==
    2828
    29 SuperCore is organized in an Object-Oriented fashion. Each score Manager is a Package, or Module, and each Module contains type definitions, functions, etc. The following summarizes our conventions for using names within SuperCore Modules.
     29[http://docs.rtems.org/doxygen/cpukit/html/ SuperCore] is organized in an Object-Oriented fashion. Each score Manager is a Package, or Module, and each Module contains type definitions, functions, etc. The following summarizes our conventions for using names within [http://docs.rtems.org/doxygen/cpukit/html/ SuperCore] Modules.
    3030 *  Use "Module_name_Particular_type_name" for type names.
    3131 *  Use "_Module_name_Particular_function_name" for functions names.
     
    4444} The_module_Type_name;
    4545}}}
    46 = =BSP ==
     46=== BSP ===
    4747
    4848 *  TODO. Is a BSP really internal? It is kind of part of an application...