| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| | |
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
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Class definitions can have collections and these can have strings e.g.:
class Url(namedtuple('Url', url_attrs)):
and this results in:
warning: Detected potential recursive class relation between class conda::_vendor::urllib3::util::url::Url and base class Url!
Strings are now possible and seen as strings.
See also (including example with namedtuble): https://docs.python.org/3/library/collections.html
|
| |/ |
|
| | |
|
| |
|
|
| |
Python #6706
|
| | |
|
| | |
|
| | |
|
| |\
| |
| | |
Namespace with name docstrings_linebreak
|
| | |
| |
| |
| |
| | |
As a regression on pull request #674 in respect to the moving of the markdown handling place the `\_linebreak` command is not translated anymore.
In fact the `\_linebreak` is not necessary at all only the space is required as the `\namespace` command takes just one word as argument.
|
| |/
|
|
| |
Note: especially latexdocvisitor (dead code that should not be dead code).
|
| |
|
|
|
|
| |
Added asterisks in the type field.
The type is temporary stored in a variable as the argument field has not yet been defined for its argument.
|
| | |
|
| |
|
|
|
|
| |
- with was not colored (in pyscanner the KEYWORD item was not used, so removed as dead code)
- incorrect handling of a 'triquote' at end of string
- incorrect handling of a stringprefix followed by the end of a string
|
| |\
| |
| | |
Bug 788940 - Bad handling of Python class members when a class declaration line contains a comment
|
| | |
| |
| |
| |
| |
| | |
line contains a comment
Made comments possible after a class declaration.
|
| |/
|
|
| |
Added handling of square brackets, single quoted strings and double quoted strings (could contain comma's as well) to default values of arguments.
|
| | |
|
| |
|
|
| |
A bit better python initialization (not only the fist "word") and subsequent determination of the type.
|
| |
|
|
| |
End of the doctrings can be only triple double or single quotes not with optional u or r or even ! at the end.
|
| |
|
|
| |
Added support for raw and unicode docstrings in python scanner (was already available in python code scanner)
|
| |
|
|
| |
improve performance
|
| |
|
|
| |
Don't overwrite the protection settings in current entry, they may result from a comment block
|
| |\
| |
| | |
Bug 732356 - doxygen's \param command is confused by some python default values
|
| | |
| |
| |
| | |
Decrement brace count only in case of a ')' not in case of a ','
|
| |\ \
| | |
| | | |
Bug 361814 - python: tuple assignment not recognized as variable initialization
|
| | |/
| |
| |
| |
| |
| |
| | |
added possibility for the separate variables from a tuple assignment:
a,b,c =
and
(a,b,c) =
|
| |\ \
| | |
| | | |
Bug 641036 - python script with #!/usr/bin/python are not documented correctly
|
| | |/
| |
| |
| | |
Handle #! at first line as a special comment (on *nix systems starts the mentioned program with the file as input)
|
| |/
|
|
| |
Made 'cls' parameter analogous to the 'self' parameter. See also https://www.python.org/dev/peps/pep-0008 (paragraph: Function and method arguments)
|
| |
|
|
|
|
|
|
|
|
| |
The bool python type was not handled.
In case of the initialization by means of a method call a variables was was aid to be a tuple (e.g. env= os.environ.copy())
Methods with initialization with defaults were shown without arguments in the brief description (e.g. def create_dir(dir, create=True):)
Arguments with values in method calls were seen as variables variables in case of continuation lines (e.g.
parser.add_argument("--https_proxy", nargs="?", help="Proxy to be used for https requests",
action="store", const="myproxy.domain.com:8080")
in this case action was seen as variable).
|
| |
|
|
| |
Proper handling of escaped character inside a triple quoted string (""" and ''')
|
| |\
| |
| | |
Bug 752657 - XML not documenting a class in python
|
| | |
| |
| |
| | |
Problem looks like to be the improper handling of strings in this case a single quote was not seen as the start of a string and thus the double quote was mistreated.
|
| |/
|
|
| |
Problem comes from the fact that the last argument has a default value and in this case the routine argListToString is mot called as it is done in case of ')' after an argument without default value (see section "FunctionParams").
|
| |
|
|
| |
Signed-off-by: Adrian Negreanu <adrian.m.negreanu@intel.com>
|
| | |
|
| |
|
|
| |
Remove unused local and static global variables. Variables have been identified by Understand (version 758) from Scitools.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
