| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
In case a `WARN_LOGFILE` is used it in this file no clear whether doxygen finished correctly or exited beforehand in case a fatal error.
Now a 'Exiting...' is also given in the warning log file in case an error is a fatal error.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\ |
|
| | |\
| | |
| | | |
Problem with horizontal ruler directly after fenced code section
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When having a fenced code block directly followed by a horizontal ruler like:
```
~~~
B
~~~
---
```
we get the warning:
```
bb.md:5: warning: unexpected command endcode
```
due to the fact that the markdown parser replaces the `~~~` by a `@code` / `endcode` block and then handles the horizontal ruler `---` but this is seen as a level 2 header on the previous part resulting in the markdown code:
```
@page md_bb bb
@subsection autotoc_md0 @code
B
@endcode
```
The problem also occurs when a fenced code block is created with back tics.
By adding a `\n` this problem is fixed.
|
| | |\ \
| | | |
| | | | |
HHC and directory elements starting with "."
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Based on the question 'Doxygen failed to run html help compiler, hhc.exe error HHC5010 when running from folder that has a parent folder that starts with “.”/ (https://stackoverflow.com/questions/58861908/doxygen-failed-to-run-html-help-compiler-hhc-exe-error-hhc5010-when-running-fro).
In we https://social.msdn.microsoft.com/Forums/en-US/0681145c-223b-498c-b7bf-be83209cbf4e/issue-with-html-workshop-in-a-windows-container?forum=visualstudiogeneral see:
HTML Help 1.x command line compiler hhc.exe cannot compile CHM file to folder whose full path contains folder name starting with dot. If you have that problem, you probably specified output path with folder starting with dot, e.g. "d:\My files.NET\documentation". You can use dots in folder names but not at the beginning.
We first convert the current path to a short name path and set this as current directory, this is only done on Windows other systems are not touched.
|
| |/ / / |
|
| |\ \ \
| | | |
| | | | |
issue #7396 Illegal Character in XML output
|
| | | |/
| |/|
| | |
| | | |
The usage of, the unusual, `&` in a filename caused troubles as the filenames in the file strings in the location element were not translated to XML.
|
| |\ \ \
| | | |
| | | | |
Fix line count after multiline close group
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fix for issue #7393
When closing a group on multiple lines, like:
/*! @}
*/
The line count of subsequent lines is wrong (it's one line less than it
should be).
|
| |\ \ \
| | | |
| | | | |
issue #7290 error: Problem running ghostscript gs -q -g562x56 -r384x384x -sDEVICE=ppmraw -sOutputFile=_form0.pnm -dNOPAUSE -dBATCH -- _form0.ps. Check your installation!
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
-sDEVICE=ppmraw -sOutputFile=_form0.pnm -dNOPAUSE -dBATCH -- _form0.ps. Check your installation!
@maehr had a talk with Robin Watts and Ken Sharp at IRC and there seem to be basically 3 different problems:
* `-r%dx%d` (the dimension for `r` shouldn't be `-r384x384x`, but `-r384x384`),
* misuse / unnecessary use of `--` and
* since 9.50 the command needs more control access (that might be worked around by either whitelisting the file via `--permit-file-read=_form0.eps` (only works from 9.50 and upwards) or generally accepting any file with `-dNOSAFER` (works since quite some time). The second option is considered to be unsafe if we would process any file, but in this case we process self produced / controlled files. I don't know if doxygen has any threat model that it assumes. ).
> Ken Sharp: Yeah the %dx is wrong, as Robin says its sheer luck that works
the -- isn't needed and is what's causing the first problem
and file control is the new bugbear
The suggestions have been implemented and test / docs works now with old and new version.
|
| | | | |
|
| | | | |
|
| | |/
|/| |
|
| |/ |
|
| |\ |
|
| | |\
| | |
| | | |
Small improvements of TCL output
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Undoing changes for (due to problems with doxygen tests):
- in case of `##` comment blocks the last line was not always show
- in case of multiple comment blocks, properly separate them
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
- handling of the used filename, sometimes the filename was not set resulting in case of a warning with file `<unknown>`, also improving, slightly, the line reference.
- in case of `##` comment blocks the last line was not always show
- in case of multiple comment blocks, properly separate them
- correct handling tab character in source code output (*gen)
|
| | | | |
|
| |\ \ \
| |/ /
|/| |
| | | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_7295
|
| | | |
| | |
| | |
| | | |
documentation has to be added to the "last" entry not to the "first" / "top"
|
| |\ \ \
| | | |
| | | |
| | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_warn_illegal_command
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Correcting compilation errors and warnings like:
```
error: invalid conversion from ‘const char*’ to ‘char*’ [-fpermissive]
char *cmd_start = (tok==TK_COMMAND_AT ? "@" : "\\");
warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings]
char *cmd_start = "\\";
```
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When having a problem like:
```
/** \file
*
* \link Something \see nothing2 \endlink
*
* \link Something @see nothing3 \endlink
*/
```
We will get a.o. the warnings:
```
.../aa.h:3: warning: Illegal command see as part of a \link
.../aa.h:5: warning: Illegal command see as part of a \link
```
it is not clear what the problem is. With this patch we get a little bit clearer warning:
```
.../aa.h:3: warning: Illegal command \see as part of a \link
.../aa.h:5: warning: Illegal command @see as part of a \link
```
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \ |
|
| | |\ \ \ \
| | |/ / /
| |/| | | |
Spelling corrections for src directory
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Spelling corrections as found by codespell and in #561.
Some reported problems were already fixed, others are fixed here, with some exceptions (a,o.):
- "referenceby" in defgen.cpp as this is in the output and I cannot oversee the consequences (looks like none, but ...)
- "HANGEUL_CHARSET" left as is as in some MS documentation is written: 'HANGUL_CHARSET: Also spelled "Hangeul". Specifies the Hangul Korean character set.' (https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-wmf/0d0b32ac-a836-4bd2-a112-b6000a1b4fc9).
|
| | | | | | |
|
| |/ / / / |
|
| |\ \ \ \ |
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When having a problem like:
```
namespace eval ::tk::dialog {}
namespace eval ::tk::dialog::file {}
namespace eval ::tk::dialog::file::chooseDir {
namespace import -force ::tk::msgcat::*
}
proc ::tk::dialog::file::chooseDir:: {args} {
}
```
This will lead to the following warnings:
```
QGDict::hashAsciiKey: Invalid null key
.../aa.tcl:9: warning: Illegal member name found.
```
this is due to the fact that the procedure name definition ends with `::` and thus actually has an empty procedure name (this is legal in TCL).
(see also: https://stackoverflow.com/questions/58683103/meaning-of-a-proc-name-ending-with).
In case of an empty name the last component is taken for the name too.
|
| |/ / / |
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_code_string
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In case we have an example like (based on issue #7302):
```
/// @file
/// Something
template <char C>
struct one { };
/// The struct single_009 the char
struct single_009 : one<' '> { };
/// The struct single_010 the char
struct single_039 : one<'\''> { };
/// The struct single_040 the char (
struct single_040 : one<'('> { };
/// The struct single_041 the char )
struct single_041 : one<')'> { };
/// The struct single_042 the char *
struct single_042 : one<'*'> { };
struct single_058 : one<':'> { };
/// The struct single_059 the char ;
struct single_059 : one<';'> { };
/// The struct single_060 the char <
struct single_060 : one<'<'> { };
/// The struct single_061 the char =
struct single_061 : one<'='> { };
/// The struct single_062 the char >
struct single_062 : one<'>'> { };
/// The struct single_063 the char ?
struct single_063 : one<'?'> { };
```
The result is that in the code section there are no links to the structs 41, 61, 62 as the `(` and `<` block it till the corresponding `)` and `>` is found.
Analogous problem for the double quote version.
|
| |\ \ \ \
| | | | |
| | | | | |
Skip empty HTML tag
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Due to the fact that an empty HTML tag (like `<strike/>` is seen as a start tag the rest of a documentation block is handled with the strikethrough. Same problem occurs for other tags as well, in most cases empty HTML tags should be left out of the output (and just give the warning about the empty tag).
Mentioned example:
```
/**
Before a strike:
<strike/>
after strike
*/
void fie_b_strike(void);
```
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
issue #7358: Ternary conditional and null-coalescing operator in constructor results in faulty warning
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
results in faulty warning
Problem due to the implementation of "Support for C# nullable types (Origin: bugzilla #638606)" (issue #4064, pull request #645). The used condition was a bit to stringent so later on the function was not recognized as constructor.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Removing some leftover debug statements from38f1441dc329e72ba4c782fdc721ce5199e01a67 and 6216208b0a4288a41450e4d37226f0e4c492128c
|
| |\ \ \ \ \ \ |
|
