| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |\
| |
| | |
issue #8585 INLINE_SOURCES = YES do not generate code inline from sources if there is no @return after @brief.
|
| | |
| |
| |
| |
| |
| |
| | |
there is no @return after @brief.
- Extended tests for the determination whether or not detailed section is available
- Corrected links in the brief section part depending on the presence / not present detailed documentation
|
| |\ \
| | |
| | | |
Merged brief and detailed description in case if INLINE_SIMPLE_STRUCTS with LaTeX / RTF
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
LaTeX/ RTF
When we have a program like:
```
/** \file */
/** outer */
struct Outer
{
/** foo */
union Foo
{
/** Bar */
struct FooFlags
{
bool cond1; /*!< \brief bar 1
* \details details1 bar 1
*/
bool cond2; /*!< bar 2 */
} flags; /*!< \brief foo bar
* \details details2 of foo bar
*/
} myMember; /*!< public member */
private:
void myWork(); /*!< private member function */
};
```
and a Doxyfile like
```
INLINE_SIMPLE_STRUCTS = YES
QUIET=YES
GENERATE_RTF=YES
```
We see in HTML that brief and detailed description start on a separate line, but for LaTeX and RTF (it is not implemented in docbook) the detailed description directly follows the brief description without a line separator.
|
| |\ \ \
| |/ /
|/| | |
Implementation functions for INLINE_SIMPLE_STRUCTS for docbook output
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The implementation of the `INLINE_SIMPLE_STRUCTS` functions was missing for docbook.
The problem shows up when using e.g.
```
/** \file */
/** outer */
struct Outer
{
/** foo */
union Foo
{
/** Bar */
struct FooFlags
{
bool cond1; /*!< \brief bar 1
* \details details1 bar 1
*/
bool cond2; /*!< bar 2 */
} flags; /*!< \brief foo bar
* \details details2 of foo bar
*/
} myMember; /*!< public member */
private:
void myWork(); /*!< private member function */
};
```
with
```
INLINE_SIMPLE_STRUCTS = YES
QUIET=YES
GENERATE_DOCBOOK=YES
```
Note with the `INLINE_SIMPLE_STRUCTS` there is also a mismatch with the opening and closing `section` tags, but that is unrelated to this implementation(in this case is is "solved" by adding a closing section tag to struct_outer.xml and removing the last closing section tag from structs_8hpp.xml
|
| |\ \
| | |
| | | |
Compilation warnings regarding reordering
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
For a number of files we get a warning (gcc 10.2.0 and 7.5.0 and on MacOS) similar to:
In file included from .../src/util.h:31,
from .../src/xmlgen.cpp:24:
.../src/docparser.h: In constructor ‘DocHRef::DocHRef(DocNode*, const HtmlAttribList&, const QCString&, const QCString&, const QCString&)’:
.../src/docparser.h:931:16: warning: ‘DocHRef::m_relPath’ will be initialized after [-Wreorder]
931 | QCString m_relPath;
| ^~~~~~~~~
.../src/docparser.h:930:16: warning: ‘QCString DocHRef::m_file’ [-Wreorder]
930 | QCString m_file;
| ^~~~~~
.../src/docparser.h:917:5: warning: when initialized here [-Wreorder]
917 | DocHRef(DocNode *parent,const HtmlAttribList &attribs,const QCString &url,
| ^~~~~~~
|
| |\ \
| | |
| | | |
Problem with cite command (tests 12)
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When running a link checker over the (x)html results of the doxygen tests 12 and subdirs enabled we get the error:
```
Processing file:///.../testing/test_output_012/html/d0/de3/citelist.xhtml
List of broken links and other issues:
file:///..../testing/test_output_012/html/
Lines: 70, 74
Code: 200 (no message)
To do: Some of the links to this resource point to broken URI fragments
(such as index.html#fragment).
The following fragments need to be fixed:
CITEREF_LeLe12 Lines: 70, 74
```
Also looking at the results of rtf and docbook output we see incorrect links.
With the rtf links there is a subsequent problem of not returning the right "label" (see util.h).
|
| |\ \
| | |
| | | |
bug_765867 Ampersand not rendered correctly in HTML Help index
|
| | |/
| |
| |
| |
| |
| | |
Corresponds to issue #5994
In the index the (index.hhk) the special HTML characters were not escaped (as done for the index.hhc (see HtmlHelp::addContentsItem). This is corrected.
|
| |\ \ |
|
| | | | |
|
| | |\ \
|/ / /
| | |
| | | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_8591
|
| | |/
| |
| |
| | |
Added a general warning about the `/****//**` type of comment
|
| |\ \
| | |
| | | |
bug_674442 CREATE_FOLDERS should not create unused folders
|
| | | |
| | |
| | |
| | | |
Correcting compilation error.
|
| | |/
| |
| |
| |
| |
| | |
Also known as issue #4672
The folders are still created but in case the folders are empty after the doxygen run the directories are removed.
|
| | |
| |
| |
| | |
INLINE_SIMPLE_STRUCTS=YES
|
| | |
| |
| |
| | |
same name
|
| | |
| |
| |
| | |
Based on https://github.com/gulrak/filesystem/issues/128
|
| |\ \
| |/ |
|
| | |\
| | |
| | | |
Running tests with subdirs enabled
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When running the standard doxygen tests with subdirs enabled (i.e. on windows `nmake tests TESTS_FLAGS==--subdirs`) we get the following type errors:
```
Failed to run xmllint on the doxygen output file ..../testing/test_output_008
```
this is due to the fact that the file to be checked is in a subdirectory and as directory separator a backslash is used (initially there are 2 backslashes but due to e.g. `check_file = check_file[0]` one backslash disappears. Furthermore everywhere else the backslashes are converted to forward slashes.
In the resulting files there are references to the mentioned sub directories path, but the file to compare to is without therse so we have to filter them as well.
|
| | |\
| | |
| | | |
Correcting documentation warnings of doxygen's own internal documentation
|
| | |/ |
|
| |/
|
|
|
| |
also made some changes to make the templated HTML output better match the
built-in output.
|
| |
|
|
|
|
|
|
|
| |
When DISABLE_INDEX=NO and HTML_DYNAMIC_MENUS=YES (both defaults) then
on screens with a width smaller than 768 pixels, the menu will collapse into a
bar with just a hamburger button and the search field.
Also the search result window now stays within the limited of the
screen.
|
| |\
| |
| | |
Confusing debug output for markdown
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When having debug output one expects to have an overview what goes into the markdown processor and comes out of it. For markdown this happens but there can be a small step in front of it (page handling) and than the input is confusing as some processing already took place.
When having a file aa.md:
```
This is a .md file
```
we get with `doxygen -d markdown`:
```
======== Markdown =========
---- input -------
@page md_aa aa\ilinebr This is a .md file
---- output -----
@page md_aa aa\ilinebr This is a .md file
=========
```
whilst it would be less confusing when we have:
```
======== Markdown =========
---- input -------
This is a .md file
---- output -----
@page md_aa aa\ilinebr This is a .md file
=========
```
|
| | | |
|
| |\ \ |
|
| | | | |
|
| | |\ \
|/ / /
| | |
| | | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_8563
|
| | | |
| | |
| | |
| | |
| | |
| | | |
improperly
A small warning about the usage of "Putting documentation after members" in case of a define.
|
| | | | |
|
| |\ \ \ |
|
| | | | | |
|
| | |\ \ \
|/ / / /
| | | |
| | | | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_8541
|
| | | | |
| | | |
| | | |
| | | | |
A `::` at the end is not necessary, intenmtion was to use make explicitly, by ".*` that all subpackages were used but that is not necessary.
|
| | | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Adding the default packages from "java.lang"
From the standard "The Java® Language, Specification, Java SE 16 Edition" ,Chapter 7, Packages and Modules:
> Code in a compilation unit automatically has access to all classes and interfaces
> declared in its package and also automatically imports all of the public classes and
> interfaces declared in the predefined package java.lang.
|
| | | | |
|
| |\ \ \ |
|
| | |\ \ \
| | |_|/
| |/| | |
issue #8552 Javadoc: strange issue with @verbatim ... @endverbatim
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- Similar problems can occur with the `\startuml` and `msc` command.
```
/**
* @startuml
* {\f} @code
* @enduml
*/
```
- some further needed corrections (for lexcode)
- `\endvhdlflow` does not exist
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
The end condition of a block was not detected correctly. in `scanner.l` (and thus `lexscanner.l` too) either the second part was missing or the compete test was missing.
Furthermore some conditions weren't handled correctly / incomplete.
|
| |/ / / |
|
| |\ \ \ |
|
