Key words of Doxygen

关注

转载 2008-12-10 14:43:00 1.2k 阅读 AI 写同款· GEO 优化 ›

基于MATLAB的太阳能光伏电力仿真，模拟每日太阳能发电，可视化功率曲线，并通过数值积分计算总能量输出。.zip 1.版本：matlab2014a/2019b/2024b 2.附赠案例数据可直接运行。 3.代码特点：参数化编程、参数可方便更改、代码编程思路清晰、注释明细。 4.适用对象：计算机，电子信息工程、数学等专业的大学生课程设计、期末大作业和毕业设计。立即下载

All commands in the documentation start with a backslash (/) or an at-sign (@). If you prefer you can replace all commands starting with a backslash below by their counterparts that start with an at-sign.

Some commands have one or more arguments. Each argument has a certain range:

If <sharp> braces are used the argument is a single word.
If (round) braces are used the argument extends until the end of the line on which the command was found.
If {curly} braces are used the argument extends until the next paragraph. Paragraphs are delimited by a blank line or by a section indicator.

If [square] brackets are used the argument is optional.

Here is an alphabetically sorted list of all commands with references to their documentation:

The following subsections provide a list of all commands that are recognized by doxygen. Unrecognized commands are treated as normal text.

--- Structural indicators ---

/addtogroup <name> [(title)]

Defines a group just like /defgroup, but in contrast to that command using the same <name> more than once will not result in a warning, but rather one group with a merged documentation and the first title found in any of the commands.

The title is optional, so this command can also be used to add a number of entities to an existing group using @{ and @} like this:

  /*! /addtogroup mygrp
   *  Additional documentation for group `mygrp'
   *  @{
   */

  /*!
   *  A function 
   */
  void func1()
  {
  }

  /*! Another function */
  void func2()
  {
  }

  /*! @} */

See also:

page Grouping, sections /defgroup, /ingroup and /weakgroup.

/callgraph

When this command is put in a comment block of a function or method and HAVE_DOT is set to YES, then doxygen will generate a call graph for that function (provided the implementation of the function or method calls other documented functions). The call graph will generated regardless of the value of CALL_GRAPH.

Note:

The completeness (and correctness) of the call graph depends on the doxygen code parser which is not perfect.

/category <name> [<header-file>] [<header-name>]

For Objective-C only: Indicates that a comment block contains documentation for a class category with name <name>. The arguments are equal to the /class command.

See also:

section /class.

/class <name> [<header-file>] [<header-name>]

Indicates that a comment block contains documentation for a class with name <name>. Optionally a header file and a header name can be specified. If the header-file is specified, a link to a verbatim copy of the header will be included in the HTML documentation. The <header-name> argument can be used to overwrite the name of the link that is used in the class documentation to something other than <header-file>. This can be useful if the include name is not located on the default include path (like <X11/X.h>). With the <header-name> argument you can also specify how the include statement should look like, by adding either quotes or sharp brackets around the name. Sharp brackets are used if just the name is given.

Example:

/* A dummy class */

class Test
{
};

/*! /class Test class.h "inc/class.h"
 *  /brief This is a test class.
 *
 * Some details about the Test class
 */

Click here for the corresponding HTML documentation that is generated by doxygen.

/def <name>

Indicates that a comment block contains documentation for a #define macro.

Example:

/*! /file define.h
    /brief testing defines
    
    This is to test the documentation of defines.
*/

/*!
  /def MAX(x,y)
  Computes the maximum of /a x and /a y.
*/

/*! 
   Computes the absolute value of its argument /a x.
*/
#define ABS(x) (((x)>0)?(x):-(x))
#define MAX(x,y) ((x)>(y)?(x):(y))
#define MIN(x,y) ((x)>(y)?(y):(x)) 
        /*!< Computes the minimum of /a x and /a y. */

Click here for the corresponding HTML documentation that is generated by doxygen.

/defgroup <name> (group title)

Indicates that a comment block contains documentation for a group of classes, files or namespaces. This can be used to categorize classes, files or namespaces, and document those categories. You can also use groups as members of other groups, thus building a hierarchy of groups.

The <name> argument should be a single-word identifier.

See also:

page Grouping, sections /ingroup, /addtogroup, /weakgroup.

/dir [<path fragment>]

Indicates that a comment block contains documentation for a directory. The "path fragment" argument should include the directory name and enough of the path to be unique w.r.t. the other directories in the project. The SHOW_DIRECTORIES option determines whether or not the directory information is shown and the STRIP_FROM_PATH option determines what is stripped from the full path before it appears in the output.

/enum <name>

Indicates that a comment block contains documentation for an enumeration, with name <name>. If the enum is a member of a class and the documentation block is located outside the class definition, the scope of the class should be specified as well. If a comment block is located directly in front of an enum declaration, the /enum comment may be omitted.

Note:

The type of an anonymous enum cannot be documented, but the values of an anonymous enum can.

Example:

class Test
{
  public:
    enum TEnum { Val1, Val2 };

    /*! Another enum, with inline docs */
    enum AnotherEnum 
    { 
      V1, /*!< value 1 */
      V2  /*!< value 2 */
    };
};

/*! /class Test
 * The class description.
 */

/*! /enum Test::TEnum
 * A description of the enum type.
 */

/*! /var Test::TEnum Test::Val1
 * The description of the first enum value.
 */

Click here for the corresponding HTML documentation that is generated by doxygen.

/example <file-name>

Indicates that a comment block contains documentation for a source code example. The name of the source file is <file-name>. The text of this file will be included in the documentation, just after the documentation contained in the comment block. All examples are placed in a list. The source code is scanned for documented members and classes. If any are found, the names are cross-referenced with the documentation. Source files or directories can be specified using the EXAMPLE_PATH tag of doxygen's configuration file.

