| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| |
| | |
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.
|
| |\ \ |
|
| | |\ \
| | | |
| | | | |
Problem with with comment recognition for group open and closing commands
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Besides the wanted start of comments `//!`, `///`, `/*!` and `/**` also the "normal" comments `//` and `/*` were recognized as starting a comment for the group open (`\{`, `@{`) and group closing (`\}`, `@}`) commands.
This was due to the usage of `?` in the regular expression meaning 0 or 1 times.
|
| |\ \ \ \
| |/ / /
|/| | | |
|
| | |\ \ \
|/ / / /
| | | |
| | | | |
https://github.com/albert-github/doxygen into albert-github-feature/regr_7105_2
|
| | | | |
| | | |
| | | |
| | | | |
In case of the `\name` command it is possible that a group is opened, but this group is not closed (for the `\name`), so the counting should not increase.
|
| |\ \ \ \ |
|
| | |\ \ \ \
|/ / / / /
| | | | |
| | | | | |
into albert-github-feature/regr_7105
|
| | | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In case of an extra closing we should not count this closing as otherwise sequences like:
```
@}
...
@{
...
@}
```
will give a warning at both `@}` statements and not just at the first (second one has an opening statement_.
|
| |\ \ \ \ |
|
| | |\ \ \ \
| | | | | |
| | | | | | |
Bug 304793 - paramType does not contain attribute element in compound.xsd schema
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Added "attributes" to "paramType"
|
| |\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
|
| | | | | | | |
|
| | |\ \ \ \ \
|/ / / / / /
| | | | | |
| | | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_xml_msc_schema
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
The items for caption, and size were not added to the xml schema for `\msc` \mscfile` `\dot` \dotfile` `\diafile`
|
| | | | | | | |
|
| |\ \ \ \ \ \ |
|
| | | | | | | | |
|
| | |\ \ \ \ \ \
|/ / / / / / /
| | | | | | |
| | | | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_6950
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
references in first array element
Don't stop at a hexadecimal number, but output the hexadecimal number (plus the part that has not been printed yet) and continue with the next input part.
|
| | | | | | | | |
|
| |\ \ \ \ \ \ \ |
|
| | |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
regression #7061 Rename test file
|
| | | | |/ / / / /
| | |/| | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Due to a regression on #7061 travis showed message:
```
not ok 71 - [071_enum_in_anon_ns.cpp]: test that enum values in anonymous namespaces produce no warning
-------------------------------------
/home/travis/build/doxygen/doxygen/testing/071/namespace_a_namespace_1_1_0d0.xml absent
-------------------------------------
```
|
| |/ / / / / / / |
|
| |\ \ \ \ \ \ \ |
|
| | |\ \ \ \ \ \ \
|/ / / / / / / /
| | | | | | | |
| | | | | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_6925
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
In general ATX headers ('#' headers and other markdown ) are converted to doxygen `\section` etc. commands
In case not all levels of doxygen commands are present so like;
```
\section sect1 Section
....
\subsubsection subsubsect1 Sub sub section
```
the information of the `\subsubsection` is not shown. Same happens in case the `\section` is not present at all.
Part of the steering of the ATX headers is done by means of the configuration setting TOC_INCLUDE_HEADINGS (default is 5) setting this setting to '0' will not convert the '#' headers to `\section` etc. (but this as side note).
Basic problem is fixing the not shown headers in case of missing levels in the `\section` commands.
- In case the `\section` command does start the page
- In case the `\section` command does not start the page.
Case the `\section` command does start the page: this is handled in the routine `int DocSection::parse()`
- see to it that not only the exact matching level is handled but also the 'jumps' in levels
- loop all 'section' of the found type and its sub sections and only jump out in case of the 'jump' level case
- give a warning in case of a 'level jump'
Case the `\section` command does not start the page: this is handled in the routine ` void DocRoot::parse()`
- as e.g. `\paragraph` could be followed by a `\subsubsection` each section type has to be handled one after another (otherwise higher types would not be handled)
- note the order is important therefore a `\subsubsection` has to be handled after a `\paragraph.
- due to the different handling the 'TK_LISTITEM' has to be handled at the end (each part can also give a 'TK_LISTITEM'
|
| |\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
End comment marker in \code section.
|
| | | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
When we have an end comment in a `\code` segment in a section we can get a message like:
```
warning: found */ without matching /* while inside a \code block! Perhaps a missing \endcode?
```
in the similar situation in a `\verbatim` section this message is not given. Switching from `\code` to `\verbatim` is not an option here as in that case other "commands" can lead to problems like in a code like `$string =~ s/^\s*//;`
In this patch the start `/*` and end `*/` comment markers for `\code` and `\verbatim` are completely ignored.
|
| |\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | | |
Incorrect warning message
|
| | |/ / / / / / / /
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
In case we have e.g. the comment:
```
* @b: first
```
We get the warning message:
```
warning: expected whitespace after : command
```
instead of a better understandable:
```
warning: expected whitespace after \b command
```
|
| |\ \ \ \ \ \ \ \ \ |
|
| | | | | | | | | | | |
|
| | |\ \ \ \ \ \ \ \ \
|/ / / / / / / / / /
| | | | | | | | | |
| | | | | | | | | | |
https://github.com/BCiesla/doxygen into BCiesla-latex-output-format-fixes
|
| | | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
This solves the problem where header of the paragraph in pdf output
generated from latex has different indent than other sections (like
param or retval).
|
| | | |_|_|_|_|_|/ /
| |/| | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Align latex output to man format where each section name is terminated
with colon.
|
| |\ \ \ \ \ \ \ \ \ |
|
| | |\ \ \ \ \ \ \ \ \
| | | | | | | | | | |
| | | | | | | | | | | |
issue #7126 Latex output format fixes
|
| | |/ / / / / / / / /
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
Based on the discussion in the proposed pull requests #7126, remove the colon in case it is clear that we have to do with a heading.
|
| |/ / / / / / / / / |
|
| |\ \ \ \ \ \ \ \ \ |
|
| | |\ \ \ \ \ \ \ \ \
| | | | | | | | | | |
| | | | | | | | | | | |
code.l: make CallContext independent of global variables
|
| | | | | | | | | | | | |
|
| | | |/ / / / / / / / |
|
