summaryrefslogtreecommitdiffstats
path: root/src/pyscanner.l
Commit message (Collapse)AuthorAgeFilesLines
* Refactoring: making pycode.l reentrantDimitri van Heesch2020-09-061-3/+4
|
* Merge pull request #7575 from albert-github/feature/bug_py_docstrDimitri van Heesch2020-08-101-2/+2
|\ | | | | Using Python docstrings
| * Using Python docstringsalbert-github2020-02-071-2/+2
| | | | | | | | | | - making documentation a bit clearer - add configuration setting to have docstrings not as preformatted text but as normal documentation (default remains preformatted).
* | Moved stripIndentation() to util, make it safe for empty inputDimitri van Heesch2020-08-051-50/+0
| |
* | Empty python comment gives problemsalbert-github2020-08-041-6/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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).
* | Renamed stripSpaces to stripIndentation and make it work directly on the ↵Dimitri van Heesch2020-07-291-26/+29
| | | | | | | | string passed.
* | Merge branch 'feature/issue_7884' of ↵Dimitri van Heesch2020-07-291-14/+56
|\ \ | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/issue_7884
| * | issue #7884 Python to xml: Whitespace in method doc not preserved ↵albert-github2020-07-031-14/+56
| | | | | | | | | | | | | | | | | | (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).
* | | More minor tweaksDimitri van Heesch2020-07-281-3/+1
| | |
* | | issue #7923 source line numbers in warnings output by parser are off by 1albert-github2020-07-271-1/+3
| | | | | | | | | | | | 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.
* | | Refactor: Modernize clang parser and make it run with multiple threadsDimitri van Heesch2020-07-161-3/+2
|/ /
* | Refactor: modernize markdown and make it thread-safeDimitri van Heesch2020-06-161-2/+4
| |
* | Warning in case of multiple python documentation sections.albert-github2020-05-271-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 ```
* | Refactor: improve encapsulation for ArgumentListDimitri van Heesch2020-04-251-1/+1
| |
* | Enabled stricter compiler warnings and fixed all new warningsDimitri van Heesch2020-03-081-6/+13
| |
* | Fix compiler warnings on Windows (Visual Studio)Dimitri van Heesch2020-02-121-0/+3
|/
* Move DocGroup inside CommentScanner instead of using a globalDimitri van Heesch2020-01-261-5/+5
|
* Cleanup unused/unwanted parser dependencies on code generatorDimitri van Heesch2020-01-261-1/+0
|
* Make commentscan.l reentrantDimitri van Heesch2019-12-301-2/+4
|
* Make pyscanner.l reentrantDimitri van Heesch2019-12-291-875/+908
|
* Changed std::unique_ptr<Entry> to std::shared_ptr<Entry> at avoid use after ↵Dimitri van Heesch2019-12-081-17/+17
| | | | free issues
* Split language parser into "outline parser" and "code parser"Dimitri van Heesch2019-12-031-30/+4
|
* Remove bogus flex codeDimitri van Heesch2019-11-181-7/+0
|
* Fixed use of uninitialized pointer in preprocessorDimitri van Heesch2019-11-091-1/+1
|
* Replaced QList<BaseInfo> with std::vector<BaseInfo>Dimitri van Heesch2019-10-291-2/+2
|
* Changed ArgumentList to be an STL containerDimitri van Heesch2019-10-271-10/+14
|
* Merge pull request #7283 from luzpaz/typosDimitri van Heesch2019-10-091-3/+3
|\ | | | | Fix typos
| * Fix typosluz.paz2019-09-281-3/+3
| | | | | | | | | | | | 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 ```
* | Use smartpointers to manage the lifetime of Entry objectsDimitri van Heesch2019-10-071-80/+28
|/
* Consistent way to show scanner statealbert-github2019-09-051-0/+2
| | | | | 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.
* issue #7009 Python class diagram not created for the base class while works ↵Dimitri van Heesch2019-08-061-3/+1
| | | | for the derived class (fix)
* issue #7009 Python class diagram not created for the base class while works ↵Dimitri van Heesch2019-08-041-27/+40
| | | | for the derived class
* take doc group out of commentscan.lAdrian Negreanu2019-07-261-5/+5
| | | | Signed-off-by: Adrian Negreanu <groleo@gmail.com>
* Merge pull request #6916 from albert-github/feature/bug_py_classDimitri van Heesch2019-05-191-0/+26
|\ | | | | Class definition with collections
| * Class definition with collectionsalbert-github2019-04-071-0/+26
| | | | | | | | | | | | | | | | | | | | | | 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
* | Improved const correctness and added support for inline namespacesDimitri van Heesch2019-04-211-2/+2
|/
* issue #6734 parsing performance worsenedDimitri van Heesch2019-01-071-2/+3
|
* Fix for 'Definition at line' points to end of multiple-lined definition for ↵Dimitri van Heesch2018-12-231-1/+1
| | | | Python #6706
* Add support of dict/set in annotations and default valuesSergey Kozlov2018-10-081-0/+6
|
* Fix annotation with default value parsingSergey Kozlov2018-10-081-1/+2
|
* Add function annotations supportSergey Kozlov2018-10-081-28/+131
|
* Merge pull request #6499 from albert-github/feature/bug_python_linebreakDimitri van Heesch2018-09-151-1/+1
|\ | | | | Namespace with name docstrings_linebreak
| * Namespace with name docstrings_linebreakalbert-github2018-09-111-1/+1
| | | | | | | | | | 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.
* | Fixing coverity messagesalbert-github2018-09-131-1/+0
|/ | | | Note: especially latexdocvisitor (dead code that should not be dead code).
* Issue 6494: asterisks before args and kwargs are ignored in pythonalbert-github2018-09-101-1/+6
| | | | | | 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.
* Update pyscanner.lArmin Müller2018-08-211-2/+2
|
* Small problems when displaying python codealbert-github2018-05-221-1/+0
| | | | | | - 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
* Merge pull request #676 from albert-github/feature/bug_788940Dimitri van Heesch2018-04-221-3/+6
|\ | | | | Bug 788940 - Bad handling of Python class members when a class declaration line contains a comment
| * Bug 788940 - Bad handling of Python class members when a class declaration ↵albert-github2018-03-051-3/+6
| | | | | | | | | | | | line contains a comment Made comments possible after a class declaration.
* | Bug 778012 - Python List as Default Parameter not parsed correctlyalbert-github2018-03-041-8/+22
|/ | | | Added handling of square brackets, single quoted strings and double quoted strings (could contain comma's as well) to default values of arguments.