If <file-name> itself is not unique for the set of example files specified by the EXAMPLE_PATH tag, you can include part of the absolute path to disambiguate it.

If more that one source file is needed for the example, the /include command can be used.

Example:

/** A Test class.
 *  More details about this class.
 */

class Test
{
  public:
    /** An example member function.
     *  More details about this function.
     */
    void example();
};

void Test::example() {}

/** /example example_test.cpp
 * This is an example of how to use the Test class.
 * More details about this example.
 */

Where the example file example_test.cpp looks as follows:

void main()
{
  Test t;
  t.example();
}

Click here for the corresponding HTML documentation that is generated by doxygen.

See also:

section /include.

/file [<name>]

Indicates that a comment block contains documentation for a source or header file with name <name>. The file name may include (part of) the path if the file-name alone is not unique. If the file name is omitted (i.e. the line after /file is left blank) then the documentation block that contains the /file command will belong to the file it is located in.

Important:

The documentation of global functions, variables, typedefs, and enums will only be included in the output if the file they are in is documented as well.

Example:

/** /file file.h
 * A brief file description.
 * A more elaborated file description.
 */

/**
 * A global integer value.
 * More details about this value.
 */
extern int globalValue;

Click here for the corresponding HTML documentation that is generated by doxygen.

Note:

In the above example JAVADOC_AUTOBRIEF has been set to YES in the configuration file.

/fn (function declaration)

Indicates that a comment block contains documentation for a function (either global or as a member of a class). This command is only needed if a comment block is not placed in front (or behind) the function declaration or definition.

If your comment block is in front of the function declaration or definition this command can (and to avoid redundancy should) be omitted.

A full function declaration including arguments should be specified after the /fn command on a single line, since the argument ends at the end of the line!

Warning:

Do not use this command if it is not absolutely needed, since it will lead to duplication of information and thus to errors.

Example:

class Test
{
  public:
    const char *member(char,int) throw(std::out_of_range);
};

const char *Test::member(char c,int n) throw(std::out_of_range) {}

/*! /class Test
 * /brief Test class.
 *
 * Details about Test.
 */

/*! /fn const char *Test::member(char c,int n) 
 *  /brief A member function.
 *  /param c a character.
 *  /param n an integer.
 *  /exception std::out_of_range parameter is out of range.
 *  /return a character pointer.
 */

Click here for the corresponding HTML documentation that is generated by doxygen.

See also:

section /var and /typedef.

/hideinitializer

By default the value of a define and the initializer of a variable are displayed unless they are longer than 30 lines. By putting this command in a comment block of a define or variable, the initializer is always hidden.

See also:

section /showinitializer.

/ingroup (<groupname> [<groupname> <groupname>])

If the /ingroup command is placed in a comment block of a class, file or namespace, then it will be added to the group or groups identified by <groupname>.

See also:

page Grouping, sections /defgroup, /addtogroup and /weakgroup

/interface <name> [<header-file>] [<header-name>]

Indicates that a comment block contains documentation for an interface with name <name>. The arguments are equal to the /class command.

See also:

section /class.

/internal

This command writes the message `For internal use only' to the output and all text after an /internal command until the end of the comment block or the end of the section (whichever comes first) is marked as "internal".

If the /internal command is put inside a section (see for example /section) all subsection after the command are considered to be internal as well. Only a new section at the same level will be visible again.

You can use INTERNAL_DOCS in the config file to show or hide the internal documentation.

/mainpage [(title)]

If the /mainpage command is placed in a comment block the block is used to customize the index page (in HTML) or the first chapter (in $/mbox{/LaTeX}$ ).

The title argument is optional and replaces the default title that doxygen normally generates. If you do not want any title you can specify notitle as the argument of /mainpage.

Here is an example:

/*! /mainpage My Personal Index Page
 *
 * /section intro_sec Introduction
 *
 * This is the introduction.
 *
 * /section install_sec Installation
 *
 * /subsection step1 Step 1: Opening the box
 *  
 * etc...
 */

You can refer to the main page using /ref index (if the treeview is disabled, otherwise you should use /ref main).

See also:

section /section, section /subsection and section /page.

/name (header)

This command turns a comment block into a header definition of a member group. The comment block should be followed by a //@{ ... //@} block containing the members of the group.

See section Member Groups for an example.

/namespace <name>

Indicates that a comment block contains documentation for a namespace with name <name>.

/nosubgrouping

This command can be put in the documentation of a class. It can be used in combination with member grouping to avoid that doxygen puts a member group as a subgroup of a Public/Protected/Private/... section.

/overload [(function declaration)]

This command can be used to generate the following standard text for an overloaded member function:

`This is an overloaded member function, provided for convenience. It differs from the above function only in what argument(s) it accepts.'

If the documentation for the overloaded member function is not located in front of the function declaration or definition, the optional argument should be used to specify the correct function.

Any other documentation that is inside the documentation block will by appended after the generated message.

Note 1:

You are responsible that there is indeed an earlier documented member that is overloaded by this one. To prevent that document reorders the documentation you should set SORT_MEMBER_DOCS to NO in this case.

Note 2:

The /overload command does not work inside a one-line comment.

Example:

class Test 
{
  public:
    void drawRect(int,int,int,int);
    void drawRect(const Rect &r);
};

void Test::drawRect(int x,int y,int w,int h) {}
void Test::drawRect(const Rect &r) {}

/*! /class Test
 *  /brief A short description.
 *   
 *  More text.
 */

/*! /fn void Test::drawRect(int x,int y,int w,int h)
 * This command draws a rectangle with a left upper corner at ( /a x , /a y ),
 * width /a w and height /a h. 
 */

/*!
 * /overload void Test::drawRect(const Rect &r)
 */

Click here for the corresponding HTML documentation that is generated by doxygen.

/package <name>

Indicates that a comment block contains documentation for a Java package with name <name>.

