| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | | | | | | | | | |
|
| | | | | | | | | | | |
|
| | |_|_|/ / / / / /
| |/| | | | | | | | |
|
|\ \ \ \ \ \ \ \ \ \
| | | | | | | | | | |
| | | | | | | | | | | |
Handling Fortran functions in call graphs
|
| |/ / / / / / / / /
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
When functions are used they have to be declared and were seen as local variables even when the 'external' keyword had been applied.
Functions are now not seen anymore as local variables as soon as the 'external' keyword has been applied.
|
|\ \ \ \ \ \ \ \ \ \
| | | | | | | | | | |
| | | | | | | | | | | |
Enable comma as separator in configuration lists
|
| |/ / / / / / / / /
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
Loosely based on problems when users use a comma as separator in a list (as this is slightly suggested in the documentation).
(https://stackoverflow.com/questions/43093051/doxygen-is-generating-empty-documentation)
|
|\ \ \ \ \ \ \ \ \ \
| | | | | | | | | | |
| | | | | | | | | | | |
Wrong separator in index for a.o. Python, C#
|
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
In e.g. the LaTeX output the separator for Pyton, C# is given as '::', this should be '.' .
With this fix the problems in the index are gone.
|
|/ / / / / / / / / /
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
methods in Python are always "virtual" (but there is no way to signal it).
|
|\ \ \ \ \ \ \ \ \ \
| | | | | | | | | | |
| | | | | | | | | | | |
Bug 749049 - Doxygen not creating call graphs for C# methods if namespace contains the classname
|
| |/ / / / / / / / /
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
contains the classname
Problem is the '.' in the namespace name.
For Csharp:
namespace N1.n2
{
is equivalent to
namespace N1
{
namespace N2
{
This splitting has to be considered in the scanner so the different namespaces are mentioned. In the code.l the '.' was not handled.
|
|\ \ \ \ \ \ \ \ \ \
| |/ / / / / / / / /
|/| | | | | | | | | |
Add python function annotations support
|
| | | | | | | | | | |
|
| | | | | | | | | | |
|
| | |_|/ / / / / /
| |/| | | | | | | |
|
|\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | | |
Bug 719541 - Error with inserting images to PDF with Markdown
|
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
Create possibility to use images in other output formats conform the `\image` command.
|
|\ \ \ \ \ \ \ \ \ \
| | | | | | | | | | |
| | | | | | | | | | | |
Bug 710654 - <img> on a \page does not copy the image to the html output folder
|
| |/ / / / / / / / /
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
Create possibility to copy the image automatically to the HTML directory, in case file cannot be found no warning is given (consistency).
|
|\ \ \ \ \ \ \ \ \ \
| | | | | | | | | | |
| | | | | | | | | | | |
issue_6524: Markdown formats missing in doxygen outputs.
|
| | |/ / / / / / / /
| |/| | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
Support for strikethrough by means of `~~<text>~~`
See also https://help.github.com/articles/basic-writing-and-formatting-syntax/ paragraph about "styling" text".
|
|\ \ \ \ \ \ \ \ \ \
| | | | | | | | | | |
| | | | | | | | | | | |
Bold text terminated by plus sign
|
| |/ / / / / / / / /
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
No reason to have '+,'-' or '=' with ignore characters.
See also: https://stackoverflow.com/questions/52696929/markdown-bold-text
|
|\ \ \ \ \ \ \ \ \ \
| |_|/ / / / / / / /
|/| | | | | | | | | |
issue_6547 Call graph missing due to ALIASES
|
| |/ / / / / / / /
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Replace the `^^` in an alias not with an physical newline but with a doxygen synthetic newline.
Shown problem is due to the fact that line matching didn't work anymore due to the fact that a physical newline was inserted (ever better seen when enabling `INLINE_SOURCES`)
|
|/ / / / / / / /
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
In fixed formatted Fortran code the numbers in the first positions of the comment were filtered out.
This is a regression on pull request #655
example where the number '1' disappears:
!> \details
!> 1.) First point
subroutine tst
end subroutine
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
FILTER_SOURCE_FILES and INLINE_SOURCES are both enabled #6395
|
|\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Don't link to non existing / not accessible namespaces , in CSharp, in the source code
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
source code
In the following the 'test' and 'System' were linked in the source code, this should not be the case.
using test;
using System;
using System.IO;
namespace NON
{
}
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
The default (string) list can contain an empty elements (e.g. INPUT, STRIP_FROM_PATH) giving false positives. Removed empty elements from the checks.
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
- corrected some initializations
- corrected some missing, new, cases (reported by travis CI)
|
|\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | | |
Implementation of standard generator for docbook output
|
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
Removed debug statement
|
| |/ / / / / / / /
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Till now docbook had its own output generator, but lot of possibilities were missing (see remark about updating below), with this patch the (more than) basic implementation has been made.
Added some docbook tests to the current tests and updated documentation where necessary
Tried updating current version but too many issues remained that were generically handled in the standard generator, code is in current version behind '#if 0' construct in doxygen.cpp and name with '_v1' and in docbookgen.cp'
|
|\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | | |
Difference between standard and used Doxyfile
|
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
Writes a the differences between the current configuration and the template configuration.
Useful when communicating e.g. in forums.
|
|\ \ \ \ \ \ \ \ \ \
| | | | | | | | | | |
| | | | | | | | | | | |
Namespace with name docstrings_linebreak
|
| |/ / / / / / / / /
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
As a regression on pull request #674 in respect to the moving of the markdown handling place the `\_linebreak` command is not translated anymore.
In fact the `\_linebreak` is not necessary at all only the space is required as the `\namespace` command takes just one word as argument.
|
|\ \ \ \ \ \ \ \ \ \
| | | | | | | | | | |
| | | | | | | | | | | |
Fixing coverity messages
|
| |/ / / / / / / / /
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
Note: especially latexdocvisitor (dead code that should not be dead code).
|
|\ \ \ \ \ \ \ \ \ \
| | | | | | | | | | |
| | | | | | | | | | | |
Close last code line properly.
|
| |/ / / / / / / / /
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
When ending code fragment, check if last code line is closed, if this is not the case close it.
(problem observed with inline code in Python, but might happen on other places as well)
|
|\ \ \ \ \ \ \ \ \ \
| | | | | | | | | | |
| | | | | | | | | | | |
Fixing coverity messages (Namespace tag)
|
| |/ / / / / / / / /
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
Correcting missing break in namespace when writing a tag file.
(Could not find a case; incase the FALL THROUGH case is correct this has to be clearly indicated in the code).
|
|\ \ \ \ \ \ \ \ \ \
| | | | | | | | | | |
| | | | | | | | | | | |
Fixing problem with possible not initialized variable (endless loop in VS 2017 debug)
|
| |/ / / / / / / / /
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
2017 debug)
The not initialized variable `l` caused and endless loop in the VS2017 debug version, variable should not have been used.
|
|/ / / / / / / / /
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Based on the stack overflow question: https://stackoverflow.com/questions/52314045/how-to-use-addtogroup-with-an-aliases-command/52314821#52314821
ALIASES += opengroup{1}="^^* \addtogroup \1_GROUP ^^ * \{ ^^"
ALIASES += close="\}"
/** \opengroup{LEVEL_1} */
// ...code statements...
/** \close */ // opengroup
Does not create a group due to the change of `\{` to just `}`, this behavior has been documented now.
|
|\ \ \ \ \ \ \ \ \ |
|
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
Added asterisks in the type field.
The type is temporary stored in a variable as the argument field has not yet been defined for its argument.
|