diff options
author | russell <russell@f38db490-d61c-443f-a65b-d21fe96a405b> | 2007-06-05 14:59:34 +0000 |
---|---|---|
committer | russell <russell@f38db490-d61c-443f-a65b-d21fe96a405b> | 2007-06-05 14:59:34 +0000 |
commit | bb30ecd2907a825167b421396e3f1156186c0248 (patch) | |
tree | a05c3fd5fe7527b4f807572f346dfc228ee52335 /doc | |
parent | 0fa7915f30431fb4858c1e2e3b51ba2a8d9a45a0 (diff) |
add a note about inline comments
git-svn-id: http://svn.digium.com/svn/asterisk/trunk@67273 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'doc')
-rw-r--r-- | doc/CODING-GUIDELINES | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/CODING-GUIDELINES b/doc/CODING-GUIDELINES index ce6b80ea5..990f5bc1f 100644 --- a/doc/CODING-GUIDELINES +++ b/doc/CODING-GUIDELINES @@ -484,6 +484,14 @@ Note that /*! */ blocks document the construct immediately following them unless they are written, /*!< */, in which case they document the construct preceding them. +It is very much preferred that documentation is not done inline, as done in +the previous example for member2. The first reason for this is that it tends +to encourage extremely brief, and often pointless, documentation since people +try to keep the comment from making the line extremely long. However, if you +insist on using inline comments, please indent the documentation with spaces! +That way, all of the comments are properly aligned, regardless of what tab +size is being used for viewing the code. + * Finishing up before you submit your code ------------------------------------------ |