Changeset 1855 in orxonox.OLD for orxonox/trunk/doc
- Timestamp:
- May 5, 2004, 9:34:21 AM (21 years ago)
- Location:
- orxonox/trunk/doc
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
orxonox/trunk/doc/CODING-STANDARDS
r1853 r1855 1 2 3 4 1.Coding Conventions 5 2.How to format your Code 6 7 1.Coding Conventions 8 -------------------- 9 ==> If you are beginning a new code-file: copy the proto_class.{cc,h} 10 ==> and work with these files. 11 12 a) in every code file, there has to be a GNU copyright header 13 b) under the (c) header write your name as main-programmer, if 14 you are just bugfixing or extending write it under co-programmer 15 c) Every function has a header with informations about it: 16 /** 17 \brief <a brief description> 18 \param <parameters the function needs> 19 \param <more parameters> 20 21 <more description> 22 */ 23 This makes live easier, if we want to add a documentation. 24 25 26 2.How to format your Code 27 ------------------------- 1 28 We use the GNU conding convention (which is also used in xemacs etc.): 2 29 -
orxonox/trunk/doc/README
r1800 r1855 14 14 in c++ and OpenGL. 15 15 If we manage to be sober enough, this game shall definitly 16 become _the_ open-source vertical scrolle ever.16 become _the_ open-source vertical scroller ever. 17 17 18 18 2.Manifesto: … … 32 32 4.Howto C++ Programming 33 33 5.Howto SVN 34 6.Coding conventions 34 35 35 36 … … 128 129 topic, it will be revised by us and merged with the trunk 129 130 130 131 7.Coding Conventions 132 -------------------- 133 Read the File CODING-STANDARDS 131 134 132 135
Note: See TracChangeset
for help on using the changeset viewer.