summaryrefslogtreecommitdiffstats
path: root/doc/faq.doc
diff options
context:
space:
mode:
authordimitri <dimitri@afe2bf4a-e733-0410-8a33-86f594647bc7>2000-08-29 16:55:26 (GMT)
committerdimitri <dimitri@afe2bf4a-e733-0410-8a33-86f594647bc7>2000-08-29 16:55:26 (GMT)
commit26ded37d33ae68d85d5ae4b2e5555ff6ed944a44 (patch)
tree6cbbe764d1beb5389d2e9247c672b7af04684260 /doc/faq.doc
parent8726fc640f878611e395b1d821661cff56a49e13 (diff)
downloadDoxygen-26ded37d33ae68d85d5ae4b2e5555ff6ed944a44.zip
Doxygen-26ded37d33ae68d85d5ae4b2e5555ff6ed944a44.tar.gz
Doxygen-26ded37d33ae68d85d5ae4b2e5555ff6ed944a44.tar.bz2
Release-1.2.1-20000829
Diffstat (limited to 'doc/faq.doc')
-rw-r--r--doc/faq.doc6
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>