Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
D
dune-istl
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Core Modules
dune-istl
Commits
eb5f03ad
Commit
eb5f03ad
authored
17 years ago
by
Christian Engwer
Browse files
Options
Downloads
Patches
Plain Diff
bestpractice.wml is already in common
[[Imported from SVN: r844]]
parent
1f336b22
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/doxygen/bestpractice.wml
+0
-60
0 additions, 60 deletions
doc/doxygen/bestpractice.wml
with
0 additions
and
60 deletions
doc/doxygen/bestpractice.wml
deleted
100644 → 0
+
0
−
60
View file @
1f336b22
# -*- html -*-
# $Id$
#use wml::layout::default title="DUNE - Doxygen Best Practice"
#use wml::std::grid
<h1>
Doxygen Best Practice
</h1>
<h2>
Overview
</h2>
<p>
usefull tips when documenting your code
</p>
<ul>
<li><a
href=
"#copydoc"
>
\copydoc
</a></li>
<li><a
href=
"#ordermodules"
>
Ordering Modules
</a></li>
</ul>
<h2>
usefull tips when documenting your code
</h2>
<h3><a
id=
"copydoc"
>
\copydoc
<
link-object
>
</a></h3>
<p>
<em>
Use \copydoc in your derived class to reuse the documentation from the
interface class.
</em>
</p>
<p>
Copies a documentation block from the object
specified by
<
link-object
>
and pastes it at the location of the
command. This command can be useful to avoid cases where a
documentation block would otherwise have to be duplicated or it can be
used to extend the documentation of an inherited member.
</p>
<p>
The link object can point to a member (of a class, file or group), a
class, a namespace, a group, a page, or a file (checked in that
order). Note that if the object pointed to is a member (function,
variable, typedef, etc), the compound (class, file, or group)
containing it should also be documented for the copying to work.
</p>
<p>
To copy the documentation for a member of a class for instance one can
put the following in the documentation
</p>
<h3><a
id=
"ordermodules"
>
Ordering Modules
</a></h3>
<p><em>
Use the file
<tt>
doxygen/modules
</tt>
to change the ordering of modules
on the modules page
</em></p>
<p>
Doxygen sorts the modules in the order it finds their
definition. This is influenced by the order doxygen reads the
source files and by the include statements in these source files.
</p>
<p>
The
<tt>
modules
</tt>
file is read right after the mainpage, before any
source files are parsed. Entering a
<tt>
@defgroup
</tt>
statement makes
this module known to doxygen so that all modules mentioned in the
<tt>
modules
</tt>
file are listed first and in the order they are
defined there.
</p>
\ No newline at end of file
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment