Changes between Version 2 and Version 3 of Developer/Coding/Doxygen

Timestamp:

10/05/09 16:09:06 (15 years ago)

Author:

Sh

Comment:

Rearranged sections.

Developer/Coding/Doxygen

@@ -1 +1 @@
 = Doxygen Recommendations =
 
-
-RTEMS is much older than [http://www.doxygen.org Doxygen] and the documentation in the .h and .inl files was obviously not written with [http://www.stack.nl/~dimitri/doxygen/manual.html Doxygen markup].  In 2007, [wiki:TBR/User/JoelSherrill JoelSherrill] undertook converting the documentation in the .h and .inl files in the RTEMS SuperCore to Doxygen format.  As a result of this effort, the Doxygen for the CVS version of the RTEMS SuperCore is now built automatically multiple times per day and made available on the RTEMS Website.  In April 2008, [wiki:TBR/User/JoelSherrill JoelSherrill] began to update the Classic API (e.g. cpukit/rtems) .h and .inl files to include [http://www.stack.nl/~dimitri/doxygen/manual.html Doxygen markup].
 =  Files  =
 
 You can document a file with the ''@file [filename]'' directive. If you omit the filename Doxygen will use it for the documentation of the file containing this directive.  This is the preferred way to document files which can be read by Doxygen. You should not use ''@file name_of_current_file'' to document the current file because this instructs Doxygen to document a file with the filename ''name_of_current_file'' and this is not necessarily the current one and may lead to ambiguity if someone from outside reuses your stuff to generate her documentation. Within one Doxygen run all files are unique and specified by the current Doxyfile. You can define how the generated output of path and filenames looks like in the Doxyfile via the
 FULL_PATH_NAMES, STRIP_FROM_PATH and STRIP_FROM_INC_PATH options.
+=  Functions  =
+
+For documentation of function arguments there are basically to ways: The first one uses @param:
+{{{
+/**
+ * Copies bytes from a source memory area to a destination memory area,
+ * where both areas may not overlap.
+ * @param[out] dest The memory area to copy to.
+ * @param[in]  src  The memory area to copy from.
+ * @param[in]  n    The number of bytes to copy.
+ */
+}}}
+
+This leads likely to copy&paste within the comment, bloats simple function comments and is not very fluent to read.
+
+One alternative is this:
+{{{
+/**
+ * Copies @a n bytes from a source memory area @a src to a destination memory
+ * area @a dest, where both areas may not overlap.
+ */
+}}}
+
+The @a indicates that the next word is a function argument and deserves some kind of high-lightning.
+=  Doxyfile Hints  =
+
 =  Header Files  =
 
@@ -37 +61 @@
                   *.ac=script-comments-only
 }}}
-=  Assembly Example  =
+==  Assembly Example  ==
 
 {{{
@@ -54 +78 @@
 }}}
 You have to put a declaration of this function somewhere in a header file.
-=  Script Example  =
+==  Script Example  ==
 
 {{{
@@ -69 +93 @@
 AC_INIT([rtems-c-src-lib-libbsp-powerpc-mpc55xxevb],[_RTEMS_VERSION],[http://www.rtems.org/bugzilla])
 }}}
-=  Functions  =
-
-For documentation of function arguments there are basically to ways: The first one uses @param:
-{{{
-/**
- * Copies bytes from a source memory area to a destination memory area,
- * where both areas may not overlap.
- * @param[out] dest The memory area to copy to.
- * @param[in]  src  The memory area to copy from.
- * @param[in]  n    The number of bytes to copy.
- */
-}}}
-
-This leads likely to copy&paste within the comment, bloats simple function comments and is not very fluent to read.
-
-One alternative is this:
-{{{
-/**
- * Copies @a n bytes from a source memory area @a src to a destination memory
- * area @a dest, where both areas may not overlap.
- */
-}}}
-
-The @a indicates that the next word is a function argument and deserves some kind of high-lightning.
 =  GCC Attributes  =
 
@@ -103 +103 @@
 
 }}}
-=  JAVADOC_AUTOBRIEF and QT_AUTOBRIEF  =
+=  History  =
 
-We should agree on either NO or YES for both.
+RTEMS is much older than [http://www.doxygen.org Doxygen] and the documentation in the .h and .inl files was obviously not written with [http://www.stack.nl/~dimitri/doxygen/manual.html Doxygen markup].  In 2007, [wiki:TBR/User/JoelSherrill JoelSherrill] undertook converting the documentation in the .h and .inl files in the RTEMS SuperCore to Doxygen format.  As a result of this effort, the Doxygen for the CVS version of the RTEMS SuperCore is now built automatically multiple times per day and made available on the RTEMS Website.  In April 2008, [wiki:TBR/User/JoelSherrill JoelSherrill] began to update the Classic API (e.g. cpukit/rtems) .h and .inl files to include [http://www.stack.nl/~dimitri/doxygen/manual.html Doxygen markup].