1
edit
Changes
no edit summary
=''We are FjXR, Code fixers are ready to go!''=
== Group member=={| class="wikitable sortable" border="1" cellpadding="5" align="centerauto"|+ OOP344 - FjXR - '''TERM 20102'''! ID !! First Name !! Last Name !! Section !! Seneca Id !! wiki id !! IRC nick !! Blog URL
|-
| A || [[User:Xlu44 | Xiongwen Lu ]] || xlu44 || A || [mailto:xlu44@learn.senecac.on.ca xlu44] || [[Special:Contributions/xlu44 | xlu44]] || xlu44 || [http://myoop344blog.blogspot.com/ my blog]
|-
| B || [[User:jpark68 | Junseok]] || Park|| A ||[mailto:jpark68@learn.senecac.on.ca Junseok] || [[Special:Contributions/jpark68 | jpark68]] || jpark68|| [http://jpark68.blogspot.com/ My Blog]
| D || [[User:Priya | Priya]] || Gill || A ||[mailto:pkgill5@learn.senecac.on.ca pkgill5] || [[Special:Contributions/priya | priya]] || pkgill5|| [http://rhui4.wordpress.com/ My Blog]
|-
| E || [[User:lwang168 | Liang Wang ]] || lwang168 || A || [mailto:lwang168@learn.senecac.on.ca lwang168] || [[Special:Contributions/lwang168 | lwang168]] || lwang168 || [http://lwang168.blogspot.com/ my blog]
|-
|}
== Notification Window ==
<!--<object width="250" height="360" id="obj_1275427285642"><param name="movie" value="http://fjxr.chatango.com/group"/><param name="wmode" value="transparent"/><param name="AllowScriptAccess" VALUE="always"/><param name="AllowNetworking" VALUE="all"/><param name="AllowFullScreen" VALUE="true"/><param name="flashvars" value="cid=1275427285642&b=60&f=50&l=999999&q=999999&r=100&s=1"/--><embed id="emb_1275427285642" src="http://fjxr.chatango.com/group" width="250" height="360" wmode="transparent" allowScriptAccess="always" allowNetworking="all" type="application/x-shockwave-flash" allowFullScreen="true" flashvars="cid=1275427285642&b=60&f=50&l=999999&q=999999&r=100&s=1"></embed><!--/object><br>[ <a href="http://fjxr.chatango.com/clonegroup?ts=1275427285642">Copy this</a> | <a href="http://chatango.com/creategroup?ts=1275427285642">Start New</a> | <a href="http://fjxr.chatango.com">Full Size</a> ]-->
== Coding Style ==
* References from the books of "Thinking in C++ (2nd Edition) by Bruce Eckel" and " Programming Windows with MFC (2nd edition) by Jeff Prosise, Microsoft Press "
* download the book here.<br/>
Thinking in C++,Volume 1, 2nd Edition by Bruce Eckel<br/>
http://matrix.senecac.on.ca/~jpark68/TIC2Vone.pdf <br/>
Volume 2: Standard Libraries & Advanced Topics<br/>
http://matrix.senecac.on.ca/~jpark68/TIC2Vtwo.pdf <br/>
<p>
Prefixes are often combined to form other prefixes, as when '''p''' and '''sz''' are joined to form '''psz''', which stands for "pointer to zero-terminated string." </p>
{| class="wikitable sortable" border="1" cellpadding="5" align="centerauto"
! Prefix !! Data Type
|-
| b || BOOL
|-
|}
=== File names ===
statement, etc.”). This is a single, consistent rule I apply to all of the
code I write, and it makes formatting much simpler. It makes the
“scannability” easier – when you look at this line:</p><br/> example: int func(int a);<br/><br/>
<p>
you know, by the semicolon at the end of the line, that this is a
declaration and it goes no further, but when you see the line:</p>
<p>
you immediately know it’s a definition because the line finishes
there’s no difference in where you place the opening parenthesis
for a multi-line definition:</p>
<p>and for a single-line definition that is often used for inlines:</p>
<p>
Placing the ‘{‘ on the next line eliminates some confusing code
in complex conditionals, aiding in the scannability. Example:
</p>
<p>
The above has poor scannability. However,
</p>
Finally, it’s much easier to visually align braces when they are
aligned in the same column. They visually "stick out" much
better.</p><br/><br/>
=== Identifier names ===
capitalizing each word. So a class looks like this:</p><br/><br/>
example: class FrenchVanilla : public IceCream {<br/><br/>
an object identifier looks like this:<br/><br/>
example: FrenchVanilla myIceCreamCone(3);<br/><br/>
and a function looks like this:<br/><br/>
example: void eatIceCreamCone();<br/><br/>
(for either a member function or a regular function).<br/>
=== Include guards on header files ===
and replacing the ‘.’ with an underscore. For example:</p><br/>
example:
=== Use of namespaces ===
if you change the namespace outside of a function or class, you will cause
that change to occur for any file that includes your header,
resulting in all kinds of problems.
In cpp files, any global using directives will only affect that file,
and so you are generally used to produce more easilyreadable
code, especially in small programs.
example:
