DevCodeStyle

About Code Style Guidelines
These guidelines are just that, guidelines not laws. We make every attempt to follow these guidelines and are currently updating older files to match this standard when we find them. Please report all violations of these guidelines as bugs on the Issue Tracker.

See ReportingBugs

Indention

 * All indention from the beginning of a line should be in TAB characters.
 * Constant alignment indention should use SPACE characters.
 * Procedure definitions split over two or more lines should use TAB characters to indent to the first ( then SPACE characters to further align.
 * These blocks should be indented:
 * for ... next
 * do ... loop
 * while ... wend
 * sub/function ... end sub/function
 * type ... end type
 * scope ... end scope
 * with ... end with

Naming Conventions

 * Underscores should only be used in macros, constants and defines.
 * All macros in the Template System should be CamelCase starting with lowercase prefix 'fbext_'
 * All other macros, constants and defines should be in all uppercase with the prefix 'FBEXT_'
 * Namespace names should be all lowercase.
 * Classes should be CamelCase starting with a uppercase letter.
 * All procedures ( subs and functions ) should be CamelCase starting with a lowercase letter.
 * Public member variables of a single letter should be uppercase, all others should follow procedure naming.

Whitespace

 * Whitespace should be applied liberally to improve readability.

Conclusion
These guidelines are subject to change and are up for discussion on the Talk:DevCodeStyle page or any other contact means.

See ContactingDevelopers