summaryrefslogtreecommitdiffstats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #7616 from albert-github/feature/bug_doxygen_internal_docuDimitri van Heesch2020-02-253-8/+18
|\ | | | | Removing warnings from doxygen internal documentation
| * Removing warnings from doxygen internal documentationalbert-github2020-02-253-8/+18
| | | | | | | | Although there is not a lot of doxygen internal documentation, it still should not produce warnings.
* | Incorrect handling of typedef in combination with constalbert-github2020-02-251-3/+10
|/ | | | | | | | | | | | | | | | | | | | | I issue #7060 and example was given with ``` typedef const char m_msgEvtName; ``` we see that - 1.8.15, listed under Typedefs: ` typedef const char m_msgEvtName` - 1.8.16 and up, listed under Variables: `const typedef char m_msgEvtName` so mentioned: - wrong "header" - const at the wrong place This is a regression on: C# consts incorrectly placed under instance variables (Origin: bugzilla #535853) (issue #2976) and the pull request #7048 The fix should only be used for C#
* Merge pull request #7601 from albert-github/feature/bug_rtf_listDimitri van Heesch2020-02-231-1/+1
|\ | | | | Disappearing words in RTF output after a list
| * Disappearing words in RTF output after a listalbert-github2020-02-181-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | When having the simple example: ``` First list - Item 1 1 Second list - Item 2 1 ``` in the RTF output the word `Second` disappears due to the fact that the is no space between a `\par` command and the word `Second`
* | Merge pull request #7608 from albert-github/feature/bug_warn_sectionDimitri van Heesch2020-02-236-6/+3
|\ \ | | | | | | Compilation warnings
| * | Compilation warningsalbert-github2020-02-226-6/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Due to ``` Commit: 1a56a39b4a97452a5c7c2d8e9d39ab28ca33dff0 [1a56a39] Commit Date: Friday, February 21, 2020 9:07:13 PM Restructure section handling ``` a number of compilation warnings (Windows) appeared: ``` c:\projects\doxygen\src\section.h(51): warning C4099: 'SectionInfo': type name first seen using 'struct' now seen using 'class' [C:\projects\doxygen\build\src\_doxygen.vcxproj] c:\projects\doxygen\src\section.h(50): note: see declaration of 'SectionInfo' ```
* | | Specifying filename in preprocessor debug outputalbert-github2020-02-231-3/+3
| | | | | | | | | | | | Especially when running with `QUIET=YES` it is no clear which file is preprocessed, so the filename is added to the preprocessor debug output
* | | issue #7585: Doxygen 1.8.17 false warnings and no generate output for ↵Dimitri van Heesch2020-02-231-1/+0
| | | | | | | | | | | | documented const functions
* | | Cleanup codeDimitri van Heesch2020-02-224-7/+5
| | |
* | | issue #7606 Unable to build "master" branchalbert-github2020-02-221-2/+2
|/ / | | | | | | | | | | | | | | | | | | | | regression on: ``` Commit: 1a56a39b4a97452a5c7c2d8e9d39ab28ca33dff0 [1a56a39] Commit Date: Friday, February 21, 2020 9:07:13 PM Restructure section handling ``` when sqlite3 has been enabled for the build.
* | Add documentation to section.hDimitri van Heesch2020-02-211-33/+29
| |
* | Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2020-02-211-5/+24
|\ \
| * | Problem in case using PREDEFINED with commaalbert-github2020-02-201-5/+24
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In the pull request "Enable comma as separator in configuration lists enhancement " (#6563) it was made possible to have commas as separators for lists. In case we have: ``` PREDEFINED = A(x,y)=sin(x),cos(y) ``` and use `doxygen -x` (or usethe define): this results in: ``` PREDEFINED = A(x \ y)=sin(x) \ cos(y) ``` this can be overcome by means of: ``` PREDEFINED = "A(x,y)=sin(x),cos(y)" ``` But for a lot of existing packages this poses a problem. (Found by looking at the doxygen configuration files as used by Fossies).
* | Merge branch 'sections'Dimitri van Heesch2020-02-2129-368/+456
|\ \ | |/ |/|
| * Restructure section handlingDimitri van Heesch2020-02-2129-368/+456
| |
* | Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2020-02-174-29/+40
|\ \
| * \ Merge pull request #7596 from albert-github/feature/bug_form_svgDimitri van Heesch2020-02-174-29/+40
| |\ \ | | | | | | | | Creation of svg images for formulas with inkscape
| | * | Creation of svg images for formulas with inkscapealbert-github2020-02-154-29/+40
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Based on the implementation as mentioned in #7578 to add the possibilities to generated svg images for formulas - When running with inkscape 92.3 / 92.4 on Cygwin /Windows there were no images generated as the `-o` flag didn't exist, the output file had to be specified as part of the `-l` (or `--export-plain-svg`) option - For more flexibility the system is checked on existence of the `pdf2svg` and `inkscape` executables, so no compilations flags are necessary
* | | | issue #6319: C++ function returning std::function with reference argument is ↵Dimitri van Heesch2020-02-171-15/+16
|/ / / | | | | | | | | | not recognized as a function (Origin: bugzilla #792830)
* | | Fixed error in Windows buildDimitri van Heesch2020-02-161-1/+1
| |/ |/|
* | Restructure citation handlingDimitri van Heesch2020-02-168-186/+214
| |
* | Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2020-02-154-27/+37
|\ \
| * \ Merge pull request #7569 from albert-github/feature/issue_7558Dimitri van Heesch2020-02-152-27/+35
| |\ \ | | | | | | | | issue #7558 PlantUML: Different behavior whether LATEX_OUTPUT has a final slash or not.
| | * | issue #7558 PlantUML: Different behavior whether LATEX_OUTPUT has a final ↵albert-github2020-02-032-27/+35
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | slash or not. The problem is that full qualified paths in `*_OUTPUT` were not handled properly they were handled as it were relative paths. In the documentation it is stated for e.g. LATEX_OUTPUT: > The LATEX_OUTPUT tag is used to specify where the LATEX docs will be put. If a relative path is entered the value of OUTPUT_DIRECTORY will be put in front of it. So in case of a non relative path the given path should be used and this path can be unrelated to `OUTPUT_DIRECTORY`, so we have to store the designated output path as well.
| * | | issue #7590 Map .f18 filetype to Fortranalbert-github2020-02-142-0/+2
| | |/ | |/| | | | | | | Supporting f18 extension
* | | Removed Doxygen::gatherDefines as it was not used anymoreDimitri van Heesch2020-02-153-3/+0
|/ /
* | Forgot to remove some config files.Dimitri van Heesch2020-02-134-9/+40
| | | | | | | | Added development option to use inkscape to create SVG formulas.
* | Unknown configuration enum valuesalbert-github2020-02-132-0/+20
| | | | | | | | | | | | | | | | | | | | | | | | In case we set for instance `DOT_IMAGE_FORMAT = SVG` (and generate call graphs) we get messages from the `dot` tool like: ``` error: Problems running dot: exit code=1, command='dot', arguments='".../example/html/test_8cpp_a764ac60c654173eb1a0afd0906ad5a12_icgraph.dot" -TSVG -o ".../example/html/test_8cpp_a764ac60c654173eb1a0afd0906ad5a12_icgraph.SVG"' ``` on other places (e.g `HTML_FORMULA_FORMAT`) and an unknown or enum value with a wrong case, the default value is (silently) taken. We now check: - is the enum value of the correct case otherwise (silently) set it to the correct case. - in case of an unknown enum value a warning is given and the default value is used
* | Improve formula handling and rendering.Dimitri van Heesch2020-02-1210-352/+406
| | | | | | | | Also added option HTML_FORMULA_FORMAT to generate SVG files for images (requires pdf2svg)
* | Fix compiler warnings on Windows (Visual Studio)Dimitri van Heesch2020-02-1220-5/+53
| |
* | Fix wrongly detecting ``` as code block inside running text.Dimitri van Heesch2020-02-121-3/+6
| |
* | Fixed typoDimitri van Heesch2020-02-091-1/+1
| |
* | issue #7411: "warning: return type of member is not documented" for static ↵Dimitri van Heesch2020-02-091-7/+30
| | | | | | | | void and virtual void functions
* | Merge pull request #7571 from maddox11/vhdl-fixed-bug-7432Dimitri van Heesch2020-02-094-51/+44
|\ \ | | | | | | vhdl-fixed-bug-7432
| * \ Merge branch 'master' into vhdl-fixed-bug-7432Dimitri van Heesch2020-02-086-92/+99
| |\ \
| * | | vhdl-fixed-bug-7432hake2020-02-044-51/+44
| | | |
* | | | Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2020-02-092-5/+5
|\ \ \ \
| * \ \ \ Merge pull request #7576 from albert-github/feature/bug_search_tag_extensionDimitri van Heesch2020-02-081-2/+2
| |\ \ \ \ | | | | | | | | | | | | Problem with links from search index files
| | * | | | Problem with links from search index filesalbert-github2020-02-081-2/+2
| | | |_|/ | | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The format of the tag file has been slightly changed in the past so that the original HTML_FILE_EXTENSION was preserved by adding the HTML_FILE_EXTENSION to the items in the tag file. This change has not been reflected in the search files like `files_0.js` resulting in lines like ``` ['core_5fbigfloat_2eh_8971',['CORE_BigFloat.h',['../../Number_types/CORE__BigFloat_8h.html.html',1,'']]], ``` this has been corrected. (Found in the CGAL code).
| * | | | Merge pull request #7577 from albert-github/feature/bug_warn_sectDimitri van Heesch2020-02-081-3/+3
| |\ \ \ \ | | |_|_|/ | |/| | | More indicative warning for wrong nesting of sections
| | * | | More indicative warning for wrong nesting of sectionsalbert-github2020-02-081-3/+3
| | |/ / | | | | | | | | | | | | In case we have a "*section" outside the hierarchy it is useful also have the id of the misbehaving "*section" even though line numbers are given , they might be misleading.
* | | | issue #7570 Comments replaced by block comments inside Markdown code blockDimitri van Heesch2020-02-091-1/+19
|/ / /
* | | issue #7570 Comments replaced by block comments inside Markdown code blockDimitri van Heesch2020-02-081-4/+8
|/ /
* | Minor fixes for table cell attributes in XML and docbook outputDimitri van Heesch2020-02-022-4/+2
| |
* | Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2020-02-022-10/+10
|\ \
| * \ Merge pull request #7529 from albert-github/feature/bug_vhdl_debugDimitri van Heesch2020-02-021-9/+9
| |\ \ | | | | | | | | Correct handling of error / removed debug statement
| | * | Correct handling of error / removed debug statementalbert-github2020-01-221-9/+9
| | | | | | | | | | | | | | | | | | | | | | | | In the vhdldocgen: - error should be handled in a doxygen consistent way (in this case with an err call) - removed left over debug statment (found through #7528)
| * | | Merge pull request #7553 from albert-github/feature/bug_accurate_warningDimitri van Heesch2020-02-021-1/+1
| |\ \ \ | | | | | | | | | | More accurate warning message.
| | * | | More accurate warning message.albert-github2020-01-301-1/+1
| | | |/ | | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | in code like `this command @unkn` would give (whilst all information is present) ``` warning: Found unknown command '\unkn' ``` instead of ``` warning: Found unknown command '@unkn' ```
generated by cgit v0.12 at 2025-04-03 22:10:57 (GMT)