/page <name> (title)

Indicates that a comment block contains a piece of documentation that is not directly related to one specific class, file or member. The HTML generator creates a page containing the documentation. The $/mbox{/LaTeX}$ generator starts a new section in the chapter `Page documentation'.

Example:

/*! /page page1 A documentation page
  Leading text.
  /section sec An example section
  This page contains the subsections /ref subsection1 and /ref subsection2.
  For more info see page /ref page2.
  /subsection subsection1 The first subsection
  Text.
  /subsection subsection2 The second subsection
  More text.
*/

/*! /page page2 Another page
  Even more info.
*/

Click here for the corresponding HTML documentation that is generated by doxygen.

Note:

The <name> argument consists of a combination of letters and number digits. If you wish to use upper case letters (e.g. MYPAGE1), or mixed case letters (e.g. MyPage1) in the <name> argument, you should set CASE_SENSE_NAMES to YES. However, this is advisable only if your file system is case sensitive. Otherwise (and for better portability) you should use all lower case letters (e.g. mypage1) for <name> in all references to the page.

See also:

section /section, section /subsection, and section /ref.

/property (qualified property name)

Indicates that a comment block contains documentation for a property (either global or as a member of a class). This command is equivalent to /var and /fn.

See also:

section /fn and /var.

/protocol <name> [<header-file>] [<header-name>]

Indicates that a comment block contains documentation for a protocol in Objective-C with name <name>. The arguments are equal to the /class command.

See also:

section /class.

/relates <name>

This command can be used in the documentation of a non-member function <name>. It puts the function inside the `related function' section of the class documentation. This command is useful for documenting non-friend functions that are nevertheless strongly coupled to a certain class. It prevents the need of having to document a file, but only works for functions.

Example:

/*! 
 * A String class.
 */ 
  
class String
{
  friend int strcmp(const String &,const String &);
};

/*! 
 * Compares two strings.
 */

int strcmp(const String &s1,const String &s2)
{
}

/*! /relates String
 * A string debug function.
 */
void stringDebug()
{
}

Click here for the corresponding HTML documentation that is generated by doxygen.

/relatesalso <name>

