Added two points to coding rules. See changelog for details.
git-svn-id: svn://svn.gna.org/svn/sgpemv2/trunk@220 3ecf2c5c-341e-0410-92b4-d18e462d057c
This commit is contained in:
parent
2f9d0367cd
commit
a71982d4dc
|
@ -96,6 +96,10 @@ Free Documentation License''.
|
||||||
|
|
||||||
@table @strong
|
@table @strong
|
||||||
|
|
||||||
|
@item 2006, January 27th, @r{--- Luca Vezzaro}
|
||||||
|
Added point on initialization lists and C-style
|
||||||
|
comments.
|
||||||
|
|
||||||
@item 2006, January 26th, @r{--- Matteo Settenvini}
|
@item 2006, January 26th, @r{--- Matteo Settenvini}
|
||||||
Added reference subsection about documenting code. Added
|
Added reference subsection about documenting code. Added
|
||||||
decisional and communicative norms.
|
decisional and communicative norms.
|
||||||
|
@ -580,6 +584,16 @@ You can also add to the end of your @file{~/.emacs} the line:
|
||||||
to automatically associate the @samp{.tcc} extension to
|
to automatically associate the @samp{.tcc} extension to
|
||||||
the @samp{c++-mode}.
|
the @samp{c++-mode}.
|
||||||
|
|
||||||
|
@item
|
||||||
|
Constructor initialization list use the following format:
|
||||||
|
@verbatim
|
||||||
|
C::C(T1 arg1, T2 arg2, ...) :
|
||||||
|
m1(arg1), m2(arg2)...
|
||||||
|
{
|
||||||
|
//...
|
||||||
|
}
|
||||||
|
@end verbatim
|
||||||
|
|
||||||
@end enumerate
|
@end enumerate
|
||||||
|
|
||||||
@c % --------------------------------------------------
|
@c % --------------------------------------------------
|
||||||
|
@ -780,6 +794,16 @@ often as possible, to ensure Unicode support.
|
||||||
If you need a smart pointer, be sure to check out
|
If you need a smart pointer, be sure to check out
|
||||||
@code{glib::RefPtr<>}.
|
@code{glib::RefPtr<>}.
|
||||||
|
|
||||||
|
@item
|
||||||
|
"C-style" comments are useful but are also problematic when you
|
||||||
|
need a fast way to exclude code from execution. Since this
|
||||||
|
kind of comments cannot nest, C-style comments cannot be
|
||||||
|
used to exclude code already commented with these old-way
|
||||||
|
comments. For this reason there is no need to complicate our
|
||||||
|
lifes with two styles of comments, the C++ comment (//) is
|
||||||
|
more than enough, and typing isn't a problem since most editors
|
||||||
|
support batch-commenting for multiple lines of code.
|
||||||
|
|
||||||
@end enumerate
|
@end enumerate
|
||||||
|
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue