Doxygen

Visit the starting documentation to learn the first steps in using Doxygen with source files.

Background
From the Doxygen starting documentation Step 3.

For members, classes and namespaces there are basically two options:
 * 1) Place a special documentation block in front of the declaration or definition of the member, class or namespace. For file, class and namespace members it is also allowed to place the documentation directly after the member.
 * See section Special comment blocks to learn more about special documentation blocks.
 * 1) Place a special documentation block somewhere else (another file or another location) and put a structural command in the documentation block. A structural command links a documentation block to a certain entity that can be documented (e.g. a member, class, namespace or file).
 * See section Documentation at other places to learn more about structural commands.

Note:
 * The advantage of the first option is that you do not have to repeat the name of the entity.
 * Files can only be documented using the second option, since there is no way to put a documentation block before a file. Of course, file members (functions, variables, typedefs, defines) do not need an explicit structural command; just putting a special documentation block in front or behind them will work fine.

Explanation of doxygen markup

 * \addtogroup
 * \brief
 * \param
 * \return  (syn. \returns)
 * \note

FC doxygen formatting
The FC project has chosen the following method for it's doxygen comment blocks: As it's special char of choice


 * \note ex.

Note: Please also read: https://github.com/FreeCAD/FreeCAD/blob/master/src/Doc/doctips.dox