cosmetics do not use msg in log class names

[simgrid.git] / README.coding

diff --git a/README.coding b/README.coding
index c2fd8fb..6b3d048 100644 (file)
--- a/README.coding
+++ b/README.coding
@@ -43,6 +43,30 @@ SimGrid4 will follow the these rules:
 This is different from the old convention (described below), that
 should not be used in S4U and its bindings, nor in the kernel.
 
 This is different from the old convention (described below), that
 should not be used in S4U and its bindings, nor in the kernel.
 

+**
+** Commenting the source: doxygen
+**
+****************************************************
+
+The global structure of the documentation is in doc/modules.doc
+
+The structure of each module (xbt, msg, etc) is in doc/module-<module>.doc
+
+The structure of a module is in its public header. This way, you're sure to
+see all the public interface (and only it). The different parts of the
+interface are grouped using the @name construct, even if it's buggy. Since
+parts often get reordered, it's better to add numbers to the parts (so that
+users can see the intended order).
+
+The documentation of each type and macro are also in the public header since
+this is were they live.
+
+The documentation of each function must be in the C++ file were it lives.
+
+Any public element (function, type and macro) must have a @brief part.
+
+We use @ as a command marker, not \ (so, use @brief not \brief)
+

 **
 ** OLD Type naming standard in SimGrid3
 **
 **
 ** OLD Type naming standard in SimGrid3
 **


@@ -68,31 +92,6 @@ Example:
 Moreover, only toto_t (and e_toto_t) are public. The rest (mainly s_toto_t)
 is private.
 
 Moreover, only toto_t (and e_toto_t) are public. The rest (mainly s_toto_t)
 is private.
 

-If you see any part of the code not following this convention, this is a
-bug. Please report it (or fix it yourself if you can).
-
-**
-** Commenting the source: doxygen
-**
-****************************************************
-
-The global structure of the documentation is in doc/modules.doc
-
-The structure of each module (xbt, msg, etc) is in doc/module-<module>.doc
-
-The structure of a module is in its public header. This way, you're sure to
-see all the public interface (and only it). The different parts of the
-interface are grouped using the @name construct, even if it's buggy. Since
-parts often get reordered, it's better to add numbers to the parts (so that
-users can see the intended order).
-
-The documentation of each type and macro are also in the public header since
-this is were they live.
-
-The documentation of each function must be in the C file were it lives.
-
-Any public element (function, type and macro) must have a @brief part.
-

 
 *
 * SimGrid Hacker Survival Guide (FIXME: should be betterly placed)
 
 *
 * SimGrid Hacker Survival Guide (FIXME: should be betterly placed)