| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
REJECT
When we have a very large "LONGSTRINBLOCK" (e.g. a very large documentation part or an encode executable in e.g. base64 encoding) , there are a lot of lines that have to be read at once, this is not really necessary they can be read sequentially (probably at the cost of some speed)
|
|
|
|
| |
base compound not resolved under certain conditions (part 2)
|
|\
| |
| | |
issue #8336 Python class only with async methods support
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
python file to xml
Doxygen expects that decorators don't have a return in them, but the complicated decorator:
```
@basetest.unittest.skipIf(
api_implementation.Type() != 'cpp' or api_implementation.Version() != 2,
'Errors are only available from the most recent C++ implementation.')
```
has some in them.
This leads to the mentioned problem as well as that the line counting is incorrect (we see that the last mentioned lie number in the xml file is 2964 though the file has 2966 lines). By fixing this (and also the line counting in the python scanner) the problem looks to be handled.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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()'
|
| |
| |
| |
| |
| | |
- direct use of std::stringstream and std::ostream gave a 30%
drop in performance.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
After commit:
```
Commit: 9533e6d6e8e69954593da006ab00ea362980bc76
Date: Wednesday, March 24, 2021 11:44:20 PM
Regression: fix potential lockup while parsing python code
```
the package fwupd-1.5.8 crashes with:
```
Reading /cygdrive/e/Fossies/fwupd-1.5.8/contrib/firmware_packager/__init__.py...
Parsing file /cygdrive/e/Fossies/fwupd-1.5.8/contrib/firmware_packager/__init__.py...
Thread 1 "doxygen" received signal SIGSEGV, Segmentation fault.
0x000000010065ea24 in yyread (yyscanner=0x8005d6930, buf=0x6ffffff60010 "", max_size=262143)
at .../doxygen/src/pyscanner.l:1443
1443 yyextra->inputPosition+=c;
```
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
- FileInfo is based on ghc::filesystem, a std::filesystem compatible
implementation that does not require C++17.
|
| | |
|
|/ |
|
|
|
|
| |
function leads to documentation error
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When having an example like:
```
## General \PYgen0 docu
#
#
#
#
# General detail \PYgen1 text
# and more
STYLE_TEMPLATE = r'''
\makeatletter
'''
## General \PYgen2 docu
#
#
#
#
#
# General detail \PYgen3 text
# and more
STYLE_TEMPLATE1 = r'''
\makeatletter
'''
```
with
```
EXTRACT_ALL = YES
QUIET = YES
```
we get the warnings (removed doubles and sorted):
```
bb.py:1: warning: Found unknown command '\PYgen0'
bb.py:10: warning: Found unknown command '\PYgen1'
bb.py:12: warning: Found unknown command '\PYgen2'
bb.py:23: warning: Found unknown command '\PYgen3'
```
we see here (especially with `PYgen3` a wrong line number.
After fixing the line count in `pyscanner.l` there was for the second block an offset of 1. This was caused by `commentscan.l` introduced with #7960 after correcting this this offset was also gone.
Revisiting the original example of #7960 showed that here here was also an offset of 1 (probably due to a misinterpretation of where the `<tr>` warning should be mentioned), here it is now also correct..
(The original mismatch was shown of Fossies for the Pygments package)
|
| |
|
|\
| |
| | |
Using Python docstrings
|
| |
| |
| |
| |
| | |
- making documentation a bit clearer
- add configuration setting to have docstrings not as preformatted text but as normal documentation (default remains preformatted).
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In case we have an empty python comment like: `"""""""` (i.e. 6 double quotes) doxygen will crash in the pyscanner.l version of `stripIndentation`.
```
class Translator(nodes.NodeVisitor):
""""""
## the var
words_and_spaces = re.compile(r'\S+| +|\n')
```
In case of an empty comment we should not call `stripIndentation` and not place `\verbatim` / `\endverbatim` around the empty comment (the later would give an non-understandable empty comment block).
An empty comment should be handled as no comment.
Found by Fossies whilst generating documentation for Mercural 5.5).
|
| |
| |
| |
| | |
string passed.
|
|\ \
| | |
| | |
| | | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_7884
|
| | |
| | |
| | |
| | |
| | |
| | | |
(MARKDOWN_SUPPORT=NO)
Corrected handling of the comment blocks. Due to the possible nesting of classes and the handling of the first line special handling is required by means of the stripping of spaces after a return in a doc block (otherwise it might be stripped away multiple times / left multiple times).
|
| | | |
|
| | |
| | |
| | |
| | | |
Explicit counting of the removed newlines at the beginning of a documenation block (markdown.cpp) so this number can be added to get a better line number in case of warnings.
|
|/ / |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In special cases when having multiple documentation section for 1 item in python it is possible that they are concatenated in a wrong way and result in a warning.
Each documentation section should be seen as a separate section and be separated from other sections.
the example:
```
#####################################################################
# # Modify Install Stage ############################################
#####################################################################
class install(_install):
"""Specialised python package installer.
It does some required chown calls in addition to the usual stuff.
"""
```
gives a warning like:
```
warning: unexpected command endverbatim
```
|
| | |
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
free issues
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
Fix typos
|
| |
| |
| |
| |
| |
| | |
Found via
```
codespell -q 3 -S *.js,*.po,./src/translator*,*.eps,./doc/changelog.doc -L ang,ans,attribs,ba,behaviour,classe,colour,german,iff,initialise,nam,nd,que,russian,statics,te,tim,uint
```
|
|/ |
|
|
|
|
|
| |
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.
|
|
|
|
| |
for the derived class (fix)
|
|
|
|
| |
for the derived class
|
|
|
|
| |
Signed-off-by: Adrian Negreanu <groleo@gmail.com>
|
|\
| |
| | |
Class definition with collections
|