summaryrefslogtreecommitdiffstats
path: root/src/scanner.l
Commit message (Collapse)AuthorAgeFilesLines
* 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
|
* Merge remote-tracking branch 'doxygen/master'Joe George2018-11-021-4/+4
|\
| * Merge pull request #6561 from ↵Dimitri van Heesch2018-10-271-4/+0
| |\ | | | | | | | | | | | | albert-github/feature/bug_scanner_obsolete_definitions Remove obsolete definitions from scanner
| | * Remove obsolete definitions from scanneralbert-github2018-10-171-4/+0
| | | | | | | | | | | | Remove some not used definitions from scanner.l (give false positives when searching for some features).
| * | Merge pull request #6536 from albert-github/feature/bug_677092Dimitri van Heesch2018-10-271-0/+4
| |\ \ | | | | | | | | Bug 677092 - single quote in HTML section of PHP breaks doxygen
| | * | Bug 677092 - single quote in HTML section of PHP breaks doxygenalbert-github2018-10-031-0/+4
| | |/ | | | | | | | | | | | | | | | | | | | | | Close string also when entering a new php (`<?php`) block Also solves: Bug 695337 - Inline HTML containing a single apostrophe (') appears to interfere with Doxygen parsing. Bug 156160 - Doesn't support quotes in HTML code embedded into a PHP script
* | | Added *.ice files as a recognized file type.Mark Spruiell2018-10-221-29/+174
|/ / | | | | | | Added a Slice-optimized output mode.
* | Bug 749049 - Doxygen not creating call graphs for C# methods if namespace ↵albert-github2018-10-201-0/+22
|/ | | | | | | | | | | | | | | | | contains the classname Problem is the '.' in the namespace name. For Csharp: namespace N1.n2 { is equivalent to namespace N1 { namespace N2 { This splitting has to be considered in the scanner so the different namespaces are mentioned. In the code.l the '.' was not handled.
* Merge pull request #717 from albert-github/feature/bug_769414Dimitri van Heesch2018-07-171-0/+60
|\ | | | | Bug 769414 - PHP: New array syntax not supported when parsing initial value
| * Bug 769414 - PHP: New array syntax not supported when parsing initial valuealbert-github2018-05-101-0/+60
| | | | | | | | Implemented possibility string initializations by means of '[' ... ']' construct (besides the already existing 'array(' ... ')'.
* | Update scanner.lArmin Müller2018-06-191-3/+3
|/
* Fixed compiler warning for nested /* in scanner.lDimitri van Heesch2018-05-011-2/+2
|
* Merge branch 'master' into feature/bug_743539Dimitri van Heesch2018-04-221-1/+4
|\
| * Bug 683564 - Value from enumeration followed with semicolon is not present ↵albert-github2018-02-141-1/+4
| | | | | | | | | | | | in java docs For java the type should not be reset to "@", see also rule <FindFields>","
* | Bug 743539 - Field with name "internal" confuses documentation builder.albert-github2018-03-061-4/+0
|/ | | | internal is not a Java reserved word / keyword but was handled as such.
* Merge pull request #645 from albert-github/feature/bug_638606Dimitri van Heesch2018-02-101-0/+16
|\ | | | | Bug 638606 - Support for C# nullable type
| * Bug 638606 - Support for C# nullable typealbert-github2018-02-011-0/+16
| | | | | | | | Added, basic, support for C# nullable types.
* | Bug 793052 - C#: Incorrect parsing of property definitions containing "//" ↵albert-github2018-01-311-1/+8
|/ | | | | | symbols in one line with "} The handling of comment signs inside a string for property definitions has been corrected, by defining parsing rules for these cases so that not the default comment handler will be used (i.e. remove the part behind the comment sign).
* Bug 790788 - Doxygen not showing the public, non-static member functionDimitri van Heesch2017-12-251-0/+5
|
* Bug 787952 - Problem parsing c++ gnu::visibilityDimitri van Heesch2017-11-091-1/+1
|
generated by cgit v0.12 at 2024-08-23 05:18:23 (GMT)