| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
overflows
|
|\ |
|
| |\
| | |
| | | |
Bug 758132 - Brief description of non documented functions
|
| | |
| | |
| | |
| | |
| | | |
In case a function or an other item is not documented and EXTRACT_ALL has not been specified it should not appear in the list with brief description of functions etc.
(This patch supersedes the patch as proposed in pull request 411 based on the comments from Dimitri van Heesch)
|
| |\ \
| | | |
| | | | |
Fix computeCommonDirPrefix sometimes not finding the correct prefix
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The code in some cases would search backwards in a string starting from
an offset beyond the string's length. Adjust so that doesn't happen and
the code doesn't mistakenly assume there is no common dir prefix.
This bug has in some scenarios led to absolute paths being used for
dir_(md5).html links, making doxygen output needlessly depend on details
of build-time paths.
|
| |\ \
| | |/
| |/| |
Fixed preprocessor macros for flex version check
|
| |/ |
|
|/ |
|
|\ |
|
| |\
| | |
| | | |
Markdown with @cond and @endcond
|
| | |
| | |
| | |
| | |
| | | |
In case markdown files are processed and they contain @cond and @endcond these are replaced wit C-style end and begin comments (and code in between is correctly removed). The C-Style comments should not be placed as they are not understood in a markdown context (analogous to what happens in Fortram, Pythone etc.).
Note: in principle @cond should not be used as a markdown file is one "comment" block and thus @if should be used, though in any case no unwanted characters should be added.
|
| |\ \
| | | |
| | | | |
Fortran module private variables and EXTRACT_PRIVATE = NO
|
| | |/
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
From the message in the doxygen forum(http://doxygen.10944.n7.nabble.com/Fortan-problems-td7434.html and http://doxygen.10944.n7.nabble.com/Fortran-module-private-variables-and-EXTRACT-PRIVATE-NO-td7423.html)
B. If EXTRACT_PRIVATE = NO, module private functions are not listed (as expected) but module private variables are (bug!).
C. Implicit PRIVATE/PUBLIC/PROTECTED statements in a module work as expected but are not "appended" to function/variable documentation. This is only a nuisance.
Problem had a common cause, the protection was hard set to 'Public' instead of the read value (analogous to static)
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
The version checks only considered YY_FLEX_SUBMINOR_VERSION and did not
take YY_FLEX_MINOR_VERSION into account, which made them fail with
flex-2.6.0.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
In case markdown files are processed and they contain @cond and @endcond these are replaced wit C-style end and begin comments (and code in between is correctly removed). The C-Style comments should not be placed as they are not understood in a markdown context (analogous to what happens in Fortram, Pythone etc.).
Note: in principle @cond should not be used as a markdown file is one "comment" block and thus @if should be used, though in any case no unwanted characters should be added.
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
From the message in the doxygen forum(http://doxygen.10944.n7.nabble.com/Fortan-problems-td7434.html and http://doxygen.10944.n7.nabble.com/Fortran-module-private-variables-and-EXTRACT-PRIVATE-NO-td7423.html)
B. If EXTRACT_PRIVATE = NO, module private functions are not listed (as expected) but module private variables are (bug!).
C. Implicit PRIVATE/PUBLIC/PROTECTED statements in a module work as expected but are not "appended" to function/variable documentation. This is only a nuisance.
Problem had a common cause, the protection was hard set to 'Public' instead of the read value (analogous to static)
|
|\ \
| | |
| | | |
Bug 757621 - unclosed tag, c# generics method with where
|
| |/
| |
| |
| |
| | |
In the routine the <dd> tag is used to do an indentation in the <dl> section, this <dd> was not closed in endConstraintList.
Problem existed from the beginning (version Release-1.5.2-20070719, commit 29a8f14)
|
|\ \
| | |
| | | |
Title in case of USE_MDFILE_AS_MAINPAGE
|
| |/
| |
| |
| |
| | |
In case USE_MDFILE_AS_MAINPAGE is used the title in the HTML output is the project name followed by the word documentation and in the index of LATeX / rtf the value is "Main Page", this is even the case when a level 1 header is given. This is a bit contrary to the handling non main pages.
With this patch in case of USE_MDFILE_AS_MAINPAGE and a level 1 header in the beginning of the main page file this level 1 header is used title
|
| | |
|
| | |
|
| | |
|
|\ \
| |/ |
|
| |\
| | |
| | | |
[Doxygen-users] plugin / filter not behaving as expected
|
| | |
| | |
| | |
| | | |
Added note about unsupported extensions
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|/ / |
|
|\ \
| | |
| | | |
Fix Windows compatibility
|
| | | |
|
| | | |
|
| | | |
|
|/ / |
|
|\ \
| | |
| | | |
Right alignment of in page table of contents
|
|/ /
| |
| |
| | |
The in page table of contents (@tableofcontents) should be right aligned with other "box" elements like div.fragment and pre.fragment
|
|\ \ |
|
| |\ \
| | | |
| | | | |
Fix hexChar for inputs 0 <= i < 10
|
| | | | |
|
| |\ \ \
| | | | |
| | | | | |
Fix typo in function name
|
| | | |/
| | |/|
| | | |
| | | |
| | | |
| | | | |
As both declarations should only differ by cv-qualifiers.
Signed-off-by: Thomas Braun <thomas.braun@byte-physics.de>
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
As both declarations should only differ by cv-qualifiers.
Signed-off-by: Thomas Braun <thomas.braun@byte-physics.de>
|
|/ / /
| | |
| | |
| | | |
contain )
|