| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In case of a construct like (Markdown, analogous for Fortran):
```
test text
@cond: after cond
whatever
@endcond
some more text
```
we get a `*/` after `test text` that should not be present.
Other places exclude besides Pyton and VHDL also Fortran and Markdown and that should happen here as well.
|
| |
|
|
| |
inside a comment" warning.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In case we have:
```
/** \file
/** the second comment start line
*/
/** the docu
*/
void a_fie(void){}
/** the docu
** double commented
*/
void a_fie2(void){}
``
one would expect to get a warning regarding the
```
/**
/**
```
but none is given.
One would have expected:
```
aa.c:13: warning: Reached end of file while still inside a (nested) comment. Nesting level 1 (probable line reference: 1)
```
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
/ Python
In case we have in the comment (or in the code) of a TCL file of Python file a construct like:
```
proc get_suite {dir {sort 1}} {
set files [glob -nocomplain $dir/*.bin]
set files [glob -nocomplain $dir/*.ps]
}
```
we get the warning:
```
warning: Reached end of file while still inside a (nested) comment. Nesting level 2 (probable line reference: 3, 2)
```
although the '/*' construct has no special comment meaning in TCL / Python (comment signs '#' / '#' or '"""). So if a c-comment construct is found it is ignored for TCL and Python.
|
| |
|
|
| |
Improvement on handling `///` comments in relation to `*/` during comment conversion.
|
| |
|
|
|
| |
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
|
| |
|
|
| |
Found via `codespell`
|
| |
|
|
| |
The debug output of the commentcnv (-d commentcnv) should be independent of the setting of QUIET in the doxygen configuration file.
|
| |
|
|
|
| |
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
|
| |
|
|
|
| |
Terminating of the VHDL comment was not found as a result of the test against python.
Added handling of end of python '#' comment and VHDL '--!' comment
|
| | |
|
| |
|
|
|
|
|
| |
A formula should not not end a "verbatim" type of block. A "verbatim" type of block should only stop at the corresponding end command.
In case of a formula with an environment (i.e. f{) the name of the environment can be parsed separately.
Corrected end condition for docbookonly.
|
| | |
|
| |
|
|
| |
improve performance
|
| |
|
|
|
| |
In case markdown files are processed and they contain @cond and @endcond these are replaced wit C-style end and begin comments (and code in between is correctly removed). The C-Style comments should not be placed as they are not understood in a markdown context (analogous to what happens in Fortram, Pythone etc.).
Note: in principle @cond should not be used as a markdown file is one "comment" block and thus @if should be used, though in any case no unwanted characters should be added.
|
| | |
|
| |
|
|
| |
Signed-off-by: Adrian Negreanu <adrian.m.negreanu@intel.com>
|
| |
|
|
|
| |
In case the previous file gives a warning regarding the wrong used nested comments and the next file does not have any doxygen comment there is still the message that there is a nested comment but even without probable line numbers.
The variable counting the nested comment level was not reset, this has been corrected with this patch.
|
| | |
|
| |
|
|
| |
Markdown
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
This bug fix is an extension to the bug fix: Add warning when encountering a nested comment start (/*) without matching end (*/).
It is quite hard to find the place in the source file where the problem occurs. This bug fix helps to locate part of the problems, it is not perfect it only gives the starting comment tags that give a problem (other problems also occur e.g. when // is followed by */).
|
| |
|
|
| |
C-comments in markdown didn't work properly
|
| |
|
|
| |
end (*/).
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
| | |
|
| |\ |
|
| | |
| |
| |
| | |
An extra "breakpoint" in the input string has been created in the form of a , (comma), so for initialization lines the line will be shorter and the , (comma) will be copied later on.
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
