PCSX2 Documentation/Code Formatting Guidelines: Difference between revisions
PCSX2 Documentation/Code Formatting Guidelines (view source)
Revision as of 22:42, 8 January 2015
, 8 January 2015→Topic 2: Using PCSX2 and wxWidgets base types instead of C/C++ atomic types.
| Line 25: | Line 25: | ||
Note that using the C++ atomic types <code>float</code> and <code>double</code> are acceptable, and that there are no defined alternatives at this time. | Note that using the C++ atomic types <code>float</code> and <code>double</code> are acceptable, and that there are no defined alternatives at this time. | ||
'''Special note:''' PCSX2-specific types <code>uptr</code> and <code>sptr</code> are meant to be integer-typed containers for pointer addresses, and should be used in situations where pointer arithmetic is needed. <code>uptr/sptr</code> definitions are not type safe and <code>void*</code> or <code>u8*</code> should be used for parameter passing instead, when possible. | |||
==Topic 3: Do not use <code>private</code> class members; use <code>protected</code> instead.== | ==Topic 3: Do not use <code>private</code> class members; use <code>protected</code> instead.== | ||