| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_endblock_msg
|
| |
| |
| |
| | |
Consistency
|
|\ \
| | |
| | |
| | | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_6831
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There are 2 different situations here:
- @var, here a special change is necessary to check and handle whether or not we are in PHP (declinfo.*, doxygen.cpp)
- @param
- the type recognition for the PHP type has to be extended with the `[]` possibility and subsequently the `[]` part has to be handled separately from the 'datatype' (doctokinizer.l, docparser.*).
- In the output we now can have multiple text strings resulting in a small change in handling of the separator between the data type (*docvisitor.*)
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_gitversion
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The original version has as features:
- getting the git version number for usage in doxygen
- making the doxygen version number inclusion dependent on the VERSION file
The disadvantage of the chosen methodology was that an extra correction step was necessary, by defining getter methods to retrieve the values this correction can be hidden.
The information is coming from different sources:
- the VERSION file
- the git "repository and build system (when present)
Furthermore there are a couple of places where the version information is used (a.o. doxygen and doxywizard executable, though the doxygenwizard was only done "half hearted")
The handling of the VERSION file has been made in such a way that it is comparable with the generation of the git version changes.
For a better abstraction the version handling is all done in a separate directory.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Show the git version on designated places (currently version, help and Doxyfile difference).
The implementation is based on the git_watcher.cmake (https://github.com/andrew-hardin/cmake-git-version-tracking).
The information is useful to see which. master, version of doxygen is used for a build on systems where a lot of builds are make (Fossies.org) or very regular builds are made (CGAL)
Furthermore the tracking of the VERSION file was not done (when changed the version.cpp was not updated), this is corrected as well.
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
groleo-docgroup
|
| | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: Adrian Negreanu <groleo@gmail.com>
|
| | | | |
| | | | |
| | | | |
| | | | | |
Read the DoxygenLayout file in a similar way as the header / footer etc. for HTML and feed the (converted) result into the XML reader.
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
Correct spelling "build in" vs. "built-in"
|
| | | | | |
|
| | | | | |
|
| |_|_|/
|/| | | |
|
|\ \ \ \
| | | | |
| | | | | |
Ambiguous file name in file command
|
| | | | |
| | | | |
| | | | |
| | | | | |
The file command has only one argument.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
I some cases a file name is used with the `\file` command and this filename exists multiple times although the `\file` command is in the file itself (actually file name can be omitted).
Another possibility is that the file description is in another file in the same directory.
When file is not found or ambiguous, try to prepend the path of the current file to it and see if the file can be found.
Example is shown in the warnings file like:
```
gmic-2.6.1/gmic-qt/src/Common.h:3: warning: the name `Common.h' supplied as the second argument in the \file statement matches the following input files:
gmic-2.6.1/gmic-qt/src/Common.h
gmic-2.6.1/zart/include/Common.h
Please use a more specific name by including a (larger) part of the path!
```
and here it is quite clear and unambiguous which file is meant.
|
|\ \ \ \ \ |
|
| |\ \ \ \ \
| | | | | | |
| | | | | | | |
USE_HTAGS = YES, there are _no_ call / caller graphs in the documentation
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Even when htags are enabled the source code has to be parsed, but should not be written by doxygen writers. During the "generateFileSources" some other settings are done as well like for "REFERENCED_BY_RELATION".
(based on question of Maciej W via lists.sourceforge.net on March 24 2014)
|
| |/ / / / /
| | | | | |
| | | | | |
| | | | | | |
Don't try to load htags filemap in case htags fails as when a wrong / old filemap is lying around this leads / can lead to incorrect results
|
|/ / / / /
| | | | |
| | | | |
| | | | | |
specialization
|
|\ \ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Some messages give a result in the form of:
`'static ostream & operator<<(ostream &out, const EntityAuth &a)' at line 61 of fileD:/Fossies/ceph-14.2.1/src/auth/Auth.h`
i.e. space was missing `file` and `D:`
|
|/ / / / / |
|
|/ / / / |
|
| |/ /
|/| | |
|
|\ \ \
| |/ /
|/| | |
Bug 645910 - Segfault on recursion while parsing "\subpage A" in "\page A"
|
| | |
| | |
| | |
| | |
| | | |
In version 1.7.3 (till 1.8.7) the problem of direct recursion (i.e. in a page is a subpage to itself) we got a segmentation fault, as of 1.8.8 the problem went into an endless loop.
The direct recursion is now detected.
|
|\ \ \
| | | |
| | | | |
issue #6847 Physical newlines (^^) in ALIASES produce a mismatch between documentation and source code
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
documentation and source code
In 1.8.15 the `^^` was already translated to `\_linebr` but here there was a ` ` (space) after the `^^`, here this is not the case resulting in "warning: Found unknown command `\_linebrline'"
placing a ` ` after the translated value solves this problem.
|
|/ / |
|
|/ |
|
|\
| |
| | |
Bug 766508 - missing comments of overridden methods
|
| |
| |
| |
| | |
Analogous to python also for PHP and Java all functions are by default virtual (for python fix see problem #6566 and fix #6570)
|
|/
|
|
|
|
| |
with sections, subsections, subsubsections and paragraphs
Previous changes corrected use of _linebr, missed one so this was not handled properly.
|
|
|
|
| |
in the XML output
|
|\
| |
| |
| | |
https://github.com/cheoljoo/doxygen into cheoljoo-run_java_once_3rd_trial
|
| |
| |
| |
| |
| |
| | |
- remove PLANTUML_RUN_FAST in config.xml
- Do not make plantuml (.pu) file for each plantuml script. (ex. inline_umlgraph_#.pu)
But, make type plantuml files (ex. inline_umlgraph_<type>..pu)
|
|\ \
| |/
| |
| | |
https://github.com/cheoljoo/doxygen into cheoljoo-run_java_once_3rd_trial
|
| | |
|
| | |
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
# What is it
- #6465 is the first reqeust. So I followed up the albert advice.
- in case of debug you use printf statements, I think that here there better options would be
- create an -d flag (e.g. -d plantuml) that gives the information, so no need for using the configuration option
- Follow up : create -d plantuml [debug.h, debug.cpp]
- usage of printf
- printf should not be used,all output is steered over calls to routines as defined in message.cpp,
- Follow up : use Debug::Print(Debug::Plantuml, ... and msg()
- usage of std::string / std::map
- in doxygen the string manipulation is. mostly, done by means of Qt classes (e.g. classes QCString, QString). For consistency these classes should be used.
- map manipulation is also done by means of Qt classes (dictionary and list classes)
- Follow up : use QDict QList QCString [plantuml.h, plantuml.cpp]
- dirent / opendir /readdir
- when browsing through directories the routines line readFileOrDirectory should probably be used or the techniques used in this routine
- Follow up : I will follow when I try to reduce redundancy of creating plantuml image.
- Run java minimally
- Test Case : 4 plantuml
- Original Run without PLANTUML_RUN_JAVA_ONCE
- 8.2 sec = 4 times * ( 1.6(java vm) + 0.1 * 1(load multiple file) + process each plantuml (0.35) *1 ) <- prediction
- New with PLANTUML_RUN_JAVA_ONCE
- 3.499 sec = 1.6(java vm) + 0.1 * 4(load multiple file) + process each plantuml (0.35) *4 <- prediction
- Creating Java Virtual Machine has a big portion.
- Result
- Improving Performance : 8.2 -> 3.499 (in case of 4 plantuml)
# Configuration
- add configuration value in Doxyfile
- PLANTUML_RUN_JAVA_ONCE = YES
# Debugging
- doxygen -d plantuml
- doxygen -d time -d plantuml
# Tested with following options
- source code of 3 plantuml
- PLANTUML_RUN_JAVA_ONCE = YES or NO
- DOT_IMAGE_FORMAT = png or svg
- DOT_CLEANUP = YES or NO
- -d plantuml
|
| |/
|/| |
|
|\ \
| | |
| | |
| | | |
zeroc-ice-master
|
| |\ \ |
|