summaryrefslogtreecommitdiffstats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* Incorrect counting of markdown verbatim blockalbert-github2020-10-081-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When we have a file aa.md like: ``` Initial text 1 verbatim text? Some text \aa5 ``` and a file bb.md like ``` Initial text 1 verbatim text? Some text \aa4 `` we get the warnings like (with current master, with 1.8.20 it is even further off): ``` aa.md:6: warning: Found unknown command '\aa5' bb.md:5: warning: Found unknown command '\aa4' ``` instead of ``` aa.md:5: warning: Found unknown command '\aa5' bb.md:4: warning: Found unknown command '\aa4' ``` This has been corrected
* Warnings during compilation of doctokinizeralbert-github2020-10-071-1/+1
| | | | | | | | | With the doctokinizer.l we get the warnings like: ``` doctokenizer.l(502): warning C4018: '<': signed/unsigned mismatch ``` The casting of `(int)` is also used on other places in this file like in `handleHtmlTag`.
* Minor tweaksDimitri van Heesch2020-10-051-60/+47
| | | | | | - lineCount() without arguments was unused - converted lineCount(...) into a macro with yytext and yyleng as arguments
* Merge branch 'feature/bug_doctok_cnt' of ↵Dimitri van Heesch2020-10-053-238/+315
|\ | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_doctok_cnt
| * Miscounting lines in doctokinizeralbert-github2020-09-203-238/+315
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When having a file like: ``` @page md_aa aa Last \error2 - Install \error3 ``` we get the warnings: ``` aa.md:3: warning: Found unknown command '\error2' aa.md:7: warning: Found unknown command '\error3' ``` instead of ``` aa.md:3: warning: Found unknown command '\error2' aa.md:5: warning: Found unknown command '\error3' ``` Investigation lead to that this is due to the fact that with a `REJECT` the line counter in `doctokinizer.l` is not reset. By counting the lines ourselves we can properly count the lines. (Other lexers don't have this problem as here we already do the counting ourselves)
* | added support for mingw PRETTY_FUNC (#8059)ArmandZampieri2020-10-051-1/+1
| | | | | | | | | | | | | | | | | | * added support for mingw PRETTY_FUNC * More compact Define test for PRETTY_FUNCTION * corrected synthax issue Co-authored-by: ZAMPIERI Armand <armand.zampieri@cmigroupe.com>
* | Merge branch 'albert-github-feature/bug_md_pg_cnt'Dimitri van Heesch2020-10-0411-58/+75
|\ \
| * | Reworked changes a bitDimitri van Heesch2020-10-0410-64/+52
| | | | | | | | | | | | | | | | | | - topLine is replaced by startLine - changed unputDocnl macro into a more self contained function-like macro
| * | Merge branch 'feature/bug_md_pg_cnt' of ↵Dimitri van Heesch2020-10-0314-61/+90
| |\ \ | | | | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_md_pg_cnt
| | * | Miscounting of lines in respect to page commandalbert-github2020-09-241-3/+6
| | | | | | | | | | | | | | | | `file` was overwritten but this should not happen, onlt for warnings this would be OK.
| | * | Miscounting of lines in respect to page commandalbert-github2020-09-2414-62/+88
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | All examples together are a bit big so they are all in the attached file together with the warnings before and after this patch. When looking at the output we see that a number of lines are off by 1 ore more due to the insertion of extra lines in the code or due to the fact that there is a reference to the start of the documentation of the page and not the line of the page command. - commentscan.l in case of a rule contaiinge {DOCNL} this can be `=n` or `\ilinebr` in the later case this should not be replaced by `\n` as this results in an increase of the line count later on. in case of a page like command also register the line of the command as "topline". - entry.h, entry.cpp storage space for the "topline" registering the line of the page like commands. - doxygen.cpp setting and using the "topline" - markdown.cpp, markdown.h don't add a `\n` as this increases the line count but use the `\ilinebr` to get correct warnings see to it that when having empty lines at the top of the page and a page is added that the empty lines appear after the page command. - index.cpp using the "topline" instead of the "docLine" to get the correct warning - pagedef.cpp, pagedef.h set and retrieve the "topline" for page like commands. - util.cpp, util.h setting and using the "topline" in `addRelatedPage` use the known file name and line for the warning regarding the section label - cite.cpp, context.cpp, reflist.cpp changed to have good function calls.
* | | | Incorrect recognition as RCS tagalbert-github2020-10-041-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When we have a, stripped down, example like: ``` \mainpage the page <tt>$PATH:</tt>$x86$<tt>bin</tt> ``` we get the warning like: ``` aa.md:4: warning: end of comment block while expecting command </tt> ``` this is due to the fact that `$PATH:</tt>$` is seen as a RCS tag although `PATH` is not a RCS keyword. Limiting the number of allowed keywords to the real RCS tags (for CVS the list is the same). See also: - https://www.gnu.org/software/trans-coord/manual/cvs/cvs.html#Keyword-substitution - https://www.gnu.org/software/rcs/manual/rcs.html#Keywords
* | | | Flush warnings file (#8069)albert-github2020-10-033-0/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Flush warnings file When having a large project the warnings file is buffered but when a long time there are no warnings emitted the last warnings are not yet written. During testing tis is most obvious when the `dot` process starts and one needs the `.dot` files but not the converted files at hat moment one wants to kill the doxygen process but the result is an incomplete warnings file of the warnings that should already be written. Created a flush function for the warnings file and placed it at a few strategic points. * Flush warnings file Last minute change without proper testing ( :-( ) * Flush warnings file void is the default changed for consistency and due to (http://www.dietmar-kuehl.de/mirror/c++-faq/newbie.html#faq-29.4): > C programmers often use f(void) when declaring a function that takes no parameters, however in C++ that is considered bad style. In fact, the f(void) style has been called an "abomination" by Bjarne Stroustrup, the creator of C++, Dennis Ritchie, the co-creator of C, and Doug McIlroy, head of the research department where Unix was born.
* | | | Merge pull request #8072 from albert-github/feature/bug_consitency_voidDimitri van Heesch2020-10-035-24/+24
|\ \ \ \ | |/ / / |/| | | Using f() instead f(void) in C++ , consistency
| * | | Using f() instead f(void) in C++ , consistencyalbert-github2020-10-025-24/+24
| | | | | | | | | | | | | | | | Seen the discussion in the pull request #8069, for consistency change occurrences of f(void) into f().
* | | | refactoring: modernize search indexDimitri van Heesch2020-10-032-157/+116
|/ / / | | | | | | | | | Also QVector has been removed from qtools as it was no longer used.
* | | Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2020-10-022-2/+2
|\ \ \
| * \ \ Merge pull request #8068 from albert-github/feature/bug_loss_dataDimitri van Heesch2020-10-011-1/+1
| |\ \ \ | | | | | | | | | | Warning about possible loss of data
| | * | | Warning about possible loss of dataalbert-github2020-10-011-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Om 64-bit windows platform we get the warning: ``` src\template.cpp(341): warning C4267: 'return': conversion from 'size_t' to 'uint', possible loss of data ``` Explicit setting conversion..
| * | | | Warning in internal documentationalbert-github2020-10-011-1/+1
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The internal documentation gives warning: ``` .../src/clangparser.h:33: warning: argument 'fileName' of command @param is not found in the argument list of ClangTUParser::switchToFile(FileDef *fd) .../src/clangparser.h:35: warning: The following parameter of ClangTUParser::switchToFile(FileDef *fd) is not documented: parameter 'fd' ``` this is corrected. (Note: warning regarding TokenManager is an javaCC upstream problem and corrected in their master).
* | | | issue #7706: Md5 hash does not match for two different runsDimitri van Heesch2020-10-021-2/+2
|/ / /
* | | issue #8066: Doxygen crashes in ClangTUParserDimitri van Heesch2020-09-302-4/+10
| | |
* | | Merge pull request #8060 from albert-github/feature/bug_md_open_bracketDimitri van Heesch2020-09-291-0/+2
|\ \ \ | | | | | | | | No warning for unbalanced brackets in markdown
| * | | No warning for unbalanced brackets in markdownalbert-github2020-09-251-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When we have the input files qq.md. ``` @page xxx0 yyy0 @} Start of text @page xxx1 yyy1 @{ Start of text ``` and qqh.h: ``` /** @page xxxh0 yyyh0 @} Start of texth */ /** @page xxxh1 yyyh1 @{ Start of texth */ ``` we get the warnings: ``` qq.md:3: warning: unbalanced grouping commands qqh.h:4: warning: unbalanced grouping commands qqh.h:15: warning: end of file with unbalanced grouping commands ``` ``` so we are missing ``` qq.md:9: warning: end of file with unbalanced grouping commands ``` due to the fact that the closing routine was not called (also the open routine was not called, always good to call it the set variables to their proper values.
* | | | Incorrect sorting of reflist itemsalbert-github2020-09-291-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When having an example like: ``` /// \file /** \xrefitem my_errors "err2" "ERR1" ERROR 101*/ #define MY_ERR_CANNOT_OPEN_FILE 101 /** \xrefitem my_errors "err2" "ERR2" ERROR 102*/ #define MY_ERR_CANNOT_CLOSE_FILE 102 /** \xrefitem my_errors "err2" "ERR1a" ERROR 101a*/ #define MY_ERR_CANNOT_OPEN_FILE3 103 /** \xrefitem my_errors "err2" "ERR2a" ERROR 102a*/ #define MY_ERR_CANNOT_CLOSE_FILE4 104 ``` the sorting should be done on the part `MY_ERR_CANNOT_...` but no sorting is done (since 1.8.18) as: - call to `qstricmp` contains twice the same value - a boolean value should be the result of the compare but in fact an integer value was returned This problem is most likely a regression due to ``` Commit: aca13723a9373a1080ca7f108e7be0905b9ae793 [aca1372] Date: Thursday, February 27, 2020 10:38:22 PM Restructure the way RefLists are handled ```
* | | | issue #8063: Failed to build current "master" branchDimitri van Heesch2020-09-283-13/+19
| | | |
* | | | Fix for broken LaTeX output.Dimitri van Heesch2020-09-2720-42/+42
| | | | | | | | | | | | | | | | | | | | | | | | Fixes error: "\begin{DoxyCodeInclude} on input line 93 ended by \end{DoxyCode}" while generating the LaTeX version of the manual
* | | | Merge branch 'multithread_outputgen'Dimitri van Heesch2020-09-2734-750/+862
|\ \ \ \ | |/ / / |/| | |
| * | | Refactoring: prepare output generators for multi-threaded useDimitri van Heesch2020-09-2734-750/+862
| |/ /
* | | Merge pull request #8045 from albert-github/feature/bug_md_fenced_cntDimitri van Heesch2020-09-241-1/+1
|\ \ \ | | | | | | | | Miscounting of lines in case of fenced code block
| * | | Miscounting of lines in case of fenced code blockalbert-github2020-09-201-1/+1
| | |/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When we have an example like: ~~~ Page ======= test text test text \error1 ``` make ``` ``` make ``` test text \error2 ~~~ we get the warnings: ``` aa.md:5: warning: Found unknown command '\error1' aa.md:17: warning: Found unknown command '\error2' ``` instead of ``` aa.md:5: warning: Found unknown command '\error1' aa.md:15: warning: Found unknown command '\error2' ``` this is due to the fact that there are 2 returns in case of a fenced code block, one with the ``endcode` but with the detection of the fenced code block (`isFencedCodeBlock`) it is not "removed".
* | | Merge pull request #8052 from albert-github/feature/issue_8051Dimitri van Heesch2020-09-241-2/+2
|\ \ \ | | | | | | | | #8051 Consider documenting debug options of doxygen
| * | | #8051 Consider documenting debug options of doxygenalbert-github2020-09-231-2/+2
| | |/ | |/| | | | | | | | | | - don't create an error in case of no argument, just handle it as a request for help. - give the usage also in case of an error (besides the error message)
* | | issue #8053 error: Attribute target redefined in SVGalbert-github2020-09-241-0/+1
|/ / | | | | | | regression on #7706 (although it has nothing to do with double runs in my opinion as indicated in the title of that issue: " Md5 hash does not match for two different runs") looks like this statement should be present.
* | Fix compiler warning when printing number of cache hits & misses (part 2)Dimitri van Heesch2020-09-211-1/+2
| |
* | issue #8037: Links using @ref stopped working in doxygen 1.8.19Dimitri van Heesch2020-09-219-2/+10
| |
* | 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-205-2004/+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 branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2020-09-172-5/+5
|\ \
| * | Proposed fix for issue #7898 (#8029)luca-aep2020-09-162-5/+5
| | | | | | | | | | | | | | | * 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
|/ /
* | 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
generated by cgit v0.12 at 2024-11-16 02:03:09 (GMT)