summaryrefslogtreecommitdiffstats
path: root/src/pre.l
Commit message (Collapse)AuthorAgeFilesLines
* issue #7265: Double quote character in C++ raw string literal causes Doxygen ↵Dimitri van Heesch2019-09-241-0/+25
| | | | to process the string contents
* 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-28/+28
|\ | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_endblock_msg
| * Correction warning messagealbert-github2019-06-011-28/+28
| | | | | | | | Consistency
* | Allow \r\n as line continuation as wellDimitri van Heesch2019-08-041-1/+1
| |
* | warning: More #endif's than #if's found.albert-github2019-08-021-0/+2
| | | | | | | | In case in a macro substitution string the last character was a backslash this was, incorrect, not seen as a sign for a line continuation.
* | issue #7104 Warning with preprocessoralbert-github2019-07-051-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The test on 'defined' has to be done earlier as otherwise the replacement (limited to 2 defined is enough for the test) of ``` (defined(__AVR_ATmega644RFR2__)||defined(__AVR_ATmega256RFR2__)) ``` will be ``` ` ! (defined( 0 )||0( 0 )) ' ``` instead of ``` ` ! (defined( 0 )||defined( 0 )) ' ```
* | issue #7021 Warning about missing item in INCLUDE_PATHalbert-github2019-06-021-1/+5
|/ | | | Do the `curlyCount` per file and not globally.
* Warning when preprocessing conditionalsalbert-github2019-04-241-0/+1
| | | | | | | | | | | | | | In case in a `#if` statement a space in the use of a macro is present a warning of the type: warning: preprocessing issue while doing constant expression evaluation: syntax error is given. Removing the white space after an ID solves the issue In the following the first expressing gives a warning whilst the second expression doesn't: #if (!__GNUC_PREREQ (4, 6)) int i0; #endif #if (!__GNUC_PREREQ(4, 6)) int k0; #endif
* Revert "issue #6856 Doxygen only expands macro defined in header file once ↵Dimitri van Heesch2019-03-281-2/+5
| | | | when referred multiple times"
* Merge pull request #6859 from albert-github/feature/issue_6856Dimitri van Heesch2019-03-201-5/+2
|\ | | | | issue #6856 Doxygen only expands macro defined in header file once when referred multiple times
| * issue #6856 Doxygen only expands macro defined in header file once when ↵albert-github2019-02-251-5/+2
| | | | | | | | | | | | referred multiple times In case the include file is already is already in the global stack it should not be added to the global stack, but still be handled for the current file
* | Removed unneeded checkDimitri van Heesch2019-03-171-1/+1
| |
* | at sign (`@`) not handled correctly in preprocessor (more fixes)Dimitri van Heesch2019-03-171-34/+40
| |
* | Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2019-03-161-1/+15
|\ \
| * \ Merge pull request #6772 from albert-github/feature/issue_6764Dimitri van Heesch2019-03-101-1/+15
| |\ \ | | | | | | | | issue #6764 Incorrect parsing of C enum comments defined using a macro
| | * | issue #6764 Incorrect parsing of C enum comments defined using a macroalbert-github2019-01-151-1/+15
| | |/ | | | | | | | | | When in a `/*` comment skip till end of the comment so a `,` won't be seen as the argument separator.
* | | at sign (`@`) not handled correctly in preprocessorDimitri van Heesch2019-03-161-0/+15
|/ /
* | Refactored Definition and derived classes such that they are abstract interfacesDimitri van Heesch2019-02-281-1/+1
|/
* Added *.ice files as a recognized file type.Mark Spruiell2018-10-221-1/+1
| | | | Added a Slice-optimized output mode.
* Merge pull request #778 from albert-github/feature/565713Dimitri van Heesch2018-07-241-0/+1
|\ | | | | Bug 565713 - Fortran: Does not recognize backslash at end of documentation line
| * Bug 565713 - Fortran: Does not recognize backslash at end of documentation linealbert-github2018-06-271-0/+1
| | | | | | | | Don't remove the end backslash in case of Fortran
* | Merge pull request #770 from albert-github/feature/bug_630931Dimitri van Heesch2018-07-231-1/+10
|\ \ | | | | | | Bug 630931 - \cond after @string literal containing backslash fails in C#
| * | Bug 630931 - \cond after @string literal containing backslash fails in C#albert-github2018-06-181-1/+10
| |/ | | | | | | Special handling in preprocessor for CSharp literal strings (i.e. strings starting with @).
* | Bug 796621 - @cond does not stop at @endcond Fortranalbert-github2018-06-191-3/+21
|/ | | | | The backslash (\) is in Fortran not an escape character but was handled as such, this has been corrected. Handling of the different Fortran string types ('...' and "...") made more consistent.
* Problem with \cond in normal comment of test 015albert-github2018-05-071-1/+1
| | | | | | | | In the \cond is also recognized in non-doxygen comment. - As a work around the \ has been removed - in case of e.g. pdf the enabled function is not shown as it does not have a doxygen comment - test file output update due to change in input code. - pre.l and commentcnv.l. better error message i.e. showing better the used condition
* Merge pull request #589 from albert-github/feature/bug_786409Dimitri van Heesch2017-09-021-0/+11
|\ | | | | Bug 786409 - parsing error in Fortran file with preprocessing
| * Bug 786409 - parsing error in Fortran file with preprocessingalbert-github2017-08-171-0/+11
| | | | | | | | Problem with ' (single quote) in Fortran. A string in Fortran can be between single or double quotes.
* | Bug 786409 - parsing error in Fortran file with preprocessingalbert-github2017-08-181-1/+1
|/ | | | the // is in Fortran the indication for string concatenation and not for comment and should thus be ignored during, Fortran, preprocessing
* Merge pull request #560 from luzpaz/typosDimitri van Heesch2017-04-021-1/+1
|\ | | | | typos
| * typosKunda2017-03-051-1/+1
| | | | | | | | | | | | some doxy typos and some misc. source typos typos some doxy typos and some misc. source typos
* | line continuation characters inside comments embedded in a macro definition ↵Dimitri van Heesch2017-04-021-3/+10
|/ | | | appeared in the output
* flex: use %option instead of command line options.Adrian Negreanu2016-09-211-0/+2
|
* FORTRAN determination string in preprocessingalbert-github2016-08-281-0/+16
| | | | In FORTRAN a string can start (and end) either with a double quote or a single quote. The later was not considered in the preprocessing resulting in unwanted substitutions in strings.
* Changed configuration mechanism to directly access options in order to ↵Dimitri van Heesch2016-01-171-9/+9
| | | | improve performance
* Fixed a couple of small memory leaksDimitri van Heesch2015-11-141-2/+4
|
* drop #include <unistd.h>Adrian Negreanu2015-05-151-3/+3
| | | | Signed-off-by: Adrian Negreanu <adrian.m.negreanu@intel.com>
* Guarded debug prints against printing a NULL pointer.Dimitri van Heesch2015-04-061-3/+3
|
* Added documentation for ``` style fenced code block and more robust parsingDimitri van Heesch2015-04-051-5/+5
|
* fix *.l for three backtickshalex20052015-03-301-2/+2
|
* add support for github flavored fenced code blockshalex20052015-03-301-0/+20
|
* Bump copyright yearDimitri van Heesch2015-02-261-1/+1
|
* Fixed several Coverity warningsDimitri van Heesch2014-11-151-2/+2
|
* Avoid a (theoretical) memory leakDimitri van Heesch2014-10-231-3/+3
|
* Fixed a number of issues (resource leaks, uninitialized members, etc) found ↵Dimitri van Heesch2014-08-311-0/+3
| | | | by coverity
* Bug 735037 - QGDict::hashAsciiKey: Invalid null keyDimitri van Heesch2014-08-211-2/+9
|
* Bug 731985 - Variadic macros failing to expand if trailing ... is emptyDimitri van Heesch2014-06-241-2/+3
|
* Updated copyrightDimitri van Heesch2014-02-111-1/+1
|
* Debug output for lexical analyzerAlbert2013-11-131-0/+2
| | | | | | | | | | | | | | In case of error messages like: input buffer overflow, can't enlarge buffer because scanner uses REJECT it is not always directly clear from which lexical analyzer (.l file) this problem comes. This patch helps to find these problems and does the following things: - when using the option -d lex with doxygen each time a lexical analyzer is called at the start a line like the following line will be given: Entering lexical analyzer: pre.l (for: ..../file.c) and at the end: Finished lexical analyzer: pre.l (for: ..../file.c) - in case the lexical analyzer has been translated with the -d option of lex / flex the above mentioned lines will be given as part of the lexical analyzer output (to stderr) and look like: --entering lexical analyzer: pre.l (for: ..../file.c) --finished lexical analyzer: pre.l (for: ..../file.c)
* Bug 711639 - [PATCH] #include does not work with absolute pathsDimitri van Heesch2013-11-111-0/+14
|
generated by cgit v0.12 at 2024-10-31 20:37:42 (GMT)