summaryrefslogtreecommitdiffstats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* issue #8105 How do add (multiple files without extension) directory in INPUT ↵albert-github2020-10-161-1/+2
| | | | | | field of doxygen configuration file Small explanation added as it is not clear what to use in case of `no_extension` in `FILE_PATTERNS`
* Merge pull request #8097 from albert-github/feature/issue_8093Dimitri van Heesch2020-10-151-1/+1
|\ | | | | issue #8093 Some URLs in fresh/updated Doxyfile are split over two lines
| * issue #8093 Some URLs in fresh/updated Doxyfile are split over two linesalbert-github2020-10-131-1/+1
| | | | | | | | | | Created an explicit split of the line before the http address so the URL will start on a new line in the doxygen configuration file and won't be split anymore (unless the total length of the URL will be longer than 78 characters but this is in the doxygen settings not the case). (The other formats: HTML, LateX and the help in the doxywizard give still the same output results).
* | Merge pull request #8096 from albert-github/feature/bug_dvipsDimitri van Heesch2020-10-151-6/+6
|\ \ | | | | | | Don't start dvips when latex fails for formulas
| * | Don't start dvips when latex fails for formulasalbert-github2020-10-131-6/+6
| |/ | | | | | | In case the latex process fails for formulas there is no reason to try to start a dvips process.
* | Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2020-10-151-1/+2
|\ \
| * \ Merge pull request #8100 from albert-github/feature/bug_latex_fig_spaceDimitri van Heesch2020-10-151-1/+2
| |\ \ | | | | | | | | Space around images in LaTeX output is sometimes a bit large
| | * | Space around images in LaTeX output is sometimes a bit largealbert-github2020-10-141-1/+2
| | |/ | | | | | | | | | | | | | | | | | | | | | When we look at images in documents we see for a number of images a big amount of white space around the image. This is e.g. the case in the doxygen manual at page 99 of the 1.8.20 version. - using `\raggedbottom` sees to it that the space inside the page is removed (there might be some white space when the next image doesn't fit anymore. (See https://tex.stackexchange.com/questions/566779/placing-figures-on-a-fixed-place-without-lot-of-space-around-it) - use `\centering` instead of `\begin{center}` as the center environment adds some extra white space (see a comment with the question, on a different subject though: https://stackoverflow.com/questions/64328597/pdftex-warning-saying-about-duplicate-figures#comment113772445_64328597)
* | | issue #8102 [C++] Reference relations are not generated for constructors ↵Dimitri van Heesch2020-10-151-0/+8
|/ / | | | | | | using list initialization
* | Incorrect label / name in case regeneration of HTML without regeneration of ↵albert-github2020-10-151-1/+1
| | | | | | | | | | | | | | dot files This is a further regression on #7840. In case we regenerate the HTML files but not the image files based on dot we get incorrect labels for the id / name in the HTML output.
* | issue #8091: [C++] Newer doxygen versions add a lot of bogus warnings about ↵Dimitri van Heesch2020-10-145-60/+70
|/ | | | undocumented entities
* Merge pull request #8092 from albert-github/feature/bug_transl_sliceDimitri van Heesch2020-10-1226-6/+119
|\ | | | | Translation function trCompoundListDescription no entry for SLICE
| * Translation function trCompoundListDescription no entry for SLICEalbert-github2020-10-1226-6/+119
| | | | | | | | | | A number of languages have no translation in the function `trCompoundListDescription()` in case the `OPTIMIZATION_OUTPUT_SLICE` is set. Translated as many as possible based on the available strings.
* | Merge pull request #8079 from albert-github/feature/issue_8078Dimitri van Heesch2020-10-121-1/+1
|\ \ | | | | | | issue #8078 Warning and extra text when using Markdown as mainpage
| * | issue #8078 Warning and extra text when using Markdown as mainpagealbert-github2020-10-061-1/+1
| | | | | | | | | | | | Also replace the `@` in a label.
* | | Merge pull request #8086 from albert-github/feature/bug_latex_footerDimitri van Heesch2020-10-121-13/+18
|\ \ \ | | | | | | | | Missing footer on first page of each chapter in LaTeX
| * | | Missing footer on first page of each chapter in LaTeXalbert-github2020-10-091-13/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In the doxygen pdf manual we see that on the first page of each chapter the footer is missing, the same occurs in the "normal" documentation generated by doxygen. References: - https://tex.stackexchange.com/questions/566034/footer-ruler-on-first-page-in-fancyhdr-with-book - https://tex.stackexchange.com/questions/566056/footer-ruler-on-first-page-in-fancyhdr-with-book-but-not-in-part-part/ Code changes ("normal" documentation): - latexgen.cpp changes required for the "normal" documentation Code changes (doxygen manual) - doxygen_manual.sty, remove word "Part" for the Appendices. - manual.sty changes like for "normal" documentation plus patching part in case of the `\part` (here we don't want the footer or header)
* | | | Merge pull request #8088 from albert-github/feature/bug_md_pg_atxDimitri van Heesch2020-10-121-0/+1
|\ \ \ \ | | | | | | | | | | Miscounting of lines in respect to page command (ATX header)
| * | | | Miscounting of lines in respect to page command (ATX header)albert-github2020-10-101-0/+1
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In case of an ATX header for a page at the beginning of a file (i.e. `#...`) there is a line miscounting. Analogous as done for lines type: ``` The page ==== ``` in pull request #8056 we have to add an extra newline.
* | | | Refactoring: Modernize BaseClassListDimitri van Heesch2020-10-1217-910/+714
| | | |
* | | | Fix type conversion warnings in searchindex.cppDimitri van Heesch2020-10-121-5/+5
| |_|/ |/| |
* | | Refactoring: Remove use of globals/statics in isAccessibleFrom*Dimitri van Heesch2020-10-114-114/+114
| | | | | | | | | | | | - Also moved AccessStack to util.h and modernized it.
* | | Spelling erroralbert-github2020-10-111-1/+1
| | | | | | | | | | | | Corrected another spelling error
* | | Spelling erroralbert-github2020-10-101-1/+1
| | | | | | | | | | | | | | | | | | Corrected spelling error (Found by Fossies).
* | | Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2020-10-102-2/+3
|\ \ \ | |/ /
| * | 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`.
* | Refactoring: Introduce ScopedTypeVariantDimitri van Heesch2020-10-103-437/+463
|/ | | | | | - Avoid creating new symbol definitions while generating syntax highlighted code. - Add some locking around shared data collection (search index & tooltips) to support concurrent processing - Unify some code that was duplicated in code.l and pycode.l
* 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.
generated by cgit v0.12 at 2024-11-16 20:25:33 (GMT)