This command can be used in the documentation of a non-member function <name>. It puts the function both inside the `related function' section of the class documentation as well as leaving its normal file documentation location. This command is useful for documenting non-friend functions that are nevertheless strongly coupled to a certain class. It only works for functions.

/showinitializer

By default the value of a define and the initializer of a variable are only displayed if they are less than 30 lines long. By putting this command in a comment block of a define or variable, the initializer is shown unconditionally.

See also:

section /hideinitializer.

/struct <name> [<header-file>] [<header-name>]

Indicates that a comment block contains documentation for a struct with name <name>. The arguments are equal to the /class command.

See also:

section /class.

/typedef (typedef declaration)

Indicates that a comment block contains documentation for a typedef (either global or as a member of a class). This command is equivalent to /var and /fn.

See also:

section /fn and /var.

/union <name> [<header-file>] [<header-name>]

Indicates that a comment block contains documentation for a union with name <name>. The arguments are equal to the /class command.

See also:

section /class.

/var (variable declaration)

Indicates that a comment block contains documentation for a variable or enum value (either global or as a member of a class). This command is equivalent to /typedef and /fn.

See also:

section /fn and /typedef.

/weakgroup <name> [(title)]

Can be used exactly like /addtogroup, but has a lower priority when it comes to resolving conflicting grouping definitions.

See also:

page Grouping and /addtogroup.

--- Section indicators ---

/attention { attention text }

Starts a paragraph where a message that needs attention may be entered. The paragraph will be indented. The text of the paragraph has no special internal structure. All visual enhancement commands may be used inside the paragraph. Multiple adjacent /attention commands will be joined into a single paragraph. The /attention command ends when a blank line or some other sectioning command is encountered.

/author { list of authors }

Starts a paragraph where one or more author names may be entered. The paragraph will be indented. The text of the paragraph has no special internal structure. All visual enhancement commands may be used inside the paragraph. Multiple adjacent /author commands will be joined into a single paragraph and separated by commas. Alternatively, one /author command may mention several authors. The /author command ends when a blank line or some other sectioning command is encountered.

Example:

/*! /class WindowsNT
 *  /brief Windows Nice Try.
 *  /author Bill Gates
 *  /author Several species of small furry animals gathered together 
 *          in a cave and grooving with a pict.
 *  /version 4.0
 *  /date    1996-1998
 *  /bug It crashes a lot and requires huge amounts of memory.
 *  /bug The class introduces the more bugs, the longer it is used.
 *  /warning This class may explode in your face.
 *  /warning If you inherit anything from this class, you're doomed.
 */

class WindowsNT {};

Click here for the corresponding HTML documentation that is generated by doxygen.

/brief {brief description}

Starts a paragraph that serves as a brief description. For classes and files the brief description will be used in lists and at the start of the documentation page. For class and file members, the brief description will be placed at the declaration of the member and prepended to the detailed description. A brief description may span several lines (although it is advised to keep it brief!). A brief description ends when a blank line or another sectioning command is encountered. If multiple /brief commands are present they will be joined. See section /author for an example.

Synonymous to /short.

/bug { bug description }

Starts a paragraph where one or more bugs may be reported. The paragraph will be indented. The text of the paragraph has no special internal structure. All visual enhancement commands may be used inside the paragraph. Multiple adjacent /bug commands will be joined into a single paragraph. Each bug description will start on a new line. Alternatively, one /bug command may mention several bugs. The /bug command ends when a blank line or some other sectioning command is encountered. See section /author for an example.

/cond [<section-label>]

Starts a conditional section that ends with a corresponding /endcond command, which is typically found in another comment block. The main purpose of this pair of commands is to (conditionally) exclude part of a file from processing (traditionally this could only be achieved using C processor commands).

The section between /cond and /endcond commands can be included by adding its section label to the ENABLED_SECTIONS configuration option. If the section label is omitted, the section will be excluded from processing unconditionally.

For conditional sections within a comment block one should use a /if ... /endif block.

Conditional sections can be nested. In this case a nested section will only be shown if it and its containing section are included.

Here is an example showing the commands in action:

/** An interface */
class Intf
{
  public:
    /** A method */
    virtual void func() = 0;

    /// @cond TEST

    /** A method used for testing */
    virtual void test() = 0;

    /// @endcond
};

/// @cond DEV
/*
 *  The implementation of the interface 
 */
class Implementation : public Intf
{
  public:
    void func();

    /// @cond TEST
    void test();
    /// @endcond

    /// @cond
    /** This method is obsolete and does
     *  not show up in the documentation.
     */
    void obsolete();
    /// @endcond
};

/// @endcond

The output will be different depending on whether ENABLED_SECTIONS is empty, TEST, DEV, or DEV TEST.

/date { date description }

Starts a paragraph where one or more dates may be entered. The paragraph will be indented. The text of the paragraph has no special internal structure. All visual enhancement commands may be used inside the paragraph. Multiple adjacent /date commands will be joined into a single paragraph. Each date description will start on a new line. Alternatively, one /date command may mention several dates. The /date command ends when a blank line or some other sectioning command is encountered. See section /author for an example.

/deprecated { description }

Starts a paragraph indicating that this documentation block belongs to a deprecated entity. Can be used to describe alternatives, expected life span, etc.

/else

Starts a conditional section if the previous conditional section was not enabled. The previous section should have been started with a /if, /ifnot, or /elseif command.

See also:

/if, /ifnot, /elseif, /endif.

/elseif <section-label>

Starts a conditional documentation section if the previous section was not enabled. A conditional section is disabled by default. To enable it you must put the section-label after the ENABLED_SECTIONS tag in the configuration file. Conditional blocks can be nested. A nested section is only enabled if all enclosing sections are enabled as well.

See also:

sections /endif, /ifnot, /else, and /elseif.

/endcond

Ends a conditional section that was started by /cond.

See also:

/cond.

/endif

Ends a conditional section that was started by /if or /ifnot For each /if or /ifnot one and only one matching /endif must follow.

See also:

/if, and /ifnot.

/exception <exception-object> { exception description }

Starts an exception description for an exception object with name <exception-object>. Followed by a description of the exception. The existence of the exception object is not checked. The text of the paragraph has no special internal structure. All visual enhancement commands may be used inside the paragraph. Multiple adjacent /exception commands will be joined into a single paragraph. Each parameter description will start on a new line. The /exception description ends when a blank line or some other sectioning command is encountered. See section /fn for an example.

Note:

the tag /exceptions is a synonym for this tag.

/if <section-label>

Starts a conditional documentation section. The section ends with a matching /endif command. A conditional section is disabled by default. To enable it you must put the section-label after the ENABLED_SECTIONS tag in the configuration file. Conditional blocks can be nested. A nested section is only enabled if all enclosing sections are enabled as well.

Example:

  /*! Unconditionally shown documentation.
   *  /if Cond1
   *    Only included if Cond1 is set.
   *  /endif
   *  /if Cond2
   *    Only included if Cond2 is set.
   *    /if Cond3
   *      Only included if Cond2 and Cond3 are set.
   *    /endif
   *    More text.
   *  /endif
   *  Unconditional text.
   */

You can also use conditional commands inside aliases. To document a class in two languages you could for instance use:

Example 2:

/*! /english
 *  This is English.
 *  /endenglish
 *  /dutch
 *  Dit is Nederlands.
 *  /enddutch
 */
class Example
{
};

Where the following aliases are defined in the configuration file:

ALIASES  = "english=/if english" /
           "endenglish=/endif" /
           "dutch=/if dutch" /
           "enddutch=/endif"

and ENABLED_SECTIONS can be used to enable either english or dutch.

See also:

sections /endif, /ifnot, /else, and /elseif.

/ifnot <section-label>

Starts a conditional documentation section. The section ends with a matching /endif command. This conditional section is enabled by default. To disable it you must put the section-label after the ENABLED_SECTIONS tag in the configuration file.

See also:

sections /endif, /if, /else, and /elseif.

/invariant { description of invariant }

Starts a paragraph where the invariant of an entity can be described. The paragraph will be indented. The text of the paragraph has no special internal structure. All visual enhancement commands may be used inside the paragraph. Multiple adjacent /invariant commands will be joined into a single paragraph. Each invariant description will start on a new line. Alternatively, one /invariant command may mention several invariants. The /invariant command ends when a blank line or some other sectioning command is encountered.

/note { text }

Starts a paragraph where a note can be entered. The paragraph will be indented. The text of the paragraph has no special internal structure. All visual enhancement commands may be used inside the paragraph. Multiple adjacent /note commands will be joined into a single paragraph. Each note description will start on a new line. Alternatively, one /note command may mention several notes. The /note command ends when a blank line or some other sectioning command is encountered. See section /par for an example.

/par [(paragraph title)] { paragraph }

If a paragraph title is given this command starts a paragraph with a user defined heading. The heading extends until the end of the line. The paragraph following the command will be indented.

If no paragraph title is given this command will start a new paragraph. This will also work inside other paragraph commands (like /param or /warning) without ending the that command.

The text of the paragraph has no special internal structure. All visual enhancement commands may be used inside the paragraph. The /par command ends when a blank line or some other sectioning command is encountered.

Example:

/*! /class Test
 * Normal text.
 *
 * /par User defined paragraph:
 * Contents of the paragraph.
 *
 * /par
 * New paragraph under the same heading.
 *
 * /note
 * This note consists of two paragraphs.
 * This is the first paragraph.
 *
 * /par
 * And this is the second paragraph.
 *
 * More normal text. 
 */
  
class Test {};

Click here for the corresponding HTML documentation that is generated by doxygen.

/param <parameter-name> { parameter description }

Starts a parameter description for a function parameter with name <parameter-name>. Followed by a description of the parameter. The existence of the parameter is checked and a warning is given if the documentation of this (or any other) parameter is missing or not present in the function declaration or definition.

The /param command has an optional attribute specifying the direction of the attribute. Possible values are "in" and "out". Here is an example for the function memcpy:

/*!
 Copies bytes from a source memory area to a destination memory area,
 where both areas may not overlap.
 @param[out] dest The memory area to copy to.
 @param[in]  src  The memory area to copy from.
 @param[in]  n    The number of bytes to copy
 */
void memcpy(void *dest, const void *src, size_t n);

If a parameter is both input and output, use [in,out] as an attribute.

The parameter description is a paragraph with no special internal structure. All visual enhancement commands may be used inside the paragraph.

Multiple adjacent /param commands will be joined into a single paragraph. Each parameter description will start on a new line. The /param description ends when a blank line or some other sectioning command is encountered. See section /fn for an example.

/post { description of the postcondition }

Starts a paragraph where the postcondition of an entity can be described. The paragraph will be indented. The text of the paragraph has no special internal structure. All visual enhancement commands may be used inside the paragraph. Multiple adjacent /post commands will be joined into a single paragraph. Each postcondition will start on a new line. Alternatively, one /post command may mention several postconditions. The /post command ends when a blank line or some other sectioning command is encountered.

/pre { description of the precondition }

Starts a paragraph where the precondition of an entity can be described. The paragraph will be indented. The text of the paragraph has no special internal structure. All visual enhancement commands may be used inside the paragraph. Multiple adjacent /pre commands will be joined into a single paragraph. Each precondition will start on a new line. Alternatively, one /pre command may mention several preconditions. The /pre command ends when a blank line or some other sectioning command is encountered.

/remarks { remark text }

Starts a paragraph where one or more remarks may be entered. The paragraph will be indented. The text of the paragraph has no special internal structure. All visual enhancement commands may be used inside the paragraph. Multiple adjacent /remark commands will be joined into a single paragraph. Each remark will start on a new line. Alternatively, one /remark command may mention several remarks. The /remark command ends when a blank line or some other sectioning command is encountered.

/return { description of the return value }

Starts a return value description for a function. The text of the paragraph has no special internal structure. All visual enhancement commands may be used inside the paragraph. Multiple adjacent /return commands will be joined into a single paragraph. The /return description ends when a blank line or some other sectioning command is encountered. See section /fn for an example.

/retval <return value> { description }

Starts a return value description for a function with name <return value>. Followed by a description of the return value. The text of the paragraph that forms the description has no special internal structure. All visual enhancement commands may be used inside the paragraph. Multiple adjacent /retval commands will be joined into a single paragraph. Each return value description will start on a new line. The /retval description ends when a blank line or some other sectioning command is encountered.

/sa { references }

Starts a paragraph where one or more cross-references to classes, functions, methods, variables, files or URL may be specified. Two names joined by either :: or # are understood as referring to a class and one of its members. One of several overloaded methods or constructors may be selected by including a parenthesized list of argument types after the method name.

Synonymous to /see.

See also:

section autolink for information on how to create links to objects.

/see { references }

Equivalent to /sa. Introduced for compatibility with Javadoc.

/since { text }

This tag can be used to specify since when (version or time) an entity is available. The paragraph that follows /since does not have any special internal structure. All visual enhancement commands may be used inside the paragraph. The /since description ends when a blank line or some other sectioning command is encountered.

/test { paragraph describing a test case }

Starts a paragraph where a test case can be described. The description will also add the test case to a separate test list. The two instances of the description will be cross-referenced. Each test case in the test list will be preceded by a header that indicates the origin of the test case.

/throw <exception-object> { exception description }

Synonymous to /exception (see section /exception).

Note:

the tag /throws is a synonym for this tag.

/todo { paragraph describing what is to be done }

Starts a paragraph where a TODO item is described. The description will also add an item to a separate TODO list. The two instances of the description will be cross-referenced. Each item in the TODO list will be preceded by a header that indicates the origin of the item.

/version { version number }

Starts a paragraph where one or more version strings may be entered. The paragraph will be indented. The text of the paragraph has no special internal structure. All visual enhancement commands may be used inside the paragraph. Multiple adjacent /version commands will be joined into a single paragraph. Each version description will start on a new line. Alternatively, one /version command may mention several version strings. The /version command ends when a blank line or some other sectioning command is encountered. See section /author for an example.

/warning { warning message }

Starts a paragraph where one or more warning messages may be entered. The paragraph will be indented. The text of the paragraph has no special internal structure. All visual enhancement commands may be used inside the paragraph. Multiple adjacent /warning commands will be joined into a single paragraph. Each warning description will start on a new line. Alternatively, one /warning command may mention several warnings. The /warning command ends when a blank line or some other sectioning command is encountered. See section /author for an example.

/xrefitem <key> "(heading)" "(list title)" {text}

This command is a generalization of commands such as /todo and /bug. It can be used to create user-defined text sections which are automatically cross-referenced between the place of occurrence and a related page, which will be generated. On the related page all sections of the same type will be collected.

The first argument <key> is a identifier uniquely representing the type of the section. The second argument is a quoted string representing the heading of the section under which text passed as the forth argument is put. The third argument (list title) is used as the title for the related page containing all items with the same key. The keys "todo", "test", "bug", and "deprecated" are predefined.

To get an idea on how to use the /xrefitem command and what its effect is, consider the todo list, which (for English output) can be seen an alias for the command

 /xrefitem todo "Todo" "Todo List"

Since it is very tedious and error-prone to repeat the first three parameters of the command for each section, the command is meant to be used in combination with the ALIASES option in the configuration file. To define a new command /reminder, for instance, one should add the following line to the configuration file:

 ALIASES += "reminder=/xrefitem reminders /"Reminder/" /"Reminders/""

Note the use of escaped quotes for the second and third argument of the /xrefitem command.

--- Commands to create links ---

/addindex (text)

This command adds (text) to the index.

/anchor <word>

This command places an invisible, named anchor into the documentation to which you can refer with the /ref command.

Note:

Anchors can currently only be put into a comment block that is marked as a page (using /page) or mainpage ( /mainpage).

See also:

section /ref.

/endlink

This command ends a link that is started with the /link command.

See also:

section /link.

/link <link-object>

The links that are automatically generated by doxygen always have the name of the object they point to as link-text.

The /link command can be used to create a link to an object (a file, class, or member) with a user specified link-text. The link command should end with an /endlink command. All text between the /link and /endlink commands serves as text for a link to the <link-object> specified as the first argument of /link.

See section autolink for more information on automatically generated links and valid link-objects.

/ref <name> ["(text)"]

Creates a reference to a named section, subsection, page or anchor. For HTML documentation the reference command will generate a link to the section. For a sections or subsections the title of the section will be used as the text of the link. For anchor the optional text between quotes will be used or <name> if no text is specified. For $/mbox{/LaTeX}$ documentation the reference command will generate a section number for sections or the text followed by a page number if <name> refers to an anchor.

See also:

Section /page for an example of the /ref command.

/section <section-name> (section title)

Creates a section with name <section-name>. The title of the section should be specified as the second argument of the /section command.

Warning:

This command only works inside related page documentation and not in other documentation blocks!

/subsection <subsection-name> (subsection title)

Creates a subsection with name <subsection-name>. The title of the subsection should be specified as the second argument of the /subsection command.

Warning:

This command only works inside a section of a related page documentation block and not in other documentation blocks!

See also:

Section /page for an example of the /subsection command.

/subsubsection <subsubsection-name> (subsubsection title)

Creates a subsubsection with name <subsubsection-name>. The title of the subsubsection should be specified as the second argument of the /subsubsection command.

Warning:

This command only works inside a subsection of a related page documentation block and not in other documentation blocks!

See also:

Section /page for an example of the /subsubsection command.

/paragraph <paragraph-name> (paragraph title)

Creates a named paragraph with name <paragraph-name>. The title of the paragraph should be specified as the second argument of the /paragraph command.

Warning:

This command only works inside a subsubsection of a related page documentation block and not in other documentation blocks!

See also:

Section /page for an example of the /paragraph command.

--- Commands for displaying examples ---

/dontinclude <file-name>

This command can be used to parse a source file without actually verbatim including it in the documentation (as the /include command does). This is useful if you want to divide the source file into smaller pieces and add documentation between the pieces. Source files or directories can be specified using the EXAMPLE_PATH tag of doxygen's configuration file.

The class and member declarations and definitions inside the code fragment are `remembered' during the parsing of the comment block that contained the /dontinclude command.

