summaryrefslogtreecommitdiffstats
path: root/src/scanner.l
Commit message (Collapse)AuthorAgeFilesLines
* issue #7635: Incorrect location for enum in XML fileDimitri van Heesch2020-03-141-6/+54
|
* Enabled stricter compiler warnings and fixed all new warningsDimitri van Heesch2020-03-081-5/+10
|
* Incorrect handling of typedef in combination with constalbert-github2020-02-251-3/+10
| | | | | | | | | | | | | | | | | | | | | I issue #7060 and example was given with ``` typedef const char m_msgEvtName; ``` we see that - 1.8.15, listed under Typedefs: ` typedef const char m_msgEvtName` - 1.8.16 and up, listed under Variables: `const typedef char m_msgEvtName` so mentioned: - wrong "header" - const at the wrong place This is a regression on: C# consts incorrectly placed under instance variables (Origin: bugzilla #535853) (issue #2976) and the pull request #7048 The fix should only be used for C#
* issue #6319: C++ function returning std::function with reference argument is ↵Dimitri van Heesch2020-02-171-15/+16
| | | | not recognized as a function (Origin: bugzilla #792830)
* Fix compiler warnings on Windows (Visual Studio)Dimitri van Heesch2020-02-121-0/+3
|
* issue #7508: TYPEDEF_HIDES_STRUCT stopped working properlyDimitri van Heesch2020-01-281-5/+3
|
* Move DocGroup inside CommentScanner instead of using a globalDimitri van Heesch2020-01-261-8/+8
|
* Cleanup unused/unwanted parser dependencies on code generatorDimitri van Heesch2020-01-261-1/+0
|
* Merge pull request #7497 from albert-github/feature/bug_consistency_onlyDimitri van Heesch2020-01-111-4/+4
|\ | | | | Consistency `\*only` and `\end*only` commands
| * Consistency `\*only` and `\end*only` commandsalbert-github2020-01-091-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Not all possibilities in respect of `\*only` and `\end*only` commands were present which could lead to messages like: ``` .../aa.h:4: warning: reached end of comment while inside a \rtfonly block; check for missing \endrtfonly tag! ../.aa.h:4: warning: rtfonly section ended without end marker .../aa.h:4: warning: rtfonly section ended without end marker ``` in case of a problem like: ``` /** \file * \rtfonly * RTF /* Nested */ * \endrtfonly */ ```
* | issue #7472: Serious regression: /**< comments cause functions to be ↵Dimitri van Heesch2020-01-091-5/+3
|/ | | | silently ignored
* Make commentscan.l reentrantDimitri van Heesch2019-12-301-3/+5
|
* Merge branch 'master' into feature/bug_fenced_codeDimitri van Heesch2019-12-261-3498/+3428
|\
| * issue #7446: C#: parameter named `extends` is broken in the documentationDimitri van Heesch2019-12-201-4/+4
| |
| * Incorrect warning "yyextra->inside" instead of "inside"albert-github2019-12-181-2/+2
| | | | | | | | | | | | | | | | | | | | We get warnings like: ``` warning: reached end of file while yyextra->inside a 'code' block! warning: Ignoring \brief command yyextra->inside argument documentation ``` this is due to the fact that the scanner has been made reentrant (inside becomes yyextra->inside and this slipped into the warning strings as well)
| * issue #7412: HTML: Opening a reference link in a new tab does not scroll to ↵Dimitri van Heesch2019-12-101-2/+5
| | | | | | | | the content
| * Merge branch 'master' into feature/bug_coverity_unintDimitri van Heesch2019-12-081-85/+58
| |\
| | * Changed std::unique_ptr<Entry> to std::shared_ptr<Entry> at avoid use after ↵Dimitri van Heesch2019-12-081-45/+46
| | | | | | | | | | | | free issues
| | * Added missing debug flags for scanner that were made reentrantDimitri van Heesch2019-12-051-0/+3
| | |
| | * Split language parser into "outline parser" and "code parser"Dimitri van Heesch2019-12-031-40/+9
| | |
| * | Coverity uninitializedalbert-github2019-12-021-1/+1
| |/ | | | | | | Fixing a number of uninitialized variables based on the coverity output of November 30, 2019
| * Made scanner.l reentrantDimitri van Heesch2019-12-011-3329/+3371
| |
| * Fixed line count misaligned introduced with JAVADOC_BANNERDimitri van Heesch2019-11-241-36/+38
| |
| * Cleanup scanner.l code and namingDimitri van Heesch2019-11-241-2756/+2723
| |
| * Made code.l scanner reentrantDimitri van Heesch2019-11-211-2/+5
| |
| * Remove bogus flex codeDimitri van Heesch2019-11-181-7/+0
| |
| * Fix line count after multiline close groupRoel Standaert2019-11-121-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | Fix for issue #7393 When closing a group on multiple lines, like: /*! @} */ The line count of subsequent lines is wrong (it's one line less than it should be).
| * Simplied the logic for moving documentation to the most nested EntryDimitri van Heesch2019-11-101-23/+21
| |
| * Merge branch 'feature/issue_7295' of ↵Dimitri van Heesch2019-11-101-0/+17
| |\ | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/issue_7295
| | * issue #7295 Doxygen documentation of C++17 nested namespace erroneousalbert-github2019-10-061-0/+17
| | | | | | | | | | | | documentation has to be added to the "last" entry not to the "first" / "top"
| * | Fixed use of uninitialized pointer in preprocessorDimitri van Heesch2019-11-091-1/+1
| | |
| * | 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).
| * | Merge pull request #7364 from albert-github/feature/issue_7358Dimitri van Heesch2019-11-021-1/+1
| |\ \ | | | | | | | | issue #7358: Ternary conditional and null-coalescing operator in constructor results in faulty warning
| | * | issue #7358: Ternary conditional and null-coalescing operator in constructor ↵albert-github2019-10-301-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | results in faulty warning Problem due to the implementation of "Support for C# nullable types (Origin: bugzilla #638606)" (issue #4064, pull request #645). The used condition was a bit to stringent so later on the function was not recognized as constructor.
| * | | Replaced QList<ListItemInfo> with std::vector<ListItemInfo>Dimitri van Heesch2019-10-291-18/+4
| | | |
| * | | Replaced QList<Grouping> with std::vector<Grouping>Dimitri van Heesch2019-10-291-60/+4
| | | |
| * | | Replaced QList<BaseInfo> with std::vector<BaseInfo>Dimitri van Heesch2019-10-291-6/+6
| |/ /
* | | Length of identifying fenced code blockalbert-github2019-10-291-8/+12
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In case we have a problem like: ``` /** \file * ``` * router = (new Router()); * ``` */ ``` there is no problem, but as soon as we add a space somewhere before the start or end identifier of the fenced code block we get: ``` .../aa.h:6: warning: reached end of file while inside a '```' block! The command that should end the block seems to be missing! ``` i.e. a problem like: ``` /** \file * ``` * router = (new Router()); * ``` */ ``` or ``` /** \file * ``` * router = (new Router()); * ``` */ ``` The relevant length is the length identifying the fenced code block / number of back ticks, not the number of spaces in front of it (analogous number of tildes).
* | Changed ArgumentList to be an STL containerDimitri van Heesch2019-10-271-143/+114
| |
* | Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2019-10-131-2/+17
|\ \
| * \ Merge pull request #7297 from albert-github/feature/bug_572798Dimitri van Heesch2019-10-091-1/+1
| |\ \ | | | | | | | | Bug 570798 - \\\< does not work for php constants
| | * | Bug 570798 - \\\< does not work for php constantsalbert-github2019-10-061-1/+1
| | |/ | | | | | | | | | Handle comment for define analogous to a normal php variable, the closing part is automatically done when the comment is finished (rule: `<DefinePHPEnd>";"`).
| * | Merge pull request #7303 from albert-github/feature/issue_7302Dimitri van Heesch2019-10-091-0/+15
| |\ \ | | | | | | | | issue 7302: Parsing of template args in single-quotes is incorrect.
| | * | issue 7302: Parsing of template args in single-quotes is incorrect.albert-github2019-10-081-0/+15
| | | | | | | | | | | | | | | | | | | | In case we encounter an unescaped single or double quote during specialization we search for the closing quote. We are cionnsidering potential escape sequences in the strings as well.
| * | | Merge pull request #7283 from luzpaz/typosDimitri van Heesch2019-10-091-1/+1
| |\ \ \ | | |/ / | |/| | Fix typos
| | * | Fix typosluz.paz2019-09-281-1/+1
| | |/ | | | | | | | | | | | | | | | Found via ``` codespell -q 3 -S *.js,*.po,./src/translator*,*.eps,./doc/changelog.doc -L ang,ans,attribs,ba,behaviour,classe,colour,german,iff,initialise,nam,nd,que,russian,statics,te,tim,uint ```
* | | Fix lifetime issue for Entry objects.Dimitri van Heesch2019-10-131-2/+2
|/ /
* | Use smartpointers to manage the lifetime of Entry objectsDimitri van Heesch2019-10-071-171/+146
|/
* issue #7265: Double quote character in C++ raw string literal causes Doxygen ↵Dimitri van Heesch2019-09-241-0/+11
| | | | to process the string contents
* Consistent way to show scanner statealbert-github2019-09-051-0/+2
| | | | | 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.
generated by cgit v0.12 at 2024-08-21 03:34:03 (GMT)