- Timestamp:
- Aug 3, 2016 12:38:04 PM (8 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/VBox-CodingGuidelines.cpp
r62705 r62912 44 44 * - Use static wherever possible. This makes the namespace less polluted 45 45 * and avoids nasty name clash problems which can occur, especially on 46 * Unix-like systems. (1) 46 * Unix-like systems. (1) It also simplifies locating callers when 47 * changing it (single source file vs entire VBox tree). 47 48 * 48 49 * - Public names are of the form Domain[Subdomain[]]Method, using mixed … … 482 483 * - The 'g_' (or 'g') prefix means a global variable, either on file or module level. 483 484 * 484 * - The 's_' (or 's') prefix means a static variable inside a function or class. 485 * - The 's_' (or 's') prefix means a static variable inside a function or 486 * class. This is not used for static variables on file level, use 'g_' 487 * for those (logical, right). 485 488 * 486 489 * - The 'm_' (or 'm') prefix means a class data member.
Note:
See TracChangeset
for help on using the changeset viewer.