For line by line descriptions of source files, one or more lines of the example can be displayed using the /line, /skip, /skipline, and /until commands. An internal pointer is used for these commands. The /dontinclude command sets the pointer to the first line of the example.

Example:

/*! A test class. */

class Test
{
  public:
    /// a member function
    void example();
};

/*! /page example
 *  /dontinclude example_test.cpp
 *  Our main function starts like this:
 *  /skip main
 *  /until {
 *  First we create a object /c t of the Test class.
 *  /skipline Test
 *  Then we call the example member function 
 *  /line example
 *  After that our little test routine ends.
 *  /line }
 */

Where the example file example_test.cpp looks as follows:

void main()
{
  Test t;
  t.example();
}

Click here for the corresponding HTML documentation that is generated by doxygen.

See also:

sections /line, /skip, /skipline, and /until.

/include <file-name>

This command can be used to include a source file as a block of code. The command takes the name of an include file as an argument. Source files or directories can be specified using the EXAMPLE_PATH tag of doxygen's configuration file.

If <file-name> itself is not unique for the set of example files specified by the EXAMPLE_PATH tag, you can include part of the absolute path to disambiguate it.

Using the /include command is equivalent to inserting the file into the documentation block and surrounding it with /code and /endcode commands.

The main purpose of the /include command is to avoid code duplication in case of example blocks that consist of multiple source and header files.

