| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
this commit is a squashed merge from lots of doxyparse evolution and
concentrates contributions from many authors, all listed at the end of this
message as Signed-off-by
follow a list of all improvements and bugfixes on doxyparse:
* workarounding strings replaced by doxygen core
* print missing module name for some C code (analizo/analizo#155)
* do not count/print 'void' as a function argument
* rough instructions for doxyparse release
* limit identifiers to 1024 chars (analizo/analizo#135)
* removing "\\" from function signatures (analizo/analizo#138)
* fix override args references (analizo/analizo#79)
* check if new_data in removeDoubleQuotes function is empty (analizo/analizo#120)
* removing double quotes from function signature (analizo/analizo#117)
* check if ArgumentList is null (analizo/analizo#116)
* don't report same module/class more than once (analizo/analizo#112)
* add missing key "defines:" to all modules (analizo/analizo#111)
* check if string is larger than 1 before removing surrounding quotes (analizo/analizo#110)
* doxyparse properly detects package methods
* output inheritance as list instead of hash
* start yaml document: ---
* adding double quoted in module name (analizo/analizo#106)
* added --version flag to doxyparse
* removing double quotes from function arguments list
* fix doxyparse segfault for python source files
* using quotes to surround members definition on yaml
* add the number of conditionals path
* generate configvalues.h
* adding .cs (csharp) as non-C file extension
* adding .pyw (python) as non-C file extension
* adding .py (python) as non-C file extension
Signed-off-by: Antonio Terceiro <terceiro@softwarelivre.org>
Signed-off-by: Henrique Dutra <hld@henriquedutra.com.br>
Signed-off-by: Igor Ribeiro Barbosa Duarte <igor.ribeiro.duarte@gmail.com>
Signed-off-by: João M. Miranda <joaomm88@gmail.com>
Signed-off-by: Jonathan Moraes <arkyebr@gmail.com>
Signed-off-by: Kleber <kleberbritomoreira10@gmail.com>
Signed-off-by: leonardork <leodegolim@yahoo.com.br>
Signed-off-by: Marcelo Ferreira <marcelohpf@gmail.com>
Signed-off-by: Mateus Andrade <mateusandrade080@gmail.com>
Signed-off-by: Matheus Miranda <matheusmirandalacerda@gmail.com>
Signed-off-by: Paulo Meirelles <paulo@softwarelivre.org>
Signed-off-by: Sabryna de Sousa <sabryna.sousa1323@gmail.com>
Signed-off-by: Vinicius Daros <vkdaros@mercurio.eclipse.ime.usp.br>
Signed-off-by: VinyPinheiro <viny-pinheiro@hotmail.com>
|
| | | | | |
| | | | |
| | | | |
| | | | | |
inside a comment" warning.
|
| |\ \ \ \ \ |
|
| | |\ \ \ \ \
| | | | | | |
| | | | | | | |
Consistency of configuration parameters
|
| | | | |/ / /
| | |/| | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Configuration parameters were used 2 forms in the code bare name like `PAPER_TYPE` and as string `"PAPER_TYPE"`.
In case of a non existing "bare name" (or misspelling) this is signaled by the compiler but in case of the string this was only shown at runtime.
In case of the usage of an obsolete configuration parameter the "bare name" was signaled as not existing (anymore).
The essential change here is the place where the ConfigValues are initialized.
|
| | |\ \ \ \ \
| | |_|/ / /
| |/| | | | |
issue #7143 note block not generated properly if there are blanks after it
|
| | |/ / / /
| | | | |
| | | | |
| | | | | |
In case minimal 2 spaces at the end of a line a line break is inserted, but the line was not terminatd so it was concatinated with the next line.
|
| |/ / / /
| | | |
| | | |
| | | | |
for the derived class (fix)
|
| | | | |
| | | |
| | | |
| | | | |
for the derived class
|
| |\ \ \ \ |
|
| | |\ \ \ \
| | | | | |
| | | | | | |
issue #6941 Tcl : separate continued lines joined in source listing
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
The input was "forgotten" but should be outputted anyway.
|
| |\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
|
| | |\ \ \ \ \
|/ / / / / /
| | | | | |
| | | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_endblock_msg
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Consistency
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
When there is a problem with a backticjk comment block we can get the message:
reached end of file while inside a ````' block!
this is a bit unreadable / non understandable as we see see 4 backticks followed by a single quote, it woulb be more readable when we get
reached end of file while inside a '```' block!
|
| |\ \ \ \ \ \ |
|
| | |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Bug 437181 - The -d Preprocessor option doesn't work for php, should be in the doc.
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
the doc.
- excluded `.php5` files from preprocessing (like other php files)
- made remark about some limits in files that are preprocessed in documentation
|
| |\ \ \ \ \ \ \ \
| |/ / / / / / /
|/| | | | | | | |
|
| | |\ \ \ \ \ \ \
|/ / / / / / / /
| | | | | | | |
| | | | | | | | |
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.*)
|
| |\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Incorrect paragraph numbers in secref list.
|
| |/ / / / / / / /
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
The definition of `\doxysection` etc. are using grouping around the section title, and this destroys the \label system as label names are stored locally.
(see also: https://tex.stackexchange.com/questions/502650/section-numbering-in-redefined-sections)
the `\doxysection` commands have been redefined (unfortunately partly copying values from book.cls)
|
| |\ \ \ \ \ \ \ \ |
|
| | | | | | | | | | |
|
| | |\ \ \ \ \ \ \ \
|/ / / / / / / / /
| | | | | | | | |
| | | | | | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_doc_cont
|
| | | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
In case we have a documentation block that is interrupted the following part is directly appended to it without an appropriate newline and results, in this case, in messages like:
```
aa.c:13: warning: Illegal command @verbatim as part of a title section
aa.c:15: warning: unexpected command endverbatim
bb.f:13: warning: Illegal command @verbatim as part of a title section
bb.f:15: warning: unexpected command endverbatim
```
We need a solution at 2 places due to the reset of of `OutputBrief` to `OutputDoc` in `setOutput`
The original problem results from the "The R Project for Statistical Computing" version 3.6.1 in the Fortran part.
|
| |\ \ \ \ \ \ \ \ \ |
|
| | | | | | | | | | | |
|
| | |\ \ \ \ \ \ \ \ \
|/ / / / / / / / / /
| | | | | | | | | |
| | | | | | | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_if_unbalanced
|
| | | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
In case in a macro substitution string the last character was a backslash this was, incorrect, not seen as a sign for a line continuation.
|
| |\ \ \ \ \ \ \ \ \ \ |
|
| | | | | | | | | | | | |
|
| | |\ \ \ \ \ \ \ \ \ \
|/ / / / / / / / / / /
| | | | | | | | | | |
| | | | | | | | | | | |
https://github.com/albert-github/doxygen into albert-github-fetaure/bug_html_ins_del_tag
|
| | | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
Github does not support the `<u>` tag for underlined text, in HTML there exists the tag `<ins>`. On https://www.w3schools.com/tags/tag_ins.asp is written:
The `<ins>` tag defines a text that has been inserted into a document.
Browsers will normally strike a line through deleted text and underline inserted text.
Most browsers will display the `<ins>` element with the following default values:
```
ins {
text-decoration: underline;
}
```
analogous there exists the tag `<del>` (https://www.w3schools.com/tags/tag_del.asp):
The `<del>` tag defines text that has been deleted from a document.
Browsers will normally strike a line through deleted text and underline inserted text.
Most browsers will display the `<del>` element with the following default values:
```
del {
text-decoration: line-through;
}
```
Definitions analogue to the underline and strike through tag the implementation for the other formats has been chosen.
|
| |\ \ \ \ \ \ \ \ \ \ \ |
|
| | |\ \ \ \ \ \ \ \ \ \ \
| | | | | | | | | | | | |
| | | | | | | | | | | | | |
warning: Reached end of file while still inside a (nested) comment.
|
| | | | | | | | | | | | | |
| | | | | | | | | | | | |
| | | | | | | | | | | | |
| | | | | | | | | | | | | |
see to it that the JAVA_BANNER comment is not seen as new start of comment, but is shown as verbatim comment (works for doxygen documentation, Doxyfile and doxywizard).
|
| |/ / / / / / / / / / / / |
|
| |\ \ \ \ \ \ \ \ \ \ \ \
| |/ / / / / / / / / / / |
|
| | |\ \ \ \ \ \ \ \ \ \ \
| | | | | | | | | | | | |
| | | | | | | | | | | | | |
warning: Member func2InGroup1() (function) of class Memgrp_Test is not documented.
|
| | | | |/ / / / / / / / /
| | |/| | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | | |
documented.
Correcting code due to the fact that `//@{` isn't seen by doxygen as block start (#7116).
Thi s problem is shown when generating the doxygen documentation.
|
| |/ / / / / / / / / / / |
|
| |\ \ \ \ \ \ \ \ \ \ \ |
|
| | |\ \ \ \ \ \ \ \ \ \ \
| | |/ / / / / / / / / /
| |/| | | | | | | | | | |
issue #7151 Doxygen 1.8.15 TOC_INCLUDE_HEADINGS >0 stops html links being generated in markdown
|
| | |/ / / / / / / / / /
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
generated in markdown
Don't create autotoc generated ids for pages.
(the `\ref` problem also occurred with `\subage`).
|
| |\ \ \ \ \ \ \ \ \ \ \
| |/ / / / / / / / / /
|/| | | | | | | | | | |
|
| | | | | | | | | | | | |
|
| |/ / / / / / / / / /
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
Regression on #7122 (and #7115 / #7116).
When having multiple consecutive `\name` sections the warning "unbalanced grouping commands" appears
Analogous to the open command also the close command needs an implicit argument.
|
