summaryrefslogtreecommitdiffstats
path: root/src/commentscan.l
Commit message (Collapse)AuthorAgeFilesLines
* Enabled stricter compiler warnings and fixed all new warningsDimitri van Heesch2020-03-081-20/+25
|
* Restructure the way RefLists are handledDimitri van Heesch2020-02-271-31/+21
|
* Restructure section handlingDimitri van Heesch2020-02-211-27/+26
|
* Restructure citation handlingDimitri van Heesch2020-02-161-1/+1
|
* Improve formula handling and rendering.Dimitri van Heesch2020-02-121-15/+6
| | | | Also added option HTML_FORMULA_FORMAT to generate SVG files for images (requires pdf2svg)
* Fix 'converting to std::stack<GuardedSection> from initializer list would ↵Dimitri van Heesch2020-01-281-1/+1
| | | | use explicit constructor' issue on some versions of gcc.
* commentscan.l: replace QStack by std::stackDimitri van Heesch2020-01-271-47/+39
|
* Replace DocCmdMapper by std::mapDimitri van Heesch2020-01-271-209/+150
|
* Move DocGroup inside CommentScanner instead of using a globalDimitri van Heesch2020-01-261-12/+56
|
* Merge branch 'ifspacing'Dimitri van Heesch2020-01-261-0/+2
|\
| * Fix for removed spaces in certain \if \else \endif constructsDimitri van Heesch2020-01-071-0/+2
| |
* | Merge pull request #7498 from albert-github/feature/bug_rulesDimitri van Heesch2020-01-111-12/+0
|\ \ | | | | | | Remove unused rules
| * | Remove unused rulesalbert-github2020-01-091-12/+0
| |/ | | | | | | Remove some unused rules.
* | Adding commands `\rtfinclude`, `\docbookinclude`, `\maninclude` and ↵albert-github2020-01-091-0/+4
|/ | | | | | `\xmlinclude` Adding for consistency with `\*only`, `\htmlincclude` and `\latexinclude` the commands: `\rtfinclude`, `\docbookinclude`, `\maninclude` and `\xmlinclude`
* Make commentscan.l reentrantDimitri van Heesch2019-12-301-1324/+1441
|
* Replaced \_fakeform by \_formDimitri van Heesch2019-12-261-2/+2
|
* Merge branch 'feature/bug_formula' of ↵Dimitri van Heesch2019-12-261-2/+2
|\ | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_formula
| * Better warning in case of `@form`albert-github2019-11-061-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When having a problem like: ``` /** \file */ /** * The fie * * @form: the new format * @content: the content of the form * * Sets @form content to be @content. * * \f$ \alpha \f$ \f[ \beta \f] */ void fie(char *form, char *content); ``` we get warnings like: ``` .../aa.h:5: warning: Wrong formula id -1 .../aa.h:6: warning: Found unknown command '\content' .../aa.h:8: warning: Wrong formula id -1 .../aa.h:8: warning: Found unknown command '\content' ``` The `@form:` is in RST analogue to the doxygen `@param form` but not understood by doxygen. The result is that it is seen as an formula as doxygen translates the formula commands to `\form`. For `@content` is handled properly as this is not a doxygen command. In this patch a more unique name is chosen so these type of conflicts don't appear (that easy). The resulting, better, warnings are now: ``` .../aa.h:5: warning: Found unknown command '\form' .../aa.h:6: warning: Found unknown command '\content' .../aa.h:8: warning: Found unknown command '\form' .../aa.h:8: warning: Found unknown command '\content' ```
* | Removed exitCode parameter as it is always 1Dimitri van Heesch2019-12-221-1/+1
| |
* | Merge branch 'feature/bug_terminate' of ↵Dimitri van Heesch2019-12-221-2/+1
|\ \ | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_terminate
| * | Better termination messagealbert-github2019-11-221-2/+1
| | | | | | | | | | | | | | | In case a `WARN_LOGFILE` is used it in this file no clear whether doxygen finished correctly or exited beforehand in case a fatal error. Now a 'Exiting...' is also given in the warning log file in case an error is a fatal error.
* | | Split language parser into "outline parser" and "code parser"Dimitri van Heesch2019-12-031-2/+2
|/ /
* | Remove bogus flex codeDimitri van Heesch2019-11-181-9/+0
| |
* | Spelling corrections for src directoryalbert-github2019-11-051-1/+1
|/ | | | | | | | Spelling corrections as found by codespell and in #561. Some reported problems were already fixed, others are fixed here, with some exceptions (a,o.): - "referenceby" in defgen.cpp as this is in the output and I cannot oversee the consequences (looks like none, but ...) - "HANGEUL_CHARSET" left as is as in some MS documentation is written: 'HANGUL_CHARSET: Also spelled "Hangeul". Specifies the Hangul Korean character set.' (https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-wmf/0d0b32ac-a836-4bd2-a112-b6000a1b4fc9).
* Replaced QList<ListItemInfo> with std::vector<ListItemInfo>Dimitri van Heesch2019-10-291-9/+6
|
* Replaced QList<SectionInfo> by std::vector<SectionInfo>Dimitri van Heesch2019-10-291-3/+3
|
* Replaced QList<Grouping> with std::vector<Grouping>Dimitri van Heesch2019-10-291-2/+2
|
* Replaced QList<BaseInfo> with std::vector<BaseInfo>Dimitri van Heesch2019-10-291-5/+5
|
* Merge branch 'std'Dimitri van Heesch2019-10-071-11/+7
|\
| * Use smartpointers to manage the lifetime of Entry objectsDimitri van Heesch2019-10-071-11/+7
| |
* | issue #7274 Subpages no longer possible under mainpagealbert-github2019-09-271-1/+1
|/ | | | Regression on #7050 / #7053 (Physical newlines (^^) not working in group names and without spaces in 1.8.15), in case the current name was explicitly set to mainpage it was still overwritten.
* Reduce the use of QString in favor of the more efficient QCStringDimitri van Heesch2019-09-211-2/+2
|
* Merge pull request #7264 from albert-github/feature/bug_164073Dimitri van Heesch2019-09-161-0/+17
|\ | | | | Bug 164073 - There should be a dummy tag that Doxygen ignores
| * Bug 164073 - There should be a dummy tag that Doxygen ignoresalbert-github2019-09-151-0/+17
| | | | | | | | Introduced the `\noop` command to ignore text till end of the line.
| * issue #6715: Errorneous matching of the immediately following block command ↵Dimitri van Heesch2019-09-071-5/+0
| | | | | | | | after @ref (try 2)
| * issue #6715: Errorneous matching of the immediately following block command ↵Dimitri van Heesch2019-09-071-0/+5
| | | | | | | | after @ref
* | Consistent way to show scanner statealbert-github2019-09-051-0/+3
|/ | | | | Create a consistent way to display the state mnemonics of the different scanners (analogous to the fortranscanner.l) Use an automatic procedure to generate the routine with the translation of the states to a string.
* Merge branch 'feature/bug_endblock_msg' of ↵Dimitri van Heesch2019-08-041-2/+2
|\ | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_endblock_msg
| * Correction warning messagealbert-github2019-06-011-2/+2
| | | | | | | | Consistency
* | Minor code simplificationsDimitri van Heesch2019-08-041-3/+8
| |
* | Merge branch 'feature/bug_doc_cont' of ↵Dimitri van Heesch2019-08-041-0/+3
|\ \ | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_doc_cont
| * | Incorrect joining documentation sections.albert-github2019-07-071-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In case we have a documentation block that is interrupted the following part is directly appended to it without an appropriate newline and results, in this case, in messages like: ``` aa.c:13: warning: Illegal command @verbatim as part of a title section aa.c:15: warning: unexpected command endverbatim bb.f:13: warning: Illegal command @verbatim as part of a title section bb.f:15: warning: unexpected command endverbatim ``` We need a solution at 2 places due to the reset of of `OutputBrief` to `OutputDoc` in `setOutput` The original problem results from the "The R Project for Statistical Computing" version 3.6.1 in the Fortran part.
* | | Regression: unbalanced grouping commandsalbert-github2019-08-021-1/+1
| | | | | | | | | | | | | | | | | | Regression on #7122 (and #7115 / #7116). When having multiple consecutive `\name` sections the warning "unbalanced grouping commands" appears Analogous to the open command also the close command needs an implicit argument.
* | | Merge branch 'feature/regr_7105_2' of ↵Dimitri van Heesch2019-07-301-1/+1
|\ \ \ | | | | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/regr_7105_2
| * | | regression #7105 Correct counting in case of `\name`albert-github2019-07-121-0/+1
| |/ / | | | | | | | | | In case of the `\name` command it is possible that a group is opened, but this group is not closed (for the `\name`), so the counting should not increase.
* | | Merge branch 'feature/regr_7105' of https://github.com/albert-github/doxygen ↵Dimitri van Heesch2019-07-301-1/+0
|\ \ \ | | | | | | | | | | | | into albert-github-feature/regr_7105
| * | | regression #7105 correct counting for group close countingalbert-github2019-07-101-0/+1
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In case of an extra closing we should not count this closing as otherwise sequences like: ``` @} ... @{ ... @} ``` will give a warning at both `@}` statements and not just at the first (second one has an opening statement_.
* | | Merge pull request #7026 from albert-github/feature/bug_end_comment_code_sectionDimitri van Heesch2019-07-291-6/+9
|\ \ \ | | | | | | | | End comment marker in \code section.
| * | | End comment marker in \code section.albert-github2019-06-041-6/+9
| | |/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | When we have an end comment in a `\code` segment in a section we can get a message like: ``` warning: found */ without matching /* while inside a \code block! Perhaps a missing \endcode? ``` in the similar situation in a `\verbatim` section this message is not given. Switching from `\code` to `\verbatim` is not an option here as in that case other "commands" can lead to problems like in a code like `$string =~ s/^\s*//;` In this patch the start `/*` and end `*/` comment markers for `\code` and `\verbatim` are completely ignored.
* | | take doc group out of commentscan.lAdrian Negreanu2019-07-261-216/+12
| |/ |/| | | | | Signed-off-by: Adrian Negreanu <groleo@gmail.com>