For a line by line description of a source files use the /dontinclude command in combination with the /line, /skip, /skipline, and /until commands.

See also:

section /example and /dontinclude.

/includelineno <file-name>

This command works the same way as /include, but will add line numbers to the included file.

See also:

section /include.

/line ( pattern )

This command searches line by line through the example that was last included using /include or /dontinclude until it finds a non-blank line. If that line contains the specified pattern, it is written to the output.

The internal pointer that is used to keep track of the current line in the example, is set to the start of the line following the non-blank line that was found (or to the end of the example if no such line could be found).

See section /dontinclude for an example.

/skip ( pattern )

This command searches line by line through the example that was last included using /include or /dontinclude until it finds a line that contains the specified pattern.

The internal pointer that is used to keep track of the current line in the example, is set to the start of the line that contains the specified pattern (or to the end of the example if the pattern could not be found).

See section /dontinclude for an example.

/skipline ( pattern )

This command searches line by line through the example that was last included using /include or /dontinclude until it finds a line that contains the specified pattern. It then writes the line to the output.

The internal pointer that is used to keep track of the current line in the example, is set to the start of the line following the line that is written (or to the end of the example if the pattern could not be found).

Note:

The command:

/skipline pattern

is equivalent to:

/skip pattern
/line pattern

See section /dontinclude for an example.

/until ( pattern )

