1
edit
Changes
m
Cleaned up display of Table of Contents
{{OOP344 Index}}
=1.0 Participants===1.1 Team Members==
{| class="wikitable sortable" border="1" cellpadding="5" align="center"
|+ OOP344 - Team Nothing - 20102
== 1.2 Team Contact Person ==
'''[mailto:kmsingh@learn.senecac.on.ca Kerry Singh]''' <br/>
=2.0 Project Development Page=
[[OOP244 - Team Nothing Project Dev Page - 20101 | Project Development Page]]
=3.0 IRC Chatlogs / Meeting Logs=
[[OOP344 - Team Nothing IRC Logs - 20102 | IRC meeting logs]]
==3.1 30-May-102010==
[[OOP344_-_Team_Nothing_IRC_Logs_-_20102#30-May-10 Channel: #Team-Nothing|Channel #Team-Nothing]]
==3.2 10-June-June102010==
[[OOP344_-_Team_Nothing_IRC_Logs_-_20102#10-June-10 Channel: #Team-Nothing|Channel #Team-Nothing]]
=4.0 Conventions and Styles===4.1 Function Conventions=====4.1.1 Function Naming Convention===
Function names are all lowercase and each word is separated by an underscore character.
</pre>
===4.1.2 Function Comments===
Each function definition should include a comment above it that includes the function name, a brief and clear description of what each variable does in the function, and a clear and concise description of what the function does.
<pre>
</pre>
==4.2 Variable Conventions=====4.2.1 Naming Convention===
Similar to the [[OOP344_-_Team_Nothing_-_20102#4.1 Function Naming Convention|4.1 Function Naming Convention]]
</pre>
===4.2.2 Variable Definitions===
Define each variable on a speparate line.
</pre>
==4.3 File Headings==
Each file with the extension of *.cpp, *.c, and *.h must include a comment heading at the beginning of the file stating the file name, author (and username), date created, last modified date, and description of what the file does. The description should be clear and concise. This must be enclosed using /* and */.
==4.4 Indentation Level==
Use an indentation level of two spaces in all situations. Do not use TAB for indentation.
</pre>
==4.5 Curly Braces==
Each { and } for a code block, such as in an if statement or a for loop, should be placed on its own separate line, with the { and } lined up with the first character of the line above it. If the code block consists of only one line of code, continue to use the curly braces for clarity and in case additional code is added afterwards.
<pre>
</pre>
==4.6 Conditional Compilation=====4.6.1 Naming Convention for Header Files===
Prefix the names of header files that we create with "tn" (initials of Team Nothing) followed by an underscore character. For example, tn_headerfile.h