summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2020-09-211-6/+6
|\
| * Merge pull request #8048 from albert-github/feature/bug_docu_archDimitri van Heesch2020-09-201-6/+6
| |\ | | | | | | Mismatch documentation and build system
| | * Mismatch documentation and build systemalbert-github2020-09-201-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | Looks like the documentation update after > Commit: 10787eed95266bb1a13c892fe4cf5a695dac1559 [10787ee] > Date: Friday, May 15, 2020 11:28:16 AM > Refactoring has not been done.
* | | Fix compiler warning when printing number of cache hits & missesDimitri van Heesch2020-09-211-1/+1
|/ /
* | Refactoring: replaced QCache by STL based LRU cache implementation.Dimitri van Heesch2020-09-209-3118/+2166
|/ | | | | Also prepared some code for multi-threaded use, and Removed tabs and trailing spaces for code.l
* Fortran comments with C comments inside (#8000)albert-github2020-09-181-1/+1
| | | | | | | | | | | | | When having a (stripped down) example like: ``` ! !!/*T !T*/ ``` we get a warning like: ``` .../ex11f.F90:4: warning: Reached end of file while still inside a (nested) comment. Nesting level 1 (probable line reference: 2, 2) ``` even though Fortran has no nested comments, and certainly doesn't have `/*` as comment signs. So message can be ignored.
* Line count mismatch for Python (#8041)albert-github2020-09-182-4/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When having an example like: ``` ## General \PYgen0 docu # # # # # General detail \PYgen1 text # and more STYLE_TEMPLATE = r''' \makeatletter ''' ## General \PYgen2 docu # # # # # # General detail \PYgen3 text # and more STYLE_TEMPLATE1 = r''' \makeatletter ''' ``` with ``` EXTRACT_ALL = YES QUIET = YES ``` we get the warnings (removed doubles and sorted): ``` bb.py:1: warning: Found unknown command '\PYgen0' bb.py:10: warning: Found unknown command '\PYgen1' bb.py:12: warning: Found unknown command '\PYgen2' bb.py:23: warning: Found unknown command '\PYgen3' ``` we see here (especially with `PYgen3` a wrong line number. After fixing the line count in `pyscanner.l` there was for the second block an offset of 1. This was caused by `commentscan.l` introduced with #7960 after correcting this this offset was also gone. Revisiting the original example of #7960 showed that here here was also an offset of 1 (probably due to a misinterpretation of where the `<tr>` warning should be mentioned), here it is now also correct.. (The original mismatch was shown of Fossies for the Pygments package)
* Fix too aggressive hyphenation of abbr. words. (#8026)Dmitriy Dorofeev2020-09-171-1/+1
| | | | | * Fix too aggressive giphenation of abbr. words. * Remove unwanted change at line 2266
* Merge pull request #8033 from albert-github/feature/bug_ftn_recognDimitri van Heesch2020-09-177-94/+76
|\ | | | | Incorrect duplicate code for Fortran fixed/free recognition
| * Incorrect duplicate code for Fortran fixed/free recognitionalbert-github2020-09-157-94/+76
| | | | | | | | There were 2 routines to recognize whether Fortran code was Fixed of Free format code, though the version in `commentcnv.l` didn't take the settings of `EXTENSION_MAPPING` into account which might lead to incorrect recognition of the format, this has been corrected.
* | Merge pull request #8039 from madebr/xapian_lowercaseDimitri van Heesch2020-09-172-12/+12
|\ \ | | | | | | Lowercase Findxapian module (same casing as upstream xapian-core)
| * | Lowercase Findxapian module (same casing as upstream xapian-core)Anonymous Maarten2020-09-162-12/+12
| | |
* | | Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2020-09-173-7/+9
|\ \ \
| * | | Proposed fix for issue #7898 (#8029)luca-aep2020-09-163-7/+9
| | | | | | | | | | | | | | | | | | | | * Proposed fix for issue #7898 - Internal search engine produce ".html" pages instead of using HTML_FILE_EXTENSION * Applied albert-github suggestions to proposed fix for issue #7898
* | | | issue #8034: doxygen crashesDimitri van Heesch2020-09-172-4/+4
|/ / /
* | | Merge branch 'tolnaisz-arg_name_as_comment'Dimitri van Heesch2020-09-163-1/+76
|\ \ \ | |/ / |/| |
| * | Renamed EXTRACT_ANON_ARGUMENTS to RESOLVE_UNNAMED_PARAMS and enabled it by ↵Dimitri van Heesch2020-09-163-15/+19
| | | | | | | | | | | | default
| * | Merge branch 'arg_name_as_comment' of https://github.com/tolnaisz/doxygen ↵Dimitri van Heesch2020-09-163-1/+72
| |\ \ |/ / / | | | | | | into tolnaisz-arg_name_as_comment
| * | Support commented out argument names in declarations controlled by new cofig ↵Szabi Tolnai2020-08-113-1/+72
| | | | | | | | | | | | EXTRACT_ANON_ARGUMENTS.
* | | Merge pull request #8004 from albert-github/feature/bug_listendDimitri van Heesch2020-09-161-0/+2
|\ \ \ | | | | | | | | Warning about end of list in brief description after alias `^^` replacement
| * | | Warning about end of list in brief description after alias `^^` replacementalbert-github2020-09-031-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | With the alias: ``` ALIASES += "sbl_add_package_main_class{2}=\brief \1 ^^ \2" ``` and the comment: ``` \sbl_add_package_main_class{Defines, \details dihedrals} ``` we will get the replacement: ``` \brief Defines \ilinebr \details dihedrals ``` but this leads to a number of warnings like: ``` warning: End of list marker found without any preceding list items ``` As the end of the brief description is here `\ilinebr` this is replaced in the definition by `\ilinebr.` (so with a `.`). We first have to strip the aritficial newlines at (the beginning and) the end end of the brief description before adding the `.`. (Found as side effect of https://stackexchange.com/filters/57710/doxygen).
* | | | Merge pull request #8003 from albert-github/feature/bug_aliasDimitri van Heesch2020-09-161-6/+6
|\ \ \ \ | | | | | | | | | | Command \ilinebr remained
| * | | | Command \ilinebr reamainedalbert-github2020-09-031-6/+6
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When having the alias: ``` ALIASES += sbl_add_package_main_class{4}="\addtogroup \1-ref-manual ^^ @{ ^^ \class \2 ^^ \brief \3 \4 ^^ @}" ``` for the comment block: ``` /** \sbl_add_package_main_class{Molecular_potential_energy, T_Phi_psi_dihedral_angles_visitor, Defines iterator over all successive pairs of dihedrals., \details Defines iterator over all successive pairs of dihedrals. \tparam CovalentStructure The type of the input covalent structure } */ ``` we get the warning: ``` warning: the name '\ilinebr' supplied as the argument of the \class, \struct, \union, or \include command is not an input file ``` The problem was that the rule: ``` <ClassDocArg2>{FILE}|"<>" { // second argument; include file ``` took the `\ilinebr`, the rule: ``` <ClassDocArg2>{DOCNL} { ``` should habe been checked before. (reported as: https://stackoverflow.com/questions/63710433/doxygen-alias-with-arguments-the-classical-linebr-problem)
* | | | Merge pull request #8036 from madebr/relocatable_cmakeDimitri van Heesch2020-09-1617-79/+79
|\ \ \ \ | |_|_|/ |/| | | Allow building doxygen as a subproject
| * | | Allow building doxygen as a subprojectAnonymous Maarten2020-09-1617-79/+79
|/ / /
* | | Refactoring: making xmlcode.l reentrantDimitri van Heesch2020-09-143-295/+331
| | |
* | | Refactoring: making sqlcode.l reentrantDimitri van Heesch2020-09-132-157/+150
| | |
* | | Refactoring: making vhdlcode.l reentrantDimitri van Heesch2020-09-135-1156/+1185
| | | | | | | | | | | | | | | Also fixed a few VHDL related memory leaks and one newly introduced Fortran memory leak.
* | | Merge pull request #8014 from albert-github/feature/issue_6442Dimitri van Heesch2020-09-121-0/+22
|\ \ \ | | | | | | | | issue #6442 C++: Trailing return type syntax + void
| * | | issue #6442 C++: Trailing return type syntax + voidalbert-github2020-09-081-2/+2
| | | | | | | | | | | | | | | | corrected typo
| * | | issue #6442 C++: Trailing return type syntax + voidalbert-github2020-09-071-0/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When having: ``` /*! * \brief Performs some side effect */ auto side_effect_after() -> void {} ``` We get the warning: ``` warning: return type of member side_effect_after is not documented ``` as the trailing return type was not taken into consideration.
* | | | Merge branch 'albert-github-feature/issue_8015'Dimitri van Heesch2020-09-111-350/+364
|\ \ \ \
| * | | | Split lexer rulesDimitri van Heesch2020-09-111-353/+361
| | | | | | | | | | | | | | | | | | | | | | | | | Also replaced tabs by spaces and removed trailing whitespace And fixed line counting issue.
| * | | | Merge branch 'feature/issue_8015' of ↵Dimitri van Heesch2020-09-111-0/+6
| |\ \ \ \ | | | | | | | | | | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/issue_8015
| | * | | | issue #8015 Special command \skip and \until no longer functional in ALIASESalbert-github2020-09-071-0/+6
| | |/ / / | | | | | | | | | | | | | | | The pattern `\ilinebr` is actually also a line break, but was not handled.
* | | | | Forgot to remove some dead codeDimitri van Heesch2020-09-111-14/+0
|/ / / /
* | | | Merge branch 'albert-github-feature/issue_8017'Dimitri van Heesch2020-09-111-5162/+5197
|\ \ \ \
| * | | | Split into separate rulesDimitri van Heesch2020-09-111-5164/+5183
| | | | | | | | | | | | | | | | | | | | Also replaced tabs by spaces and removed trailing whitespace
| * | | | Merge branch 'feature/issue_8017' of ↵Dimitri van Heesch2020-09-111-0/+16
| |\ \ \ \ |/ / / / / | | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/issue_8017
| * | | | issue #8017 C++: mishandling of brackets used in trailing return typesalbert-github2020-09-081-0/+16
| | | | | | | | | | | | | | | | | | | | Handle `{` and `;` inside, nested, round brackets not as end of return type
* | | | | Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2020-09-111-6/+6
|\ \ \ \ \
| * \ \ \ \ Merge pull request #8020 from albert-github/feature/bug_testsqlite3_python3Dimitri van Heesch2020-09-101-6/+6
| |\ \ \ \ \ | | | | | | | | | | | | | | Make testsqlite3.py python script running with python 3
| | * | | | | Make testsqlite3.py python script running with python 3albert-github2020-09-081-6/+6
| | |/ / / / | | | | | | | | | | | | | | | | | | | | | | | | The testsqlite3.py didn't run under python 3 (found by means of pylint). Making it runnable under python 2 and python 3.
* | | | | | issue #8022: Different results on 64 and 32 bitDimitri van Heesch2020-09-111-1/+1
|/ / / / /
* | | | | Refactoring: making fortrancode.l reentrantDimitri van Heesch2020-09-105-907/+980
|/ / / /
* | | | Merge pull request #8013 from albert-github/feature/bug_trail_retDimitri van Heesch2020-09-071-1/+1
|\ \ \ \ | |/ / / |/| | | Double "->" in warning in case of trailing return type
| * | | Double "->" in warning in case of trailing return typealbert-github2020-09-071-1/+1
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When having the input ``` /*! * \brief Performs some side effect * \param i1 first */ auto side_effect_after(int i1, int i2) -> void; ``` we get the warning ``` warning: The following parameter of side_effect_after(int i1, int i2) -> -> void is not documented: ``` so a double "->". The "->" has already been added in scanner.l and defargs.l so shouldn't be added here. (also the return type gives a warning, but this is another issue #6442)..
* | | Refactoring: making pycode.l reentrantDimitri van Heesch2020-09-064-1206/+1260
| | |
* | | Merge pull request #8007 from albert-github/feature/bug_warn_readDimitri van Heesch2020-09-061-2/+2
|\ \ \ | | | | | | | | Readability of warning message
| * | | Readability of warning messagealbert-github2020-09-041-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A warning like: ``` warning: source examples is not a readable file or directory... skipping. ``` is hard to understand, would be better to have: ``` warning: source 'examples' is not a readable file or directory... skipping. ```