This command writes all lines of the example that was last included using /include or /dontinclude to the output, until it finds a line containing the specified pattern. The line containing the pattern will be written as well.

The internal pointer that is used to keep track of the current line in the example, is set to the start of the line following last written line (or to the end of the example if the pattern could not be found).

See section /dontinclude for an example.

/verbinclude <file-name>

This command includes the file <file-name> verbatim in the documentation. The command is equivalent to pasting the file in the documentation and placing /verbatim and /endverbatim commands around it.

Files or directories that doxygen should look for can be specified using the EXAMPLE_PATH tag of doxygen's configuration file.

/htmlinclude <file-name>

This command includes the file <file-name> as is in the HTML documentation. The command is equivalent to pasting the file in the documentation and placing /htmlonly and /endhtmlonly commands around it.

Files or directories that doxygen should look for can be specified using the EXAMPLE_PATH tag of doxygen's configuration file.

--- Commands for visual enhancements ---

/a <word>

Displays the argument <word> using a special font. Use this command to refer to member arguments in the running text.

Example:

  ... the /a x and /a y coordinates are used to ...

This will result in the following text:

... the x and y coordinates are used to ...

/arg { item-description }

This command has one argument that continues until the first blank line or until another /arg is encountered. The command can be used to generate a simple, not nested list of arguments. Each argument should start with a /arg command.

Example:

Typing:

  /arg /c AlignLeft left alignment.
  /arg /c AlignCenter center alignment.
  /arg /c AlignRight right alignment
  
  No other types of alignment are supported.

will result in the following text:

AlignLeft left alignment.
AlignCenter center alignment.
AlignRight right alignment

No other types of alignment are supported.

Note:

For nested lists, HTML commands should be used.

Equivalent to /li

/b <word>

Displays the argument <word> using a bold font. Equivalent to <b>word</b>. To put multiple words in bold use <b>multiple words</b>.

/c <word>

Displays the argument <word> using a typewriter font. Use this to refer to a word of code. Equivalent to <tt>word</tt>.

Example:

Typing:

     ... This function returns /c void and not /c int ...

will result in the following text:

... This function returns void and not int ...

Equivalent to /p To have multiple words in typewriter font use <tt>multiple words</tt>.

/code

Starts a block of code. A code block is treated differently from ordinary text. It is interpreted as C/C++ code. The names of the classes and members that are documented are automatically replaced by links to the documentation.

See also:

section /endcode, section /verbatim

/copydoc <link-object>

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.

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.

To copy the documentation for a member of a class for instance one can put the following in the documentation

  /*! @copydoc MyClass::myfunction() 
   *  More documentation.
   */

if the member is overloaded, you should specify the argument types explicitly (without spaces!), like in the following:

  /*! @copydoc MyClass::myfunction(type1,type2) */

Qualified names are only needed if the context in which the documentation block is found requires them.

The copydoc command can be used recursively, but cycles in the copydoc relation will be broken and flagged as an error.

/dot

Starts a text fragment which should contain a valid description of a dot graph. The text fragment ends with /enddot. Doxygen will pass the text on to dot and include the resulting image (and image map) into the output. The nodes of a graph can be made clickable by using the URL attribute. By using the command /ref inside the URL value you can conveniently link to an item inside doxygen. Here is an example:

/*! class B */
class B {};

/*! class C */
class C {};

/*! /mainpage

  Class relations expressed via an inline dot graph:
  /dot
  digraph example {
      node [shape=record, fontname=Helvetica, fontsize=10];
      b [ label="class B" URL="/ref B"];
      c [ label="class C" URL="/ref C"];
      b -> c [ arrowhead="open", style="dashed" ];
  }
  /enddot
  Note that the classes in the above graph are clickable 
  (in the HTML output).
 */

/dotfile <file> ["caption"]

Inserts an image generated by dot from <file> into the documentation.

The first argument specifies the file name of the image. doxygen will look for files in the paths (or files) that you specified after the DOTFILE_DIRS tag. If the dot file is found it will be used as an input file to the dot tool. The resulting image will be put into the correct output directory. If the dot file name contains spaces you'll have to put quotes (") around it.

The second argument is optional and can be used to specify the caption that is displayed below the image. This argument has to be specified between quotes even if it does not contain any spaces. The quotes are stripped before the caption is displayed.

/e <word>

Displays the argument <word> in italics. Use this command to emphasize words.

Example:

Typing:

  ... this is a /e really good example ...

will result in the following text:

... this is a really good example ...

Equivalent to /em. To emphasis multiple words use <em>multiple words</em>.

/em <word>

Displays the argument <word> in italics. Use this command to emphasize words.

Example:

Typing:

  ... this is a /em really good example ...

will result in the following text:

... this is a really good example ...

Equivalent to /e

/endcode

Ends a block of code.

See also:

section /code

/enddot

Ends a blocks that was started with /dot.

/endhtmlonly

Ends a block of text that was started with a /htmlonly command.

See also:

section /htmlonly.

/endlatexonly

Ends a block of text that was started with a /latexonly command.

See also:

section /latexonly.

/endmanonly

Ends a block of text that was started with a /manonly command.

See also:

section /manonly.

/endverbatim

Ends a block of text that was started with a /verbatim command.

See also:

section /verbatim.

/endxmlonly

Ends a block of text that was started with a /xmlonly command.

See also:

section /xmlonly.

/f$

Marks the start and end of an in-text formula.

See also:

section formulas for an example.

/f[

Marks the start of a long formula that is displayed centered on a separate line.

See also:

section /f] and section formulas.

/f]

Marks the end of a long formula that is displayed centered on a separate line.

See also:

