| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
to process the string contents
|
|
|
|
|
| |
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.
|
|\
| |
| |
| | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_endblock_msg
|
| |
| |
| |
| | |
Consistency
|
| | |
|
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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 )) '
```
|
|/
|
|
| |
Do the `curlyCount` per file and not globally.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
when referred multiple times"
|
|\
| |
| | |
issue #6856 Doxygen only expands macro defined in header file once when referred multiple times
|
| |
| |
| |
| |
| |
| | |
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
|
| | |
|
| | |
|
|\ \ |
|
| |\ \
| | | |
| | | | |
issue #6764 Incorrect parsing of C enum comments defined using a macro
|
| | |/
| | |
| | |
| | | |
When in a `/*` comment skip till end of the comment so a `,` won't be seen as the argument separator.
|
|/ / |
|
|/ |
|
|
|
|
| |
Added a Slice-optimized output mode.
|
|\
| |
| | |
Bug 565713 - Fortran: Does not recognize backslash at end of documentation line
|
| |
| |
| |
| | |
Don't remove the end backslash in case of Fortran
|
|\ \
| | |
| | | |
Bug 630931 - \cond after @string literal containing backslash fails in C#
|
| |/
| |
| |
| | |
Special handling in preprocessor for CSharp literal strings (i.e. strings starting with @).
|
|/
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
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
|
|\
| |
| | |
Bug 786409 - parsing error in Fortran file with preprocessing
|
| |
| |
| |
| | |
Problem with ' (single quote) in Fortran. A string in Fortran can be between single or double quotes.
|
|/
|
|
| |
the // is in Fortran the indication for string concatenation and not for comment and should thus be ignored during, Fortran, preprocessing
|
|\
| |
| | |
typos
|
| |
| |
| |
| |
| |
| | |
some doxy typos and some misc. source typos
typos
some doxy typos and some misc. source typos
|
|/
|
|
| |
appeared in the output
|
| |
|
|
|
|
| |
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.
|
|
|
|
| |
improve performance
|
| |
|
|
|
|
| |
Signed-off-by: Adrian Negreanu <adrian.m.negreanu@intel.com>
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
by coverity
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|