Changes

 == [[OOP344]] - [[OOP344 Student List]] - [[OOP344 Teams]] - [[OOP344 Assignment One]] - [[OOP344 Assignment Two]] - [[OOP344 IRC Schedules 20093 |OOP344 IRC Schedules]]<br />

== 2.2 Group Members==

=== Wen Fang Chen===

=== Yong Hong===

=== Taehoon Kim===

Email: hoongoon86@hotmail.com

=== Chi-Lea Tran===

=== Victor Tran===

 === Cong Wang===

=== Yong Xue === IRC Username: yxue11 Section: C Blog: http://opp344-yxue.blogspot.com/ Email: yxue11@learn.senecac.on.ca === Shun Yao Zhang===

IRC Username== 3.1 Address == svn: yxue11//zenit.senecac.on.ca/ops344_093a06  == 3.2 Usernames and Logins ==  Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4 Wen Fang Chen: ops344_093svn62

SectionYong Hong: Cops344_093svn65

BlogTaehoon Kim: http://opp344-yxue.blogspot.com/ops344_093svn66

EmailChi-Lea Tran: yxue11@learn.senecac.on.caops344_093svn61

3.1 Address svnShun Yao Zhang://zenit.senecac.on.ca/ops344_093a06 3.2 Usernames and Logins ops344_093svn64

= 4.1 File headings0 Conventions and Styles =

Each file with the extension of *.cpp, *.c, and *.h must include a comment heading 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 */. For example:

4.2 Function Comments    Each function should include a comment above the function similar to the file heading (4.1), except only including the function name and a description of what the function does. For example: 

== 4.3 Inline Comments    Inline comments should be used to clarify what exactly something is doing, or to leave a note for yourself or others regarding the code in that general area. Please use inline comments wherever the code might be confusing for others to understand. 4.4 Indent level==

Inline comments should be used to clarify what exactly something is doing, or to leave a note for yourself or others regarding the code in that general area. Please use inline comments wherever the code might be confusing for others to understand.

All documents must have indentation when writing code in a code block== 4. The indent 4 Indent level in any case will consist of two spaces. There will be no tab use. For example:  ==

 4.5 Curly Bracket Use  </pre>

== 4.5 Curly Bracket Use of { } in a code block, such as in an if statement, a for loop, should start on a new line, with the { } lined up with the first character of the line above it. If the code block only has one coded line for the result, please use the curly brackets anyways for readability’s sake. For example:==

Use of { } in a code block, such as in an if statement, a for loop, should start on a new line, with the { } lined up with the first character of the line above it. If the code block only has one coded line for the result, please use the curly brackets anyways for readability’s sake. For example:

== 4.6 Variable Naming Conventions    Variables should follow regular programming conventions ( must start with lowercase letter, no symbols…). Variables should be descriptive for better understanding of it’s For example:==

Variables should follow regular programming conventions ( must start with lowercase letter, no symbols…). Variables should be descriptive for better understanding of it’s For example:

== 4.7 Function Naming Conventions  ==

|+ [[ ASOS Brigade| ASOS Brigade]]! Last Name !! Name !! Seneca Username !! Section !! Blog Url !! IRC Nick !! Current Task !! SVN ID|-| Zhang || Shun Yao || syzhang4 || C || [http://shunyao-CPA.blogspot.com/ MY Blog] || DownWind || IO_MenuBar ||64|-| Hong || Yong || yhong17 || B || [http://xderick.blogspot.com/ xDerick' Blog] || Yong_Clicker || IO_Form, IO_Frame, IO_Field || 65|-| Kim || Taehoon || tkim28 || B || [http://hoonkoon.blogspot.com/ Blog] || hoongoon || IO_Radio || 66|-| Chen || Wen Fang || wfchen || C || [http://wenfangchen.blogspot.com/ Gwen's Blog] || Gwen2009 || IO_Label || 62|-| Xue || Yong || yxue11 || C || [http://opp344-yxue.blogspot.com/ Blog] || yxue11 || IO_Edit,IO_Vedit|| 67|-| Tran || Chi-Lea || ctran13 || C || [http://ctran13.blogspot.com Nitty Gritty] || ctran13 || ciol.c, IO_TextEdit|| 61|-| Tran || Victor || vvtran || C || [http://victran.blogspot.com Blog?] || victran || IO_CheckList || 63|-| Wang || Cong || cwang84 || B || [http://wangcong422.blogspot.com Blog] || cwang84 || IO_Menu || 68|-! Contact: !! - !! - !! - !! - !! - !! - !! -|-| Tran || Chi-Lea || - || - || - || - || - || -|-| Chen || Wen Fang || - || - || -|| - || -|| -|-|} ==