section /f[ and section formulas.

/htmlonly

Starts a block of text that will be verbatim included in the generated HTML documentation only. The block ends with a endhtmlonly command.

This command can be used to include HTML code that is too complex for doxygen (i.e. applets, java-scripts, and HTML tags that require attributes). You can use the /latexonly and /endlatexonly pair to provide a proper $/mbox{/LaTeX}$ alternative.

Note: environment variables (like $(HOME) ) are resolved inside a HTML-only block.

See also:

section /manonly and section /latexonly.

/image <format> <file> ["caption"] [<sizeindication>=<size>]

Inserts an image into the documentation. This command is format specific, so if you want to insert an image for more than one format you'll have to repeat this command for each format.

The first argument specifies the output format. Currently, the following values are supported: html and latex.

The second argument specifies the file name of the image. doxygen will look for files in the paths (or files) that you specified after the IMAGE_PATH tag. If the image is found it will be copied to the correct output directory. If the image name contains spaces you'll have to put quotes (") around it. You can also specify an absolute URL instead of a file name, but then doxygen does not copy the image nor check its existance.

The third argument is optional and can be used to specify the caption that is displayed below the image. This argument has to be specified on a single line and between quotes even if it does not contain any spaces. The quotes are stripped before the caption is displayed.

The fourth argument is also optional and can be used to specify the width or height of the image. This is only useful for $/mbox{/LaTeX}$ output (i.e. format=latex). The sizeindication can be either width or height. The size should be a valid size specifier in (for example 10cm or 6in or a symbolic width like /textwidth).

Here is example of a comment block:

  /*! Here is a snapshot of my new application:
   *  /image html application.jpg
   *  /image latex application.eps "My application" width=10cm
   */

And this is an example of how the relevant part of the configuration file may look:

  IMAGE_PATH     = my_image_dir

Warning:

The image format for HTML is limited to what your browser supports. For $/mbox{/LaTeX}$

, the image format must be Encapsulated PostScript (eps).

Doxygen does not check if the image is in the correct format. So you have to make sure this is the case!

/latexonly

Starts a block of text that will be verbatim included in the generated $/mbox{/LaTeX}$ documentation only. The block ends with a endlatexonly command.

This command can be used to include $/mbox{/LaTeX}$ code that is too complex for doxygen (i.e. images, formulas, special characters). You can use the /htmlonly and /endhtmlonly pair to provide a proper HTML alternative.

Note: environment variables (like $(HOME) ) are resolved inside a $/mbox{/LaTeX}$ -only block.

See also:

section /latexonly and section /htmlonly.

/manonly

Starts a block of text that will be verbatim included in the generated MAN documentation only. The block ends with a endmanonly command.

This command can be used to include groff code directly into MAN pages. You can use the /htmlonly and /latexonly and /endhtmlonly and /endlatexonly pairs to provide proper HTML and $/mbox{/LaTeX}$ alternatives.

See also:

section /htmlonly and section /latexonly.

/li { item-description }

This command has one argument that continues until the first blank line or until another /li is encountered. The command can be used to generate a simple, not nested list of arguments. Each argument should start with a /li command.

Example:

Typing:

  /li /c AlignLeft left alignment.
  /li /c AlignCenter center alignment.
  /li /c AlignRight right alignment
  
  No other types of alignment are supported.

will result in the following text:

AlignLeft left alignment.
AlignCenter center alignment.
AlignRight right alignment

No other types of alignment are supported.

Note:

For nested lists, HTML commands should be used.

Equivalent to /arg

/n

Forces a new line. Equivalent to <br> and inspired by the printf function.

/p <word>

Displays the parameter <word> using a typewriter font. You can use this command to refer to member function parameters in the running text.

Example:

  ... the /p x and /p y coordinates are used to ...

This will result in the following text:

... the x and y coordinates are used to ...

Equivalent to /c

/verbatim

Starts a block of text that will be verbatim included in both the HTML and the $/mbox{/LaTeX}$ documentation. The block should end with a /endverbatim block. All commands are disabled in a verbatim block.

Warning:

Make sure you include a /endverbatim command for each /verbatim command or the parser will get confused!

/xmlonly

Starts a block of text that will be verbatim included in the generated XML output only. The block ends with a endxmlonly command.

This command can be used to include custom XML tags.

See also:

section /htmlonly and section /latexonly.

//

This command writes a backslash character (/) to the HTML and $/mbox{/LaTeX}$ output. The backslash has to be escaped in some cases because doxygen uses it to detect commands.

/@

This command writes an at-sign (@) to the HTML and $/mbox{/LaTeX}$ output. The at-sign has to be escaped in some cases because doxygen uses it to detect JavaDoc commands.

/~[LanguageId]

This command enables/disables a language specific filter. This can be used to put documentation for different language into one comment block and use the OUTPUT_LANGUAGE tag to filter out only a specific language. Use /~language_id to enable output for a specific language only and /~ to enable output for all languages (this is also the default mode).

Example:

/*! /~english This is english /~dutch Dit is Nederlands /~german Dieses ist
    deutsch. /~ output for all languages.
 */

/&

This command writes the & character to output. This character has to be escaped because it has a special meaning in HTML.

/$

This command writes the $ character to the output. This character has to be escaped in some cases, because it is used to expand environment variables.

/#

This command writes the # character to the output. This character has to be escaped in some cases, because it is used to refer to documented entities.

/<

This command writes the < character to the output. This character has to be escaped because it has a special meaning in HTML.

/>

This command writes the > character to the output. This character has to be escaped because it has a special meaning in HTML.

/%

This command writes the % character to the output. This character has to be escaped in some cases, because it is used to prevent auto-linking to word that is also a documented class or struct.

PHP only commands

For PHP files there are a number of additional commands, that can be used inside classes to make members public, private, or protected even though the language itself doesn't support this notion.

To mark a single item use one of /private, /protected, /public. For starting a section with a certain protection level use one of: /privatesection, /protectedsection, /publicsection. The latter commands are similar to "private:", "protected:", and "public:" in C++.