summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* | 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)
* | | 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
* | | Updated instructions to toggle debugging flex codeDimitri van Heesch2015-12-131-25/+20
| | |
* | | Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2015-12-121-0/+2
|\ \ \ | |/ /
| * | Merge pull request #423 from albert-github/feature/bug_doxyapp_clangDimitri van Heesch2015-12-121-0/+2
| |\ \ | | | | | | | | doxyapp and CLANG linking
| | * | doxyapp and CLANG linkingalbert-github2015-12-121-0/+2
| |/ / | | | | | | | | | In case CLANG is enabled for doxygen this library is also used for doxyapp, but the clang libraries were not included in the doxyapp CMake project.
* | | Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2015-12-128-123/+29
|\ \ \ | |/ /
| * | 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-102-21/+21
| |\ \ \ | | | | | | | | | | Adding compilation options for flex/lex and bison/yacc
| | * | | Adding compilation options for flex/lex and bison/yaccalbert-github2015-12-082-21/+21
| | |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| | |/ /
| * | | Merge pull request #420 from albert-github/feature/bug_csharp_set_codeDimitri van Heesch2015-12-101-1/+1
| |\ \ \ | | |/ / | |/| | Support set in code highlighting
| | * | Support set in code highlightingalbert-github2015-12-091-1/+1
| |/ / | | | | | | | | | Analogous to the C# property get also the property set is supported
* | | Made paragraph spacing more flexible in the LaTeX output to prevent page ↵Dimitri van Heesch2015-12-122-2/+2
|/ / | | | | | | overflows
* | Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2015-12-068-5/+13
|\ \
| * \ Merge pull request #415 from albert-github/feature/bug_758132_1Dimitri van Heesch2015-12-036-3/+10
| |\ \ | | | | | | | | Bug 758132 - Brief description of non documented functions
| | * | Bug 758132 - Brief description of non documented functionsalbert-github2015-11-226-3/+10
| | | | | | | | | | | | | | | | | | | | In case a function or an other item is not documented and EXTRACT_ALL has not been specified it should not appear in the list with brief description of functions etc. (This patch supersedes the patch as proposed in pull request 411 based on the comments from Dimitri van Heesch)
| * | | Merge pull request #417 from ilor/dir-prefix-find-revDimitri van Heesch2015-12-031-0/+1
| |\ \ \ | | | | | | | | | | Fix computeCommonDirPrefix sometimes not finding the correct prefix
| | * | | Fix computeCommonDirPrefix sometimes not finding the correct prefixTomasz Śniatowski2015-12-031-0/+1
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The code in some cases would search backwards in a string starting from an offset beyond the string's length. Adjust so that doesn't happen and the code doesn't mistakenly assume there is no common dir prefix. This bug has in some scenarios led to absolute paths being used for dir_(md5).html links, making doxygen output needlessly depend on details of build-time paths.
| * | | Merge pull request #416 from lameventanas/masterDimitri van Heesch2015-11-252-2/+2
| |\ \ \ | | |/ / | |/| | Fixed preprocessor macros for flex version check
| | * | Fixed preprocessor macros for flex version checklameventanas2015-11-252-2/+2
| |/ /
* | | Bug 758900 - C++ templated member-function appears both as public and privateDimitri van Heesch2015-12-061-0/+2
|/ /
* | Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2015-11-220-0/+0
|\ \ | |/
| * 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)
* | | Support flex-2.6.0Dimitri van Heesch2015-11-226-10/+10
| | |
* | | Support flex-2.6.0Heiko Becker2015-11-226-7/+7
| | | | | | | | | | | | | | | | | | The version checks only considered YY_FLEX_SUBMINOR_VERSION and did not take YY_FLEX_MINOR_VERSION into account, which made them fail with flex-2.6.0.
* | | Fixed problem with latex and PDF bookmarksDimitri van Heesch2015-11-223-73/+34
| | |
* | | Markdown with @cond and @endcondalbert-github2015-11-221-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.
* | | Fortran module private variables and EXTRACT_PRIVATE = NOalbert-github2015-11-221-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)
* | Merge pull request #408 from albert-github/feature/bug_757621Dimitri van Heesch2015-11-151-0/+1
|\ \ | | | | | | Bug 757621 - unclosed tag, c# generics method with where
| * | Bug 757621 - unclosed tag, c# generics method with wherealbert-github2015-11-071-0/+1
| |/ | | | | | | | | In the routine the <dd> tag is used to do an indentation in the <dl> section, this <dd> was not closed in endConstraintList. Problem existed from the beginning (version Release-1.5.2-20070719, commit 29a8f14)
* | Merge pull request #407 from albert-github/feature/bug_main_md_titleDimitri van Heesch2015-11-151-2/+3
|\ \ | | | | | | Title in case of USE_MDFILE_AS_MAINPAGE
| * | Title in case of USE_MDFILE_AS_MAINPAGEalbert-github2015-11-021-2/+3
| |/ | | | | | | | | In case USE_MDFILE_AS_MAINPAGE is used the title in the HTML output is the project name followed by the word documentation and in the index of LATeX / rtf the value is "Main Page", this is even the case when a level 1 header is given. This is a bit contrary to the handling non main pages. With this patch in case of USE_MDFILE_AS_MAINPAGE and a level 1 header in the beginning of the main page file this level 1 header is used title
* | Fix for Travis Build (take 3)Dimitri van Heesch2015-11-141-1/+7
| |
* | Fix for Travis Build (take 2)Dimitri van Heesch2015-11-141-1/+1
| |
* | Bug 756604 - Unable to prevent a numbered listDimitri van Heesch2015-11-143-10/+33
| |
* | Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2015-11-141-0/+7
|\ \ | |/
| * Merge pull request #404 from albert-github/feature/bug_css_filterDimitri van Heesch2015-10-311-0/+7
| |\ | | | | | | [Doxygen-users] plugin / filter not behaving as expected
| | * [Doxygen-users] plugin / filter not behaving as expectedalbert-github2015-10-141-0/+7
| | | | | | | | | | | | Added note about unsupported extensions
* | | Fixed a couple of small memory leaksDimitri van Heesch2015-11-142-3/+5
| | |
generated by cgit v0.12 at 2024-07-05 05:11:47 (GMT)