summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2019-05-2710-14/+203
|\
| * Merge pull request #7007 from albert-github/feature/bug_latex_appendixDimitri van Heesch2019-05-251-16/+44
| |\ | | | | | | More than 26 appendices in LaTeX manual
| | * More than 26 appendices in LaTeX manualalbert-github2019-05-231-16/+44
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The 1.8.15 manual had 26 examples but due to the fact that a new example was created we got 27 and thus the characters A-Z are not sufficient. In a number of LaTeX versions this leads to messages like: ``` Appendix \GenericError { }{LaTeX Error: Counter too large}{See th e LaTeX manual or LaTeX Companion for explanation.}{You've lost some text. Try typing <return> to proceed.\MessageBreak If that doesn't work, type X <retu rn> to quit.}. ! LaTeX Error: Counter too large. ``` Solution for this is to reorganize the examples a little bit. This is done here by means of the "groups": - Style examples - Language Examples as a consequence also the sections / subsections etc had to go 1 level deeper and this is accomplished by defining a new environment in which the different sections go 1 level deeper.
| * Merge pull request #6957 from ↵Dimitri van Heesch2019-05-218-0/+155
| |\ | | | | | | | | | | | | cfriedt/feature/cfriedt/6955/allow-javadoc-style-comment-blocks-with-a-doxyfile-variable Allow Javadoc-style comment blocks with a Doxyfile variable
| | * do not clobber version placeholderChristopher Friedt2019-05-181-1/+1
| | |
| | * updated manual, included examples in documentationChristopher Friedt2019-05-172-1/+12
| | |
| | * make similar javadoc banner change for stripping special comments from codeChristopher Friedt2019-05-091-0/+18
| | |
| | * add blurb to docblocksChristopher Friedt2019-05-091-0/+10
| | |
| | * Allow Javadoc-style comment blocks with a Doxyfile variableChristopher Friedt2019-05-035-0/+116
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Javadoc allows comments like this (which I refer to as "banner" comments) /***************** * *****************/ but doxygen does not recognize them. Instead, the doxygen manual says to do this /*************//** * ****************/ which some users aren't even aware is required. It also behaves poorly with clang-format. I'm proposing to add a Doxyfile boolean option JAVADOC_BANNER which will default to NO. When set to YES, it will consider the first and second comments above to be equivalent. However, I don't believe that the JAVADOC_BANNER option should default to YES, as there are likely a number of projects who have used the former syntax with full expectation that it would *not* appear in their documentation. At least having the JAVADOC_BANNER default to NO allows users to opt-in voluntarily by adding JAVADOC_BANNER = YES to their Doxyfile. If the consensus is to make it a default at a later time, first a warning can be added during build that should trigger users to modify their comment style, and then eventually the default could be set to JAVADOC_BANNER = YES, or the config option could be removed entirely and it would just always be enabled.
| * | Merge pull request #7001 from albert-github/feature/bug_lex_debugDimitri van Heesch2019-05-212-0/+6
| |\ \ | | | | | | | | Missing debug statements sqlcode and xmlcode lexers
| | * | Missing debug statements sqlcode and xmlcode lexersalbert-github2019-05-202-0/+6
| | | | | | | | | | | | | | | | The messages for `doxygen -d lex` were missing in case of the sqlcode.l and xmlcode.l
* | | | Bug 757574 - Warning regarding subsection with anchor in markdownDimitri van Heesch2019-05-271-3/+25
|/ / /
* | | Bug 757574 - Warning regarding subsection with anchor in markdownDimitri van Heesch2019-05-201-15/+8
| | |
* | | Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2019-05-192-1/+35
|\ \ \ | |/ /
| * | Merge pull request #6916 from albert-github/feature/bug_py_classDimitri van Heesch2019-05-191-0/+26
| |\ \ | | | | | | | | Class definition with collections
| | * | Class definition with collectionsalbert-github2019-04-071-0/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Class definitions can have collections and these can have strings e.g.: class Url(namedtuple('Url', url_attrs)): and this results in: warning: Detected potential recursive class relation between class conda::_vendor::urllib3::util::url::Url and base class Url! Strings are now possible and seen as strings. See also (including example with namedtuble): https://docs.python.org/3/library/collections.html
| * | | Merge pull request #6961 from albert-github/feature/bug_nested_comment_tcl_pyDimitri van Heesch2019-05-191-1/+9
| |\ \ \ | | | | | | | | | | Incorrect Reached end of file while still inside a (nested) comment for TCL / Python
| | * | | Incorrect Reached end of file while still inside a (nested) comment for TCL ↵albert-github2019-05-031-1/+9
| | | |/ | | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | / Python In case we have in the comment (or in the code) of a TCL file of Python file a construct like: ``` proc get_suite {dir {sort 1}} { set files [glob -nocomplain $dir/*.bin] set files [glob -nocomplain $dir/*.ps] } ``` we get the warning: ``` warning: Reached end of file while still inside a (nested) comment. Nesting level 2 (probable line reference: 3, 2) ``` although the '/*' construct has no special comment meaning in TCL / Python (comment signs '#' / '#' or '"""). So if a c-comment construct is found it is ignored for TCL and Python.
* | | | Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2019-05-181-2/+2
|\ \ \ \ | |/ / /
| * | | Merge pull request #6962 from albert-github/feature/bug_output_tag_orderDimitri van Heesch2019-05-181-2/+2
| |\ \ \ | | | | | | | | | | Incorrect output tag order
| | * | | Incorrect output tag orderalbert-github2019-05-041-2/+2
| | |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When we have the Mardown file: ``` # First heading level 1 Some text ... ``` we get in the HTML file: ``` ... <div class="PageDoc"><div class="header"> <div class="headertitle"> <div class="title">First heading level 1 </div> </div> </div><!--header-->javascript"> <div class="contents"> <div class="textblock"><p>Some text ... </p> </div></div><!-- PageDoc --> </div><!-- contents --> ... ``` Here we see that the `PageDoc` is closed before the `Contents` although the `PageDoc` was opened before the `Contents`. In this constellation it doesn't give problems as both translate to `</div>` tag and in other output formats nothing is outputted, but in case in another format something is outputted this might lead to problems also the comment is now so that is indicates the error.
* | | | Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2019-05-183-198/+115
|\ \ \ \ | |/ / /
| * | | Merge pull request #7000 from doxygen/revert-6987-issue6960_bDimitri van Heesch2019-05-182-175/+92
| |\ \ \ | | | | | | | | | | Revert "alternate fix for .dot file handling"
| | * | | Revert "alternate fix for .dot file handling"Dimitri van Heesch2019-05-182-175/+92
| |/ / /
| * | | Merge pull request #6971 from albert-github/feature/issue_6945Dimitri van Heesch2019-05-181-23/+23
| |\ \ \ | | | | | | | | | | issue #6945 \class after \brief doesn't count as a new line - resulting docs show merged descriptions
| | * | | issue #6945 \class after \brief doesn't count as a new line - resulting docs ↵albert-github2019-05-081-23/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | show merged descriptions Set "ends brief description" for the different for the commands mentioned in issue (as well as addtogroup)
* | | | | Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2019-05-181-0/+2
|\ \ \ \ \ | |/ / / /
| * | | | Merge pull request #6977 from mrhatch97/fix-cpp17-namespacesDimitri van Heesch2019-05-181-0/+2
| |\ \ \ \ | | | | | | | | | | | | Fixes #6765 - Fixed C++17-namespace assignment bug
| | * | | | Fixed C++17-namespace assignment bugMatthew Hatch2019-05-091-0/+2
| | |/ / / | | | | | | | | | | | | | | | Added scope save and restore before and after namespace parsing
* | | | | Fixed issue in doxmlparser in getter functionDimitri van Heesch2019-05-181-1/+1
|/ / / /
* | | | Merge pull request #6983 from albert-github/feature/bug_utf8_nbspDimitri van Heesch2019-05-181-6/+19
|\ \ \ \ | | | | | | | | | | Special handling of the UTF8 nbsp sequence
| * | | | Special handling of the UTF8 nbsp sequencealbert-github2019-05-111-6/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The UTF8 nbsp sequence 0xc2 0xa0 is not seen as a whitespace sequence and not handled properly. This can lead to: ``` warning: found </c> tag without matching <c> ``` when we have e.g. ```e.g. `linux`<br>``` where the space between the `.` and the backtick is actually the UTF8 nbsp sequence Replacing the the UTF8 nbsp sequence with the `&nbsp;` sequence.
* | | | | Merge pull request #6991 from albert-github/feature/issue_6990Dimitri van Heesch2019-05-181-0/+1
|\ \ \ \ \ | | | | | | | | | | | | issue #6990 Dot produces no Graphs
| * | | | | issue #6990 Dot produces no Graphsalbert-github2019-05-151-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | Backslashes also have to be escaped otherwise a tooltip / brief description like `//!replace "\" with "\\"` won't be produced properly.
* | | | | | Merge pull request #6987 from thomas-haller/issue6960_bDimitri van Heesch2019-05-172-92/+175
|\ \ \ \ \ \ | | | | | | | | | | | | | | alternate fix for .dot file handling
| * | | | | | added check if .dot file is already queued for processing before adding a ↵Thomas Haller2019-05-142-51/+114
| | | | | | | | | | | | | | | | | | | | | | | | | | | | new processing job
| * | | | | | delayed creation and update of .md5 files after successful creation of ↵Thomas Haller2019-05-142-43/+52
| | | | | | | | | | | | | | | | | | | | | | | | | | | | output files
| * | | | | | node numbers removed for md5 calculation to avoid false md5 mismatchesThomas Haller2019-05-131-15/+26
| | | | | | |
* | | | | | | Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2019-05-1512-1221/+1200
|\ \ \ \ \ \ \
| * \ \ \ \ \ \ Merge pull request #6988 from albert-github/feature/bug_htags_call_graphDimitri van Heesch2019-05-151-8/+5
| |\ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | USE_HTAGS = YES, there are _no_ call / caller graphs in the documentation
| | * | | | | | | USE_HTAGS = YES, there are _no_ call / caller graphs in the documentationalbert-github2019-05-141-8/+5
| | | |/ / / / / | | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
| * | | | | | | Merge pull request #6989 from albert-github/feature/bug_htags_filemapDimitri van Heesch2019-05-151-1/+1
| |\ \ \ \ \ \ \ | | |/ / / / / / | |/| | | | | | Don't try to load htags filemap in case htags fails
| | * | | | | | Don't try to load htags filemap in case htags failsalbert-github2019-05-141-1/+1
| |/ / / / / / | | | | | | | | | | | | | | | | | | | | | 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
| * | | | | | Merge pull request #6985 from albert-github/feature/bug_enable_doxmlparserDimitri van Heesch2019-05-1311-1212/+1194
| |\ \ \ \ \ \ | | | | | | | | | | | | | | | | Enable example doxmlparser possibilities for cmake build
| | * | | | | | Enable example doxmlparser possibilities for cmake buildalbert-github2019-05-1211-1212/+1194
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The doxmlparser example program could be build by the build system before the use of cmake. In cmake it was available but "disabled" by means of an empty CMakeLists.txt in the doxmlparser main directory. (Windows is not fond of symbolic links, so removing link between src/doxmlintf.h and include/doxmlintf.h)
* | | | | | | | issue 6986: C++ static template methods: duplication as non-static and ↵Dimitri van Heesch2019-05-151-0/+6
|/ / / / / / / | | | | | | | | | | | | | | | | | | | | | specialization
* | | | | | | Merge branch 'albert-github-feature/svg_image_determnation'Dimitri van Heesch2019-05-131-1/+5
|\ \ \ \ \ \ \ | |_|/ / / / / |/| | | | | |
| * | | | | | Simplified code a bitDimitri van Heesch2019-05-131-15/+5
| | | | | | |
| * | | | | | Merge branch 'feature/svg_image_determnation' of ↵Dimitri van Heesch2019-05-131-1/+15
| |\ \ \ \ \ \ |/ / / / / / / | | | | | | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/svg_image_determnation
| * | | | | | Image not seen as svg imagealbert-github2019-04-051-1/+15
| | |_|_|_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In case a svg image url has some decoration behind it, the image is not seen as a svg image. The decoration is taken away from the determination. Found by means of: ``` [![Build Status](https://api.travis-ci.com/ILIAS-eLearning/ILIAS.svg?branch=release_5-3)](https://travis-ci.com/ILIAS-eLearning/ILIAS) [![Minimum PHP Version](https://img.shields.io/badge/php-%3E%3D%205.6-8892BF.svg)](https://php.net/) ```
generated by cgit v0.12 at 2024-11-01 16:40:24 (GMT)