| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
In normal C-comment (i.e. `/*` without extra `*` of `!` etc.) doxygen commands should be ignored.
This was notr te case see e.g.:
```
const char * /* O - or @code NULL@ */
zipcXMLGetAttribute();
```
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This commit changes the following in relation to string use
- The implicit convert from 'QCString' to 'const char *' is removed
- Strings parameters use 'const QCString &' as much as possible in favor
over 'const char *'
- 'if (s)' where s is a QCString has been replaced by 'if(!s.isEmpty())'
- data() now always returns a valid C-string and not a 0-pointer.
- when passing a string 's' to printf and related functions 'qPrint(s)' is
used instead of 's.data()'
- for empty string arguments 'QCString()' is used instead of '0'
- The copy() operation has been removed
- Where possible 'qstrcmp(a,b)==0' has been replaces by 'a==b' and
'qstrcmp(a,b)<0' has been replaced by 'a<b'
- Parameters of string type that were default initialized with '= 0' are
no initialized with '= QCString()'
|
|/
|
|
|
| |
Especially with commands like `\f$\mbox{\LaTeX}\f$`MathJax has some problem as it is not, yet, able to use the commands `\raise` and `lower` inside the `\mbox` as used in this LaTeX command.
Also switching in and out of math-mode doesn't work as the resulting code either doesn't work in MathJax or in LaTeX, hence the new command s `\f(` and `\f)`.
|
| |
|
| |
|
| |
|
|\ |
|
| | |
|
|/
|
|
|
| |
- Correct handling of C comment start and end tokens as well as Cpp comment start in rules. These tokes can give "Reached end of file while still inside a (nested) comment..."
- Correct other warnings in respect to lex files
|
| |
|
| |
|
|\
| |
| | |
issue #8286 Incorrect processing of VHDL strings
|
| |
| |
| |
| | |
See a `\` in comment in VHDL also as a normal character in a string.
|
|/
|
|
| |
Just copying normal vhdl comment, don't interpret it.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When having a (stripped down) example like:
```
!
!!/*T
!T*/
```
we get a warning like:
```
.../ex11f.F90:4: warning: Reached end of file while still inside a (nested) comment. Nesting level 1 (probable line reference: 2, 2)
```
even though Fortran has no nested comments, and certainly doesn't have `/*` as comment signs. So message can be ignored.
|
|
|
|
| |
There were 2 routines to recognize whether Fortran code was Fixed of Free format code, though the version in `commentcnv.l` didn't take the settings of `EXTENSION_MAPPING` into account which might lead to incorrect recognition of the format, this has been corrected.
|
| |
|
|
|
|
|
|
|
| |
Based on the definition in the (informative) Annex A of the C++ draft 2020 standard (N4849, part [gram.lex]), the definitions have been made for the lexer.
Now integer and floating point constants wit a single quote are seen as numbers and not as part of character constants.
(also tested on CGAL)
|
|
|
|
|
| |
In the file `commentcnv.l` there is no default rule present, resulting in the, non understandable, output as indicated in https://github.com/doxygen/doxygen/issues/7873#issuecomment-650100405
(this is not the cause of the problem as reported with issue https://github.com/doxygen/doxygen/issues/7873, but quite annyoing)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When we have code like:
```
//!
//! \f$a \times
//! c \f$
//!
```
this will throw a warning like:
```
warning: End of comment block while inside formula.
```
due to the fact that after the comment conversion the code is like:
```
/**
* \f$a \times
//! c \f$
* */
```
Comparing to the `///` comments:
```
///
/// \f$a \times
/// c \f$
///
```
we get
```
/**
* \f$a \times
c \f$
* */
```
This discrepancy has been removed.
|
|
|
|
| |
very popular)
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| | |
preceding '|' action
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Some email addresses give problems in the comment converter as they contain e.g. `@code`, so we try to detect Email addresses (analogous to doctokenizer.l) to prevent these false positives.
The given warning would ne like:
```
aa.h:13: warning: Reached end of file while still inside a (nested) comment. Nesting level 1 (probable line reference: 1)
```
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Spelling corrections as found by codespell and in #561.
Some reported problems were already fixed, others are fixed here, with some exceptions (a,o.):
- "referenceby" in defgen.cpp as this is in the output and I cannot oversee the consequences (looks like none, but ...)
- "HANGEUL_CHARSET" left as is as in some MS documentation is written: 'HANGUL_CHARSET: Also spelled "Hangeul". Specifies the Hangul Korean character set.' (https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-wmf/0d0b32ac-a836-4bd2-a112-b6000a1b4fc9).
|
| |
| |
| |
| | |
Forgot to add the `/` to the not "normal" characters in the ReadLine
|
|/
|
|
|
| |
Part of the problem has already been solved by means of "Bug 616379 - doxygen result by nested comment incorrectly" (pull request #6649.
The missing part (start of comment) has been added here.
|
|
|
|
|
| |
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
|