| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
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'
|
| | |
|
| |
|
|
| |
Made implementation analogous to the implementation for parameters in respect to padding and the use of colon (:).
|
| |\
| |
| | |
Cannot properly jump from brief to detailed function description in python
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In case a plain python function (i.e. not in a class or similar) the reference in the brief description to the detailed description points to nowhere as the anchor at the detailed description has file_ in front of it.
The file_ is required for namespaces as mentioned in the code:
// member is in a namespace, but is written as part of the file documentation
// as well, so we need to make sure its label is unique.
tests, on a python project, gave that this doesn't happen and that in case of just files a wrong member reference is given in.
Based on: Generating Python Documentation with doxygen produces broken links to functions (https://stackoverflow.com/questions/50217315/generating-python-documentation-with-doxygen-produces-broken-links-to-functions#50217315)
|
| |\ \
| |/
| |
| |
| | |
# Conflicts:
# src/translator.h
|
| | |
| |
| |
| | |
Found via `codespell`
|
| | |
| |
| |
| |
| | |
Removed restrictions that functions / variables / enums ... in a \name command were executed from the test.
(Note: In case of functions the arguments were tested or presence).
|
| | | |
|
| | | |
|
| |/
|
|
|
|
| |
default.
Remove now unused method trTypeString.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
* Rebased with upstream master
* Added build instructions to README
* Bug 398942 - fixes the problem with instance variables and
arguments with the same name
Signed-off-by: Antonio Terceiro <terceiro@softwarelivre.org>
Signed-off-by: João M. Miranda <joaomm88@gmail.com>
Signed-off-by: Paulo Meirelles <paulo@softwarelivre.org>
Signed-off-by: Vinicius Daros <vkdaros@mercurio.eclipse.ime.usp.br>
Signed-off-by: Jonathan Moraes <arkyebr@gmail.com>
|
| |
|
|
| |
the parameter table for Latex output.
|
| |
|
|
| |
not written
|
| | |
|
| |
|
|
| |
Documentation section
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
improve performance
|
| |
|
|
| |
documented
|
| | |
|
| |
|
|
| |
function (C++)
|
| | |
|
| |
|
|
|
| |
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)
|
| | |
|
| | |
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In a number of instances we don't get the filename of where the error occurs but a name or even unknown between <> e.g.
<fie_p2>:1: warning: parameters of member fie_p2 are not (all) documented
<error>:1: warning: parameters of member p1.error are not (all) documented
<unknown>:1: warning: Member fie_p3 (function) of class p3::int1_p3 is not documented.
This patch tries to overcome this problem by providing the right file:
.../p2.h:8: warning: parameters of member fie_p2 are not (all) documented
.../p1.py:7: warning: parameters of member p1.error are not (all) documented
.../p3.f90:3: warning: Member fie_p3 (function) of class p3::int1_p3 is not documented.
|
| |/ |
|
| |\
| |
| | |
Bug 745481 - Doxygen generates bad "More..." file links for functions within a namespace
|
| | |
| |
| |
| |
| |
| | |
a namespace
Namespaces are recorded at separate pages as well. Condition should be extended for namespaces as well.
|
| |\ \
| |/ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
With the new commands \hidecallgraph and \hidecallergraph it is possible to suppress a call or caller graph even though the corresponding option CALL_GRAPH or CALLER_GRAPH is set.
commands.doc
config.xml
diagrams.doc
- updating documentation to support new commands
entry.cpp
- initialize callgraph and callergraph with the value from the config file
commentscan.l
- add handling for the new commands
context.cpp
memberdef.cpp
util.cpp
- getting the option for CALL_GRAPH and CALLER_GRAPH is not necessary anymore as it is incorporated in the initialization of an Entry item
dbusxmlscanner.cpp
- initialization is done in the Entry item
vhdljjparser.cpp
- gBlock was a static variable and therefore initialized before the doxygen main routine started. A Entry element sets now the default for callgraph and callergraph based on the config file and as the config file is not yet known at that moment the value for CALL_GRAPH and CALLER_GRAPH were set to False. By making a pointer of gBlock and doing an appropriate new Entry call this problem is overcome.
|
| |/ |
|
| |
|
|
|
| |
When having a not documented MODULE member it is mentioned that a member in a 'namespace' is not documented. For Fortran this is a bit strange as Fortran does not know the term namespace, modules are handled as namespaces (in the pre 1.8.9 version a message was given about 'class', which is equally confusing).
This patch changes in this case 'namespace' to 'module'.
|
| |\
| |
| | |
Remove unused local and static global variables
|
| | |
| |
| |
| | |
Remove unused local and static global variables. Variables have been identified by Understand (version 758) from Scitools.
|
| |/
|
|
|
| |
Also made dangerous string access more visible by introducing rawData().
This replaces data() which will now return a constant string.
|
| | |
|
| |
|
|
| |
tagfile
|
| | |
|
| | |
|
| | |
|
| | |
|
