diff options
author | Dimitri van Heesch <dimitri@stack.nl> | 2000-08-29 16:55:26 (GMT) |
---|---|---|
committer | Dimitri van Heesch <dimitri@stack.nl> | 2000-08-29 16:55:26 (GMT) |
commit | 7a048b942ae75eae857fb7f7466926b5749799c0 (patch) | |
tree | 6cbbe764d1beb5389d2e9247c672b7af04684260 /doc/faq.doc | |
parent | 5ce25000172e185e0ca5b9f20538f80cbbfe0b0e (diff) | |
download | Doxygen-7a048b942ae75eae857fb7f7466926b5749799c0.zip Doxygen-7a048b942ae75eae857fb7f7466926b5749799c0.tar.gz Doxygen-7a048b942ae75eae857fb7f7466926b5749799c0.tar.bz2 |
Release-1.2.1-20000829
Diffstat (limited to 'doc/faq.doc')
-rw-r--r-- | doc/faq.doc | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/faq.doc b/doc/faq.doc index 0817742..4606a19 100644 --- a/doc/faq.doc +++ b/doc/faq.doc @@ -39,12 +39,12 @@ You should use the \\mainpage command inside a comment block like this: In order for global functions, variables, enums, typedefs, and defines to be documented you should document the file in which these commands are -located using a comment block containing a \file (or @file) +located using a comment block containing a \\file (or \@file) command. Alternatively, you can put all members in a group (or module) -using the \ingroup command and then document the group using a comment -block containing the \defgroup command. +using the \\ingroup command and then document the group using a comment +block containing the \\defgroup command. <li><b>How can I avoid that some code fragment is parsed by Doxyen?</b> <p> |