summaryrefslogtreecommitdiffstats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* Bug 742715 - Unnamed structs gives: QGDict::hashAsciiKey: Invalid null keyDimitri van Heesch2015-12-282-5/+15
|
* Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2015-12-281-10/+19
|\
| * Bug 595186 - Python ignores \private tagalbert-github2015-12-271-9/+0
| | | | | | | | Don't overwrite the protection settings in current entry, they may result from a comment block
| * Merge pull request #429 from albert-github/feature/bug_732356Dimitri van Heesch2015-12-261-1/+1
| |\ | | | | | | Bug 732356 - doxygen's \param command is confused by some python default values
| | * Bug 732356 - doxygen's \param command is confused by some python default valuesalbert-github2015-12-261-1/+1
| | | | | | | | | | | | Decrement brace count only in case of a ')' not in case of a ','
| * | Merge pull request #431 from albert-github/feature/bug_361814Dimitri van Heesch2015-12-261-0/+14
| |\ \ | | | | | | | | Bug 361814 - python: tuple assignment not recognized as variable initialization
| | * | Bug 361814 - python: tuple assignment not recognized as variable initializationalbert-github2015-12-261-0/+14
| | |/ | | | | | | | | | | | | | | | | | | added possibility for the separate variables from a tuple assignment: a,b,c = and (a,b,c) =
| * | Merge pull request #427 from albert-github/feature/bug_641036Dimitri van Heesch2015-12-261-0/+4
| |\ \ | | | | | | | | Bug 641036 - python script with #!/usr/bin/python are not documented correctly
| | * | Bug 641036 - python script with #!/usr/bin/python are not documented correctlyalbert-github2015-12-251-0/+4
| | |/ | | | | | | | | | Handle #! at first line as a special comment (on *nix systems starts the mentioned program with the file as input)
* | | Bug 755939 - Warning refers to incorrect line for undocumented member ↵Dimitri van Heesch2015-12-281-1/+1
| | | | | | | | | | | | function (C++)
* | | Bug 758132 - Brief description of non documented functions (fixes)Dimitri van Heesch2015-12-283-8/+6
| | |
* | | Bug 745659 - The table in classes.html has no class attributeDimitri van Heesch2015-12-281-1/+1
| | |
* | | Bug 752845 - Non-alphanumeric characters in Markdown links don't work properlyDimitri van Heesch2015-12-281-2/+2
| | |
* | | Bug 731509 - Markdown backticks not processed within Markdown links.Dimitri van Heesch2015-12-281-1/+2
| | |
* | | Bug 746361 - Doxygen thinks C++ class is Objective-CDimitri van Heesch2015-12-272-1/+7
|/ /
* | Minor change to pycode.l:codifyLinesDimitri van Heesch2015-12-261-3/+3
| |
* | Merge branch 'feature/bug_593642' of ↵Dimitri van Heesch2015-12-261-29/+110
|\ \ | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_593642
| * | Bug 593642 - Python: STRIP_CODE_COMMENTS Doesn't work within the source codealbert-github2015-12-251-29/+110
| |/ | | | | | | In case STRIP_CODE_COMMENTS is set the doxygen specific comment is stripped from the output.
* | Merge pull request #428 from albert-github/feature/bug_578720Dimitri van Heesch2015-12-262-0/+2
|\ \ | | | | | | Bug 578720 - [Python] Add pyw as a valid extension
| * | Bug 578720 - [Python] Add pyw as a valid extensionalbert-github2015-12-262-0/+2
| |/ | | | | | | Added pyw as extension, based also on: https://docs.python.org/2/tutorial/appendix.html (15.1.2. Executable Python Scripts)
* | Merge pull request #430 from albert-github/feature/bug_735152Dimitri van Heesch2015-12-263-7/+33
|\ \ | | | | | | Bug 735152 - Python: Allow undocumented "cls" parameter for class methods
| * | Bug 735152 - Python: Allow undocumented "cls" parameter for class methodsalbert-github2015-12-263-7/+33
| |/ | | | | | | Made 'cls' parameter analogous to the 'self' parameter. See also https://www.python.org/dev/peps/pep-0008 (paragraph: Function and method arguments)
* | Bug 746162 - formulas creating invalid HTML codeDimitri van Heesch2015-12-262-11/+58
|/
* Bug 759622 - problems with charset using plantumlDimitri van Heesch2015-12-201-1/+1
|
* Bug 757812 - Doxygen do not support comparison angle bracket in templateDimitri van Heesch2015-12-201-2/+2
|
* Bug 757300 - Failed to document nested classes with "reference to array" ↵Dimitri van Heesch2015-12-201-1/+1
| | | | parameters
* Bug 758495 - Bug in VHDL parser + other fixesDimitri van Heesch2015-12-203-20/+139
|
* Bug 759381 - unable to @ref or @link C++ templated operator overloadsDimitri van Heesch2015-12-191-1/+6
|
* Reverted change that caused doxygen to return error code 2 when it produced ↵Dimitri van Heesch2015-12-194-8/+7
| | | | a warning
* Bug 759177 - Markdown fenced code blocks not parsed properly in commentDimitri van Heesch2015-12-191-4/+4
|
* Merge pull request #424 from albert-github/feature/bug_py_typesDimitri van Heesch2015-12-191-5/+25
|\ | | | | Correct / set types for python variables
| * Correct / set types for python variablesalbert-github2015-12-121-5/+25
| | | | | | | | | | | | | | | | | | | | 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).
* | Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2015-12-195-470/+494
|\ \
| * \ Merge pull request #412 from bagage/masterDimitri van Heesch2015-12-175-470/+494
| |\ \ | | |/ | |/| Add WARN_AS_ERROR option to stop execution at first warning (equivalent of compilers' -Werror option)
| | * Add WARN_AS_ERROR option to stop execution at first warning (equivalent of ↵Gautier Pelloux-Prayer2015-12-165-470/+494
| | | | | | | | | | | | compilers' -Werror option)
| | * Merge pull request #410 from albert-github/feature/bug_markdown_condDimitri van Heesch2015-11-151-0/+2
| | |\ | | | | | | | | Markdown with @cond and @endcond
| | | * Markdown with @cond and @endcondalbert-github2015-11-141-0/+2
| | | | | | | | | | | | | | | | | | | | 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.
| | * | Merge pull request #409 from albert-github/feature/bug_privateDimitri van Heesch2015-11-151-2/+2
| | |\ \ | | | | | | | | | | Fortran module private variables and EXTRACT_PRIVATE = NO
| | | * | Fortran module private variables and EXTRACT_PRIVATE = NOalbert-github2015-11-081-2/+2
| | | |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | From the message in the doxygen forum(http://doxygen.10944.n7.nabble.com/Fortan-problems-td7434.html and http://doxygen.10944.n7.nabble.com/Fortran-module-private-variables-and-EXTRACT-PRIVATE-NO-td7423.html) B. If EXTRACT_PRIVATE = NO, module private functions are not listed (as expected) but module private variables are (bug!). C. Implicit PRIVATE/PUBLIC/PROTECTED statements in a module work as expected but are not "appended" to function/variable documentation. This is only a nuisance. Problem had a common cause, the protection was hard set to 'Public' instead of the read value (analogous to static)
* | | | Bug 759281 - Doxygen parser confused by C++11 attributesDimitri van Heesch2015-12-131-7/+18
| | | |
* | | | Bug 759247 - C++11 unified initializer for array with templates treated as ↵Dimitri van Heesch2015-12-131-0/+2
| | | | | | | | | | | | | | | | function
* | | | Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2015-12-127-122/+28
|\ \ \ \ | |/ / /
| * | | Merge pull request #418 from albert-github/feature/bug_606104Dimitri van Heesch2015-12-101-3/+6
| |\ \ \ | | | | | | | | | | Bug 606104 - Deprecated list: Wrong prefix '<globalScope>::' for global functions
| | * | | Bug 606104 - Deprecated list: Wrong prefix '<globalScope>::' for global ↵albert-github2015-12-061-3/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | functions The globalScope as shown in the output has no meaning and is confusing (and is also lacking the starting <). This problem is a regression from: Bug 740218 - Full scope needed when making link inside cross-referenced section [with test case]
| * | | | Merge pull request #419 from albert-github/feature/flex_bison_optionDimitri van Heesch2015-12-101-20/+20
| |\ \ \ \ | | | | | | | | | | | | Adding compilation options for flex/lex and bison/yacc
| | * | | | Adding compilation options for flex/lex and bison/yaccalbert-github2015-12-081-20/+20
| | |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adding the options LAEX_FLAGS and YACC_FLAGS to the COMPILE_FLAGS for flex/lex bison/yacc to create more flexibility during compilation. Example: when one wants to compile e.g. fortranscanner.l with the flex debug flag -d one can perform the following steps: - touch fortranscanner.l in te src directory - run make LEX_FLAGS=-d or set environment variable LEX_FLAGS to -d run make to undo this touch again forttranscanner -l and run make (don't forget to unset the environment variable LEX_FLAGS) Analogous for bison/yacc wit the YACC_FLAGS
| * | | | Merge pull request #421 from albert-github/feature/py_obsoleteDimitri van Heesch2015-12-103-97/+0
| |\ \ \ \ | | | | | | | | | | | | Remove obsolete py files
| | * | | | Remove obsolete py filesalbert-github2015-12-093-97/+0
| | |/ / /
| * | | | Merge pull request #422 from albert-github/feature/bug_clang_generationDimitri van Heesch2015-12-101-1/+1
| |\ \ \ \ | | | | | | | | | | | | Adjusted used option for CLANG usage with CMake in documentation
| | * | | | Adjusted used option for CLANG usage with CMake in documentationalbert-github2015-12-091-1/+1
| | |/ / /