| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
| |
fatal javascript error
|
| |\
| |
| | |
Bug 722112 - 'static' and 'throw' C++ keywords not colored
|
| | |
| |
| |
| | |
In case we don't specify a name with a type in the prototype of a function the type is still stored and should be moved to the type/
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| | |
| | | |
Bug 771344 - Class name 'internal' breaks class hierarchy in C++
|
| | |/
| |
| |
| |
| |
| | |
Analogous to the rule for:
<FindMembers>{B}*"internal"{BN}*":"{BN}*
reject the "internal" keyword in case not in Cli
|
| |/ |
|
| |\ |
|
| | |\
| | |
| | | |
Option for PlantUML configuration file
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Some words was not translated. Additionally, fixed some typos.
|
| |/ / |
|
| |/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In python the STRIP_CODE_COMMENTS didn't work properly, the "## /file" was not seen by the rule <*>{POUNDCOMMENT}" as the longer "<*>"#".* took precedence.
Example file bb.py:
## \file
#
## pyfie docu
# \include aa.h
# \include bb.py
# \include cc.f
#
def pyfie():
pass
|
| |
|
|
|
|
| |
When looking at the index of the doxygen (pdf) manual we see that __init__ is on a bit strnge place (between "\" items) and that the item "\@" is missing.
Made handling of the index consistent by using latex... routines and adjusting the label routine in respect to the @.
|
| | |
|
| |\
| |
| |
| | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_766059
|
| | |
| |
| |
| |
| |
| | |
The original problem in this bug request was that forward slashes were used in the PATH instead of backslashes.
In the command shell this does not result in problems, but when calling a program from within doxygen this leads to the problem that the executable cannot be found.
In this patch the PATH variable is, just for the process, changed in such a way that ther are back slashes instead of forward slashes (Windows only, not on Cygwin).
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This patch makes the handling of the \snippet and other commands consistent between the different languages (no line numbers anymore with python) and also introduces analogous to \includelineno the command \snippetlineno.
Some non relevant changes:
- *code.l Calculation of the end line was incorrect, in case of a snippet the end line was the number of lines of the snippet and not reltive to the start line.
- *code.l made consistent over the different laguages, enabling exBlock and inlineFragment
- testing/indexpage.xml in test 14 the \snippet command was used with python and giving line numbers, linenumbers are now gone (consistency)
|
| | | |
|
| |\ \
| | |
| | | |
sqlite3gen: insert xrefs using integer refids
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
Modified the memberdef table so that it includes all elements xmlgen
dups for a memberdef.
|
| | | | |
|
| | |/
|/| |
|
| |\ \ |
|
| | |\ \
| | | |
| | | | |
Bug 737472 - HTML code special commands unconditionally include line numbers
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When using a code fragment in "regular" documentation like:
@code
This is a code fragment
@endcode
this is shown without line numbers but when using {unparsed} or another unknown extension, so
@code{unparsed}
This is a code fragment
@endcode
line numbers were shown.
(similar for the markdown fenced block).
|
| | |\ \ \
| | | | |
| | | | | |
Warnings from CLANG compiler
|
| | | | | |
| | | | |
| | | | |
| | | | | |
The CLANG compiler gave some warnings after pull request #503 ("Introducing commands includedoc and snippetdoc ") at places that are not / should not be reachable.
|
| |/ / / / |
|
| |\ \ \ \
| | |/ /
| |/| | |
|
| | |\ \ \
| | |/ /
| |/| | |
Initialization of python variables and type determination
|
| | | | |
| | | |
| | | |
| | | | |
A bit better python initialization (not only the fist "word") and subsequent determination of the type.
|
| |\ \ \ \
| |/ / / |
|
| | |\ \ \
| | | | |
| | | | | |
FORTRAN determination string in preprocessing
|
| | | |/ /
| | | |
| | | |
| | | | |
In FORTRAN a string can start (and end) either with a double quote or a single quote. The later was not considered in the preprocessing resulting in unwanted substitutions in strings.
|
| | |\ \ \
| | | | |
| | | | | |
Bug 742452 - Fortran: attributes after a blank line are ignored / Bug 625602 - FORTRAN: comment in subroutine argument list
|
| | | |/ /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- FORTRAN: comment in subroutine argument list
This patch fixes the problem that comment lines in continuation parts stopped the continuation part.
Patch consists of 2 parts:
- correct setting of continuation characters for fixed form source code
- ignoring lines with just comment (based on initial fix proposed by angus-g, but extended for empty lines and comment lines that contain a continuation character)
|
| | |\ \ \
| | | | |
| | | | | |
Determination of end of parameter list
|
| | | |/ /
| | | |
| | | |
| | | | |
The determination of a parameter list should not stop at a newline character.
|
| | |\ \ \
| | | | |
| | | | | |
Include command show lines numbers (e.g. LaTeX)
|
| | | |/ /
| | | |
| | | |
| | | |
| | | | |
Based on the report of Luis Vega (http://doxygen.10944.n7.nabble.com/include-inserts-line-numbers-for-LaTeX-PDF-output-td7683.html)
The default setting for parseCode calls was not consistent between the different output formats, resulting in wrong settings of default options (e.g. show line numbers).
|
| | |\ \ \
| | | | |
| | | | | |
Bug 710611 - Missing Page References in the Index Chapters of the LaTex/PDF output
|
| | | |/ /
| | | |
| | | |
| | | |
| | | |
| | | | |
output
In a pagref the path should not be present.
|
| | |/ /
| | |
| | |
| | |
| | | |
Purpose to have the possibility to have repeating texts not repeated in the comments.
The commands include and snippet introduce code blocks whilst the commands includedoc and snippetdoc inclode the text as is and it will be parsed by doxygen.
|
