summaryrefslogtreecommitdiffstats
path: root/src/doxygen.cpp
Commit message (Collapse)AuthorAgeFilesLines
* Revert "Minor code cleanup for layout files"Dimitri van Heesch2019-10-161-1/+1
| | | | This reverts commit ed4515149fd0839dba1f59858aec37b73c0ac805.
* Properly close quotes in warningalbert-github2019-10-101-0/+2
| | | | | | | | | | | | | | Found warning like: ``` Possible candidates: 'template < T > gmic::gmic(const T &pixel_type=(T) 0) 'template < T > gmic::gmic(const char *const commands_line, const char *const custom_commands=0, const bool include_stdlib=true, float *const p_progress=0, bool *const p_is_abort=0, const T &pixel_type=(T) 0) 'template < T > gmic::gmic(const char *const commands_line, cimg_library::CImgList< T > &images, cimg_library::CImgList< char > &images_names, const char *const custom_commands=0, const bool include_stdlib=true, float *const p_progress=0, bool *const p_is_abort=0) ``` Note the starting quote `'` but there is no closing quote (in case of a file and line the closing quote is present.
* Merge pull request #7283 from luzpaz/typosDimitri van Heesch2019-10-091-1/+1
|\ | | | | Fix typos
| * Fix typosluz.paz2019-09-281-1/+1
| | | | | | | | | | | | 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-495/+474
|/
* issue #7277: C++ - Crash using all system memory on using parent constructor ↵Dimitri van Heesch2019-09-261-2/+2
| | | | with same name
* Minor code cleanup for layout filesDimitri van Heesch2019-09-241-1/+1
|
* Reduce the use of QString in favor of the more efficient QCStringDimitri van Heesch2019-09-211-1/+1
|
* Warning with xrefitem from documentationalbert-github2019-09-131-0/+2
| | | | | | | | | | The example code with the `xrefitem` in the documentation gives a warning: ``` my_errors:1: warning: multiple use of page label 'my_errors', (other occurrence: .../aa.h, line: 4) ``` it is possible (and explicitly stated) to have an `\page` with the same name giving some extra information. The warning regarding the multiple page is removed in case of a xrefitem page.
* Refactoring code for dot related source filesDimitri van Heesch2019-09-101-1/+0
|
* issue #7189: wrong warning on ambiguous image filesDimitri van Heesch2019-09-021-8/+23
|
* Merge branch 'feature/bug_endblock_msg' of ↵Dimitri van Heesch2019-08-041-121/+121
|\ | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_endblock_msg
| * Correction warning messagealbert-github2019-06-011-121/+121
| | | | | | | | Consistency
* | Merge branch 'feature/issue_6831' of ↵Dimitri van Heesch2019-08-041-1/+1
|\ \ | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/issue_6831
| * | issue #6831 Failure to recognize class array with PHP in @varalbert-github2019-02-151-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | There are 2 different situations here: - @var, here a special change is necessary to check and handle whether or not we are in PHP (declinfo.*, doxygen.cpp) - @param - the type recognition for the PHP type has to be extended with the `[]` possibility and subsequently the `[]` part has to be handled separately from the 'datatype' (doctokinizer.l, docparser.*). - In the output we now can have multiple text strings resulting in a small change in handling of the separator between the data type (*docvisitor.*)
* | | issue 7068: "QGDict::hashAsciiKey: Invalid null key" error messages (part 2)Dimitri van Heesch2019-07-311-2/+2
| | |
* | | Reduce code duplication when printing version stringDimitri van Heesch2019-07-301-31/+20
| | |
* | | Merge branch 'feature/bug_gitversion' of ↵Dimitri van Heesch2019-07-301-3/+24
|\ \ \ | | | | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_gitversion
| * | | Show git version informationalbert-github2019-05-311-11/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The original version has as features: - getting the git version number for usage in doxygen - making the doxygen version number inclusion dependent on the VERSION file The disadvantage of the chosen methodology was that an extra correction step was necessary, by defining getter methods to retrieve the values this correction can be hidden. The information is coming from different sources: - the VERSION file - the git "repository and build system (when present) Furthermore there are a couple of places where the version information is used (a.o. doxygen and doxywizard executable, though the doxygenwizard was only done "half hearted") The handling of the VERSION file has been made in such a way that it is comparable with the generation of the git version changes. For a better abstraction the version handling is all done in a separate directory.
| * | | Show git version informationalbert-github2019-04-071-3/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Show the git version on designated places (currently version, help and Doxyfile difference). The implementation is based on the git_watcher.cmake (https://github.com/andrew-hardin/cmake-git-version-tracking). The information is useful to see which. master, version of doxygen is used for a build on systems where a lot of builds are make (Fossies.org) or very regular builds are made (CGAL) Furthermore the tracking of the VERSION file was not done (when changed the version.cpp was not updated), this is corrected as well.
* | | | Improved constness and avoid using non-const members of aliasesDimitri van Heesch2019-07-291-25/+29
| | | |
* | | | Merge branch 'docgroup' of https://github.com/groleo/doxygen into ↵Dimitri van Heesch2019-07-271-0/+1
|\ \ \ \ | | | | | | | | | | | | | | | groleo-docgroup
| * | | | take doc group out of commentscan.lAdrian Negreanu2019-07-261-0/+1
| | | | | | | | | | | | | | | | | | | | Signed-off-by: Adrian Negreanu <groleo@gmail.com>
* | | | | issue @7140 DoxygenLayout does not support UTF8 BOM formatalbert-github2019-07-261-3/+1
| | | | | | | | | | | | | | | | | | | | Read the DoxygenLayout file in a similar way as the header / footer etc. for HTML and feed the (converted) result into the XML reader.
* | | | | Merge pull request #7112 from arm-in/masterDimitri van Heesch2019-07-201-1/+1
|\ \ \ \ \ | |/ / / / |/| | | | Correct spelling "build in" vs. "built-in"
| * | | | built-inArmin Müller2019-07-091-1/+1
| | | | |
* | | | | Avoid calling non-const member aliases and 0 pointer dereference in sqlite3Dimitri van Heesch2019-06-171-3/+3
| | | | |
* | | | | refactoring dot.cppThomas Haller2019-06-131-0/+1
| |_|_|/ |/| | |
* | | | Merge pull request #6954 from albert-github/feature/bug_ambig_fileDimitri van Heesch2019-05-301-1/+11
|\ \ \ \ | | | | | | | | | | Ambiguous file name in file command
| * | | | Ambiguous file name in file commandalbert-github2019-05-031-1/+1
| | | | | | | | | | | | | | | | | | | | The file command has only one argument.
| * | | | Ambiguous file name in file commandalbert-github2019-05-021-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I some cases a file name is used with the `\file` command and this filename exists multiple times although the `\file` command is in the file itself (actually file name can be omitted). Another possibility is that the file description is in another file in the same directory. When file is not found or ambiguous, try to prepend the path of the current file to it and see if the file can be found. Example is shown in the warnings file like: ``` gmic-2.6.1/gmic-qt/src/Common.h:3: warning: the name `Common.h' supplied as the second argument in the \file statement matches the following input files: gmic-2.6.1/gmic-qt/src/Common.h gmic-2.6.1/zart/include/Common.h Please use a more specific name by including a (larger) part of the path! ``` and here it is quite clear and unambiguous which file is meant.
* | | | | Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2019-05-151-9/+6
|\ \ \ \ \
| * \ \ \ \ Merge pull request #6988 from albert-github/feature/bug_htags_call_graphDimitri van Heesch2019-05-151-8/+5
| |\ \ \ \ \ | | | | | | | | | | | | | | USE_HTAGS = YES, there are _no_ call / caller graphs in the documentation
| | * | | | | USE_HTAGS = YES, there are _no_ call / caller graphs in the documentationalbert-github2019-05-141-8/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Even when htags are enabled the source code has to be parsed, but should not be written by doxygen writers. During the "generateFileSources" some other settings are done as well like for "REFERENCED_BY_RELATION". (based on question of Maciej W via lists.sourceforge.net on March 24 2014)
| * | | | | | Don't try to load htags filemap in case htags failsalbert-github2019-05-141-1/+1
| |/ / / / / | | | | | | | | | | | | | | | | | | Don't try to load htags filemap in case htags fails as when a wrong / old filemap is lying around this leads / can lead to incorrect results
* | | | | | issue 6986: C++ static template methods: duplication as non-static and ↵Dimitri van Heesch2019-05-151-0/+6
|/ / / / / | | | | | | | | | | | | | | | specialization
* | | | | Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2019-05-071-1/+1
|\ \ \ \ \
| * | | | | Missing white space in warningalbert-github2019-05-061-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some messages give a result in the form of: `'static ostream & operator<<(ostream &out, const EntityAuth &a)' at line 61 of fileD:/Fossies/ceph-14.2.1/src/auth/Auth.h` i.e. space was missing `file` and `D:`
* | | | | | Add const correctness for argument listsDimitri van Heesch2019-05-051-16/+19
|/ / / / /
* | | | | Further const correctness changesDimitri van Heesch2019-05-051-125/+130
|/ / / /
* | | | Improved const correctness and added support for inline namespacesDimitri van Heesch2019-04-211-47/+233
| |/ / |/| |
* | | Merge pull request #6857 from albert-github/feature/bug_645910Dimitri van Heesch2019-03-101-1/+8
|\ \ \ | |/ / |/| | Bug 645910 - Segfault on recursion while parsing "\subpage A" in "\page A"
| * | Bug 645910 - Segfault on recursion while parsing "\subpage A" in "\page A"albert-github2019-02-251-1/+8
| | | | | | | | | | | | | | | In version 1.7.3 (till 1.8.7) the problem of direct recursion (i.e. in a page is a subpage to itself) we got a segmentation fault, as of 1.8.8 the problem went into an endless loop. The direct recursion is now detected.
* | | Merge pull request #6858 from albert-github/feature/issue_6847Dimitri van Heesch2019-02-281-1/+1
|\ \ \ | | | | | | | | issue #6847 Physical newlines (^^) in ALIASES produce a mismatch between documentation and source code
| * | | issue_6847 Physical newlines (^^) in ALIASES produce a mismatch between ↵albert-github2019-02-251-1/+1
| |/ / | | | | | | | | | | | | | | | | | | documentation and source code In 1.8.15 the `^^` was already translated to `\_linebr` but here there was a ` ` (space) after the `^^`, here this is not the case resulting in "warning: Found unknown command `\_linebrline'" placing a ` ` after the translated value solves this problem.
* | | Refactored Definition and derived classes such that they are abstract interfacesDimitri van Heesch2019-02-281-73/+51
|/ /
* | Remove persistent storage of Entry objectsDimitri van Heesch2019-02-171-780/+540
|/
* Merge pull request #6824 from albert-github/feature/bug_766508Dimitri van Heesch2019-02-091-0/+1
|\ | | | | Bug 766508 - missing comments of overridden methods
| * Bug 766508 - missing comments of overridden methodsalbert-github2019-02-061-0/+1
| | | | | | | | Analogous to python also for PHP and Java all functions are by default virtual (for python fix see problem #6566 and fix #6570)
* | issue #6828 Physical newlines (^^) in ALIASES configuration tags not working ↵albert-github2019-02-071-1/+1
|/ | | | | | with sections, subsections, subsubsections and paragraphs Previous changes corrected use of _linebr, missed one so this was not handled properly.