1
edit
Changes
m
|-
|}
=== (Discussion: Indentation) ===
Something simple, but that should be standard for all pieces of the code.
{| class="wikitable" border="1"
|+ Discussion
! Name !! Comment
|-
| fmDeOliveira || I usually put two spaces for a new indent, and keep a blank line between new big blocks of code and whatever comes before it (usually an if statement, a for loop, or the signature of a function).
→Team Programming Standards
The tab space is interpreted different across different software and operating systems. Use normal spaces to add indentation instead.
====Indent Rule(Discussion: Indentation) ====Something simple, but that should be standard for all pieces of the code. {| class="wikitable" border="1"|+ Discussion! Name !! Comment|-| fmDeOliveira || I usually put two spaces for a new indent, and keep a blank line between new big blocks of code and whatever comes before it (usually an if statement, a for loop, or the signature of a function).|-| MattAdams || Please only indent to 4 spaces. If we all use the same indenting, when it comes to putting our code together it will looks the same.<br /><br />NOTE: Most text editors have the option to change tabs to spaces, so you are still able to press the tab key, however it will convert it to spaces when the file is saved.|-|}
=== Put the pointer identifier(*) right after the target variable type. ===
|-
| fmDeOliveira || I prefer using // for single-line comments and /* */ for blocks of commented code. This would avoid problems commenting out blocks of code that already have single-line comments (the end of the single-line comment would not be interpreted as the end of the block comment).
|-
|}