| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\ \ \
| | | |
| | | | |
Warning in case of multiple python documentation sections.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In special cases when having multiple documentation section for 1 item in python it is possible that they are concatenated in a wrong way and result in a warning.
Each documentation section should be seen as a separate section and be separated from other sections.
the example:
```
#####################################################################
# # Modify Install Stage ############################################
#####################################################################
class install(_install):
"""Specialised python package installer.
It does some required chown calls in addition to the usual stuff.
"""
```
gives a warning like:
```
warning: unexpected command endverbatim
```
|
|\ \ \ \
| | | | |
| | | | | |
Better warning for non documented struct
|
| |/ / /
| | | |
| | | |
| | | |
| | | | |
In case if a 'struct' we get the message about a 'class', by using the 'compoundTypeString' this can be corrected.
(message was originally found in #7304)
|
|\ \ \ \
| | | | |
| | | | | |
Issue #7804 String double quotes in C get misinterpreted by pdflatex
|
| |/ / /
| | | |
| | | |
| | | | |
The `"` quote is in some LaTeX language packages redefined to be used to create a umlaut / umlaut / tréma and in normal running text they have to replaced / escaped,
|
|\ \ \ \
| |/ / /
|/| | | |
Compilation error on debug compilation of constexp.l
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
I case we use `LEX_FLAGS=-d` to compile `constexp.l` we get the error:
```
constexp.l: In member function ‘bool ConstExpressionParser::parse(const char*, int, const QCString&)’:
constexp.l:140:17: error: ‘yyscanner’ was not declared in this scope; did you mean ‘yyscan_t’?
140 | yyset_debug(1,yyscanner);
| ^~~~~~~~~
| yyscan_t
make[2]: *** [src/CMakeFiles/doxymain.dir/build.make:455: src/CMakeFiles/doxymain.dir/__/generated_src/constexp.cpp.o] Error 1
```
|
|\ \ \
| |_|/
|/| | |
|
| | | |
|
|/ / |
|
|\ \
| | |
| | | |
issue #7595 Links from one Markdown file to another do not work
|
|/ /
| |
| |
| |
| | |
- the not linking in case of a the relative path (as there was no anchor for it)
- (on windows) the created, internal, anchor for a file can contain a `:` but this is not possible in an anchor and has to be escaped.
|
|/ |
|
| |
|
|\ |
|
| |\
| | |
| | | |
Fix #7495 generate "bitfield"
|
| | |
| | |
| | | |
Fix missing "bitfield" property generation in Perlmod
|
| |\ \
| | | |
| | | | |
update URLS on README to prevent redirects
|
| |/ / |
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Makes doxycfg library more self contained
- renames _doxygen library to doxymain
- Modernizes Debug implementation
- Moves Doxygen::runningTime into Debug
- Moves full version string to libversion
- Removed mentioning of file version in messages (when
FILE_VERSION_FILTER is used)
- Move substitute functions into QCString
|
|\ \
| | |
| | | |
GNU compilation warnings
|
| | |
| | |
| | |
| | |
| | | |
Older GNU compilers, i.e. before version 7, don't know the option `-Wno-implicit-fallthrough`, so it is made compiler version dependent.
(would have liked to use `VERSION_GREATER_EQUAL` but this is introduced in cmake 3.7)
|
|\ \ \
| |/ /
|/| | |
|
| | | |
|
|/ / |
|
| | |
|
|\ \
| | |
| | | |
make declArgumentList be from declaration, and argumentList from definition
|
| | |
| | |
| | |
| | | |
...whereas the declArgumentList is always from the declaration
|
|\ \ \
| | | |
| | | | |
Plantuml has problems with output directories ending with directory separator
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Based on the message in #7558
In case a `HTML_OUTPUT` directory (or other `*_OUTPUT` directory ends with a directory separator we get the message:
```
QGDict::hashAsciiKey: Invalid null key
```
by stripping the directory separator this problem can be overcome.
|
|\ \ \ \
| | | | |
| | | | | |
Link fixed in documentation
|
| | | | | |
|
|\ \ \ \ \ |
|
| |\ \ \ \ \
| | | | | | |
| | | | | | | |
issue #7738 \todo ignores EXCLUDE_SYMBOLS
|
| | |\ \ \ \ \
| | |/ / / / /
| |/| | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
In case a xref item has no reference the name is empty and thus the item should not be displayed.
As it is possible that none of the items have a reference the page should only be added when there are item available to display
|
|\ \ \ \ \ \ \
| |/ / / / / /
|/| | | | | | |
|
| | | | | | | |
|
| |\ \ \ \ \ \
|/ / / / / / /
| | | | | | |
| | | | | | | |
https://github.com/dhebbeker/doxygen into dhebbeker-feature/change-DirList-container-to-std
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
and GropuDefImpl.
Required as the list type the directories are added to has pointers to non-const DirDef as value type.
(cherry picked from commit be6f0726eff5371a656a0831d50676cd30116170)
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
There is no inSort() in current QList or std container. Thus it was replaced by the sequence of adding an item and sorting the list afterwards.
(cherry picked from commit 91370bf84ac299fcb773e1b9d81e8f5c56da0725)
|
| | | | | | |
| | | | | | |
| | | | | | | |
Forward declaration is not possible for an alias.
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
(cherry picked from commit 38d38b225f1e8698e5813e16356e8929fcec1e81)
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
(cherry picked from commit 3a90e663f701e7f414d31d54264ce66d62c17976)
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
https://stackoverflow.com/a/4110482/5534993
https://www.copperspice.com/docs/cs_api_1.5/containers-c.html
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
issue #7734 Incorrect parsing of Q_PROPERTY
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
The parsing of the type / name was not done correctly as the name `{ID}` is also part of the `{TSCOPE}` and hence the name was seen as a type.
The name is the last part before an attribute is present.
Missing other parts:
- parsing of `*`
- not parsing of a number of (not supported attributes)
The definition of `Q_PROPERTY` is:
```
Q_PROPERTY(type name
(READ getFunction [WRITE setFunction] |
MEMBER memberName [(READ getFunction | WRITE setFunction)])
[RESET resetFunction]
[NOTIFY notifySignal]
[REVISION int]
[DESIGNABLE bool]
[SCRIPTABLE bool]
[STORED bool]
[USER bool]
[CONSTANT]
[FINAL])
```
Note: in the implementation we do not enforce the order of the attributes.
|