| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Consistency
|
| |
|
| |
|
| |
|
|\
| |
| | |
Double id for tooltips in XHTML possible.
|
| |
| |
| |
| | |
The tooltips (XHTML) should not be displayed per code fragment but for the entire (output) file as otherwise tooltips might be added multiple times resulting in double IDs.
|
|/
|
|
|
|
| |
Based on the example of #6805
- First line of inline documentation didn't have a line number
- The line numbers in inline documentation were off by one
|
|
|
|
|
|
| |
The code coloring of the output stops at an early stage, resulting in incorrect HTML / LaTeX / ... output, due to a double counting of the lines in case of `STRIP_CODE_COMMENTS=NO`.
Problem is visible when looking at the documentation of the VHDL documentation block in the manual for VHDL code in e.g. HTML and LaTex (Note problem occurs in the 1.8.15 master, not in the 1.8.14 version).
|
|
|
|
| |
'positive'
|
| |
|
|
|
|
|
|
|
| |
- add coloring of "of"
- improvement for architecture
- adding coloring for names after an end statement
removed obsolete g_CurrScope
|
|
|
|
|
| |
Super trivial typos
Some are in qtools/ which I know is a 3rd party dependency but as we know is now obsolete upstream. I reckon it wouldn't be much of an issue to merge neverthless
Tacked on several more commits
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
This patch makes the handling of the \snippet and other commands consistent between the different languages (no line numbers anymore with python) and also introduces analogous to \includelineno the command \snippetlineno.
Some non relevant changes:
- *code.l Calculation of the end line was incorrect, in case of a snippet the end line was the number of lines of the snippet and not reltive to the start line.
- *code.l made consistent over the different laguages, enabling exBlock and inlineFragment
- testing/indexpage.xml in test 14 the \snippet command was used with python and giving line numbers, linenumbers are now gone (consistency)
|
|
|
|
| |
improve performance
|
| |
|
|
|
|
|
|
| |
The version checks only considered YY_FLEX_SUBMINOR_VERSION and did not
take YY_FLEX_MINOR_VERSION into account, which made them fail with
flex-2.6.0.
|
|
|
|
| |
Signed-off-by: Adrian Negreanu <adrian.m.negreanu@intel.com>
|
| |
|
|\
| |
| | |
Remove unused local and static global variables
|
| |
| |
| |
| | |
Remove unused local and static global variables. Variables have been identified by Understand (version 758) from Scitools.
|
|/
|
|
|
| |
Also made dangerous string access more visible by introducing rawData().
This replaces data() which will now return a constant string.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
- operations on current index and node (next(), prev(), last(), first()) have been removed.
- access to internal nodes has been removed.
- old QList has been renamed to QInternalList for use inside qtools only.
- added type safe compare, new, and delete operations (compareValues(), newValue(), deleteValue()).
- add compareValues also to QDict for consistency.
- changed doxygen's implementation to comply with the new QList and QDict interface.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
|
|
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=707641
Add references if the file is filtered, as the parser
does not know whether we are insideBody or not.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|