summaryrefslogtreecommitdiffstats
path: root/src/scanner.l
Commit message (Collapse)AuthorAgeFilesLines
* 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
|/
* 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.
* issue #7243: Some PHP classes are not properly extracted/documentedDimitri van Heesch2019-09-021-7/+6
|
* Merge branch 'feature/bug_endblock_msg' of ↵Dimitri van Heesch2019-08-041-16/+16
|\ | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_endblock_msg
| * Correction warning messagealbert-github2019-06-011-15/+15
| | | | | | | | Consistency
| * Correction warning messagealbert-github2019-06-011-1/+1
| | | | | | | | | | | | | | | | | | | | When there is a problem with a backticjk comment block we can get the message: reached end of file while inside a ````' block! this is a bit unreadable / non understandable as we see see 4 backticks followed by a single quote, it woulb be more readable when we get reached end of file while inside a '```' block!
* | Merge pull request #7097 from albert-github/featre/bug_437181Dimitri van Heesch2019-08-041-1/+1
|\ \ | | | | | | Bug 437181 - The -d Preprocessor option doesn't work for php, should be in the doc.
| * | Bug 437181 - The -d Preprocessor option doesn't work for php, should be in ↵albert-github2019-07-021-1/+1
| | | | | | | | | | | | | | | | | | | | | the doc. - excluded `.php5` files from preprocessing (like other php files) - made remark about some limits in files that are preprocessed in documentation
* | | issue 7068: "QGDict::hashAsciiKey: Invalid null key" error messages (part 3)Dimitri van Heesch2019-08-011-2/+2
| | |
* | | issue 7068: "QGDict::hashAsciiKey: Invalid null key" error messages (part 2)Dimitri van Heesch2019-07-311-8/+16
| | |
* | | issue 7068: "QGDict::hashAsciiKey: Invalid null key" error messagesDimitri van Heesch2019-07-301-3/+6
| | |
* | | Merge pull request #7116 from albert-github/feature/bug_comment_recognitionDimitri van Heesch2019-07-301-2/+2
|\ \ \ | | | | | | | | Problem with with comment recognition for group open and closing commands
| * | | Problem with with comment recognition for group open and closing commandsalbert-github2019-07-101-2/+2
| |/ / | | | | | | | | | | | | Besides the wanted start of comments `//!`, `///`, `/*!` and `/**` also the "normal" comments `//` and `/*` were recognized as starting a comment for the group open (`\{`, `@{`) and group closing (`\}`, `@}`) commands. This was due to the usage of `?` in the regular expression meaning 0 or 1 times.
* | | take doc group out of commentscan.lAdrian Negreanu2019-07-261-8/+8
|/ / | | | | | | Signed-off-by: Adrian Negreanu <groleo@gmail.com>
* | Fixes #6860.Austin Henriksen2019-06-121-0/+29
| |
* | Bug 535853 - C# consts incorrectly placed under instance variablesalbert-github2019-06-101-0/+4
|/ | | | Handle consts separately and in case of CSharp set the static flag.
* Merge pull request #6957 from ↵Dimitri van Heesch2019-05-211-0/+37
|\ | | | | | | | | cfriedt/feature/cfriedt/6955/allow-javadoc-style-comment-blocks-with-a-doxyfile-variable Allow Javadoc-style comment blocks with a Doxyfile variable
| * Allow Javadoc-style comment blocks with a Doxyfile variableChristopher Friedt2019-05-031-0/+37
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Javadoc allows comments like this (which I refer to as "banner" comments) /***************** * *****************/ but doxygen does not recognize them. Instead, the doxygen manual says to do this /*************//** * ****************/ which some users aren't even aware is required. It also behaves poorly with clang-format. I'm proposing to add a Doxyfile boolean option JAVADOC_BANNER which will default to NO. When set to YES, it will consider the first and second comments above to be equivalent. However, I don't believe that the JAVADOC_BANNER option should default to YES, as there are likely a number of projects who have used the former syntax with full expectation that it would *not* appear in their documentation. At least having the JAVADOC_BANNER default to NO allows users to opt-in voluntarily by adding JAVADOC_BANNER = YES to their Doxyfile. If the consensus is to make it a default at a later time, first a warning can be added during build that should trigger users to modify their comment style, and then eventually the default could be set to JAVADOC_BANNER = YES, or the config option could be removed entirely and it would just always be enabled.
* | Fixed C++17-namespace assignment bugMatthew Hatch2019-05-091-0/+2
|/ | | | Added scope save and restore before and after namespace parsing
* Improved const correctness and added support for inline namespacesDimitri van Heesch2019-04-211-2/+2
|
* Email address not seenalbert-github2019-04-191-3/+3
| | | | | | In case of an email address like abc@code-factory.org we get the message like: warning: reached end of file while inside a code block! due to the fact that the email address contains a '-'.
* Bug 322353 - C variable argument list doesn't work in @paramalbert-github2019-02-191-0/+1
| | | | The `...` argument was not documented in case of inline parameter documentation, with `\param` it was possible to document the `...` argument.
* Merge branch 'feature/bug_136299' of ↵Dimitri van Heesch2019-02-171-1/+1
|\ | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_136299
| * Bug 136299 - attributes to <p> tag get lostalbert-github2019-02-041-1/+1
| | | | | | | | | | | | | | | | | | | | | | Besides the `p` tag there were a number of other tags were also the attributes were lost: - `br` - `hr` - `a` in case of used as an anchor i.e. with the `name=` attribute In case of a `caption` with a `table` and no `id=` attribute with the `caption` there was still an anchor generated In scanner.l the warnings message was a bit unclear.
* | Issue #6818 Certain regex pattern in class constant causes PHP class to be ↵albert-github2019-02-061-1/+2
| | | | | | | | | | | | ignored In case of Cpp we also have to consider the case of strings that can contain the `[[...]]` part.
* | Issue #6818 Certain regex pattern in class constant causes PHP class to be ↵albert-github2019-02-051-0/+1
|/ | | | | | | ignored Only ally the rule `<*>"[["` for Cpp See also fix d8001efd89146e04d92f5ea41ab27a7de09b6c53 i.e. Problem parsing c++ gnu::visibility (Origin: bugzilla #787952) #6259
* Problem with just an asterisks on a `\code` linealbert-github2019-02-021-1/+1
| | | | | Problem occurs when a line with just a `*` is followed by another line with an `# and some comment. The test on newline has been removed. Problem is most likely a consequence of Bug #5288 - Asterisks in comment wrongly displayed for @code, i.e. 23f337e64b95d3fa08f32980c866669b190c872f
* issue #6796 Bad link to section, subsection if pointing at item past ↵albert-github2019-01-261-1/+1
| | | | | | suspicious text To escape `\` and `@` not only `\\` and `@@` should be possible but also `\@` and `@\`
* Added 'constexpr' as attribute label and to XML outputDimitri van Heesch2019-01-131-0/+12
|
* issue #6748 1.8.15 regression with C# internal modifieralbert-github2019-01-081-0/+4
| | | | In the fix for issue #677 / bug 743539 only the Java part, in scanner.l, should have been removed and not the other languages in respect to the word "internal", compare also code.l
* issue #6734 parsing performance worsenedDimitri van Heesch2019-01-071-7/+8
|
* Fixed differently by changing root cause for introducing the spaceDimitri van Heesch2018-11-241-1/+1
|
* Minor restructuringDimitri van Heesch2018-11-181-37/+37
|
* Fix scanner.l for SliceJoe George2018-11-021-2/+2
|
generated by cgit v0.12 at 2024-10-30 19:46:16 (GMT)