diff options
| author | dimitri <dimitri@afe2bf4a-e733-0410-8a33-86f594647bc7> | 2004-11-14 19:44:16 (GMT) |
|---|---|---|
| committer | dimitri <dimitri@afe2bf4a-e733-0410-8a33-86f594647bc7> | 2004-11-14 19:44:16 (GMT) |
| commit | 0625007cb86815b2e30138183d4fe9d2e7850df9 (patch) | |
| tree | 181f9ebfd0706ecca5898b169bffa8bc4f5486cc /doc/faq.doc | |
| parent | 670c8a436d6324a5ffb991f779cae0bc955959f7 (diff) | |
| download | Doxygen-0625007cb86815b2e30138183d4fe9d2e7850df9.zip Doxygen-0625007cb86815b2e30138183d4fe9d2e7850df9.tar.gz Doxygen-0625007cb86815b2e30138183d4fe9d2e7850df9.tar.bz2 | |
Release-1.3.9.1-20041114
Diffstat (limited to 'doc/faq.doc')
| -rw-r--r-- | doc/faq.doc | 13 |
1 files changed, 11 insertions, 2 deletions
diff --git a/doc/faq.doc b/doc/faq.doc index fb8bb0b..8cd217d 100644 --- a/doc/faq.doc +++ b/doc/faq.doc @@ -79,7 +79,13 @@ document either the class or namespace. <li><b>How can I make doxygen ignore some code fragment?</b> <p> -You can use Doxygen's preprocessor for this: + +The new and easiest way is to add one comment block +with a \ref cmdcond "\\cond" command at the start and one comment block +with a \ref cmdendcond "\\endcond" command at the end of the piece of +code that should be ignored. This should be within the same file of course. + +But you can also use Doxygen's preprocessor for this: If you put \verbatim #ifndef DOXYGEN_SHOULD_SKIP_THIS @@ -97,7 +103,10 @@ as <code>PREPROCESSING = YES</code>. <li><b>How can I change what is after the <code>\#include</code> in the class documentation?</b> -You can document your class like +In most cases you can use STRIP_FROM_INC_PATH to strip a user defined +part of a path. + +You can also document your class as follows \verbatim /*! \class MyClassName include.h path/include.h |