- Updated coding style with a point on static non-POD objects.
git-svn-id: svn://svn.gna.org/svn/sgpemv2/trunk@283 3ecf2c5c-341e-0410-92b4-d18e462d057c
This commit is contained in:
parent
e008b0d4db
commit
b00d733ef0
|
@ -97,6 +97,10 @@ Free Documentation License''.
|
||||||
|
|
||||||
@table @strong
|
@table @strong
|
||||||
|
|
||||||
|
@item 2006, February 2nd, @r{--- Luca Vezzaro}
|
||||||
|
Updated coding style with a point on static non-POD
|
||||||
|
objects.
|
||||||
|
|
||||||
@item 2006, January 27th, @r{--- Matteo Settenvini, Djina Verbanac}
|
@item 2006, January 27th, @r{--- Matteo Settenvini, Djina Verbanac}
|
||||||
Add section about conventions to be followed when
|
Add section about conventions to be followed when
|
||||||
documenting anomalies.
|
documenting anomalies.
|
||||||
|
@ -1007,6 +1011,13 @@ lifes with two styles of comments, the C++ comment (//) is
|
||||||
more than enough, and typing isn't a problem since most editors
|
more than enough, and typing isn't a problem since most editors
|
||||||
support batch-commenting for multiple lines of code.
|
support batch-commenting for multiple lines of code.
|
||||||
|
|
||||||
|
@item
|
||||||
|
Never use global static variables of non-POD (Plain Old Data)
|
||||||
|
type.
|
||||||
|
The reason why not doing this is fundamental, and it is well
|
||||||
|
described, along with a possible alternative here:
|
||||||
|
@url{http://www.parashift.com/c++-faq-lite/ctors.html#faq-10.12}.
|
||||||
|
|
||||||
@end enumerate
|
@end enumerate
|
||||||
|
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue