git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/simgrid/simgrid/trunk@900
48e7efb5-ca39-0410-a469-
dd3cf9ba447f
*
* There is several possible interfaces for this, ranging from the really completely automatic parsing to
* completely manual. Let's study each of them from the simplest to the more advanced.
*
* There is several possible interfaces for this, ranging from the really completely automatic parsing to
* completely manual. Let's study each of them from the simplest to the more advanced.
+ *
+ * \warning At least, I would like to present those sections in the right order, but doxygen prevents me
+ * from doing so. There is a weird bug I fail to circumvent here. The right order is naturally:
+ * - a) basic operations
+ * - b) Automatic parsing
+ * - c) Simple manual definitions
+ * - d) Callback Persistant State: Simple push/pop mecanism
+ * - e) Callback Persistant State: Full featured mecanism
*/
/** @name a) basic operations
*/
/** @name a) basic operations
-/** @name Callback Persistant State: Simple push/pop mecanism
+/** @name d) Callback Persistant State: Simple push/pop mecanism
* @ingroup GRAS_dd
*
* Sometimes, one of the callbacks need to leave information for the next ones. If this is a simple integer (such as
* @ingroup GRAS_dd
*
* Sometimes, one of the callbacks need to leave information for the next ones. If this is a simple integer (such as
-/** @name Callback Persistant State: Full featured mecanism
+/** @name e) Callback Persistant State: Full featured mecanism
* @ingroup GRAS_dd
*
* Sometimes, one of the callbacks need to leave information for the next ones. If the simple push/pop mecanism
* @ingroup GRAS_dd
*
* Sometimes, one of the callbacks need to leave information for the next ones. If the simple push/pop mecanism