Changes between Version 10 and Version 11 of doc/tec/developerrules/palmstandard
- Timestamp:
- Nov 6, 2018 6:09:46 PM (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
doc/tec/developerrules/palmstandard
v10 v11 105 105 106 106 == Commenting & documentation == 107 Documentation consists of putting information both inside and outside the source code. 108 Comments should give a good idea of what the code does and where to look for any special activity. 107 Documentation consists of putting information both internally and externally of the source code. Comments should give a good idea of what the code does and where to look for any special activity. PALM supports the use of Doxygen, a tool for generating documentation and flow charts from annotated source code. This requires some special formatting, as described below. 109 108 110 '''Doxygen format''' 109 '''File header section''' 110 * todos, notes, author,.... 111 111 * Declaration !< Description 112 112 * see file header 113 113 * @author etc. 114 114 * MODULE/SUBROUTINE description !> 115 116 '''Header section'''117 * todos, notes, author,....118 115 119 116 '''Inside the code''' … … 125 122 126 123 '''Outside the code''' 124 You are in the middle of it. We have an extensive online documentation wiki embedded into a [link-to trac] project management system, directly connected to the svn repository, allowing to [browse the PALM code] @ all its former and of course current revision in a web-based environment. 125 Your carefully developed code can only be used, if there is a documentation that tells the PALM user how to use and steer the feature. 127 126 128 127 = (X) Coding =