| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| | |
Properly open quotes in warning
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Commit 78b5c44 'Properly close quotes in warning' https://github.com/doxygen/doxygen/pull/7312 handled the case that a closing quote was missing in case of a missing closing quote.
I case the word template is missing it is possible to miss the opening quote, resulting in:
```
wxWidgets-3.1.3/src/x11/brush.cpp:66: warning: no matching class member found for
wxBrush::wxBrush(const wxColour &col, int style)
Possible candidates:
wxBrush::wxBrush()'
wxBrush::wxBrush(const wxColour &colour, wxBrushStyle style=wxBRUSHSTYLE_SOLID)'
```
this is fixed here.
|
|\ \
| |/
|/| |
RTF extension file to standard output, make according documentation consistent.
|
| |
| |
| |
| |
| | |
Create possibility to write rtf extension file to standard output as well, see to it that same technique is used on different places
Update documentation and make it consistent
|
|\ \
| |/
|/| |
|
| | |
|
|/
|
|
| |
This reverts commit ed4515149fd0839dba1f59858aec37b73c0ac805.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|\
| |
| | |
Fix typos
|
| |
| |
| |
| |
| |
| | |
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
```
|
|/ |
|
|
|
|
| |
with same name
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|\
| |
| |
| | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_endblock_msg
|
| |
| |
| |
| | |
Consistency
|
|\ \
| | |
| | |
| | | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_6831
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.*)
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_gitversion
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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 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.
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
groleo-docgroup
|
| | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: Adrian Negreanu <groleo@gmail.com>
|
| | | | |
| | | | |
| | | | |
| | | | | |
Read the DoxygenLayout file in a similar way as the header / footer etc. for HTML and feed the (converted) result into the XML reader.
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
Correct spelling "build in" vs. "built-in"
|
| | | | | |
|
| | | | | |
|
| |_|_|/
|/| | | |
|
|\ \ \ \
| | | | |
| | | | | |
Ambiguous file name in file command
|
| | | | |
| | | | |
| | | | |
| | | | | |
The file command has only one argument.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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.
|
|\ \ \ \ \ |
|
| |\ \ \ \ \
| | | | | | |
| | | | | | | |
USE_HTAGS = YES, there are _no_ call / caller graphs in the documentation
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
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 fails as when a wrong / old filemap is lying around this leads / can lead to incorrect results
|
|/ / / / /
| | | | |
| | | | |
| | | | | |
specialization
|
|\ \ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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:`
|
|/ / / / / |
|
|/ / / / |
|
| |/ /
|/| | |
|
|\ \ \
| |/ /
|/| | |
Bug 645910 - Segfault on recursion while parsing "\subpage A" in "\page A"
|
| | |
| | |
| | |
| | |
| | | |
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.
|