Changes between Version 11 and Version 12 of Developer/Coding/NamingRules
- Timestamp:
- 11/22/14 04:47:04 (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Developer/Coding/NamingRules
v11 v12 25 25 = RTEMS internal interfaces = 26 26 27 = SuperCore=27 == Super Core == 28 28 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 SuperCoreModules.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. 30 30 * Use "Module_name_Particular_type_name" for type names. 31 31 * Use "_Module_name_Particular_function_name" for functions names. … … 44 44 } The_module_Type_name; 45 45 }}} 46 = =BSP==46 === BSP === 47 47 48 48 * TODO. Is a BSP really internal? It is kind of part of an application...