| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_startuml
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Not all diagrams can be created with the PlantUML `@startuml` command but need another
PlantUML `@start...` command. This wil look like `@start<engine>` where currently supported are
the following `<engine>`'s: `uml`, `bpm`, `wire`, `dot`, `ditaa`, `salt`, `math`, `latex`,
`gantt`, `mindmap`, `wbs`, `yaml`, `creole`, `json` and `flow`. By default the `<engine>` is
`uml`. The `<engine>` can be specified as an option.
Explicitly the option variant has been chosen so we won't get an explosion of extra commands.
|
| |
| |
| |
| | |
2 or more returns inside a quoted text were not handled properly, added a repeat count.
|
|\ \
| | |
| | | |
issue #8511 Java: linebreak after @link can cause wrong parsing of subsequent doc
|
| | |
| | |
| | |
| | |
| | |
| | | |
subsequent doc
Allowing also a `\n` after the @link.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This commit changes the following in relation to string use
- The implicit convert from 'QCString' to 'const char *' is removed
- Strings parameters use 'const QCString &' as much as possible in favor
over 'const char *'
- 'if (s)' where s is a QCString has been replaced by 'if(!s.isEmpty())'
- data() now always returns a valid C-string and not a 0-pointer.
- when passing a string 's' to printf and related functions 'qPrint(s)' is
used instead of 's.data()'
- for empty string arguments 'QCString()' is used instead of '0'
- The copy() operation has been removed
- Where possible 'qstrcmp(a,b)==0' has been replaces by 'a==b' and
'qstrcmp(a,b)<0' has been replaced by 'a<b'
- Parameters of string type that were default initialized with '= 0' are
no initialized with '= QCString()'
|
|/ |
|
| |
|
|
|
|
|
| |
- direct use of std::stringstream and std::ostream gave a 30%
drop in performance.
|
| |
|
| |
|
|\ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/
|
|
|
| |
- Correct handling of C comment start and end tokens as well as Cpp comment start in rules. These tokes can give "Reached end of file while still inside a (nested) comment..."
- Correct other warnings in respect to lex files
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
In case of an artificial line break and the string starting with a `"` reject the rule, so lonely `"` are handled properly.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When having a simple file like:
```
/// \file
/// @brief Different xxxxxxxxxxxxxxxxxxxxx
/// @param[in] var = zzzzzz
/// @details Different yyyyyyyy
void fie(int var);
``
we see in the version 1.8.18 that the text is displayed as:
```
Parameters
[in] var = zzzzzz
Different yyyyyyyy
```
but in the newer versions this is like:
```
Parameters
[in] var = zzzzzz Different yyyyyyyy
```
the inserted intermediate `\ilinebr` are not handled as newlines
|
|\
| |
| | |
issue #8142 UTF-8 in URL in source generates truncated URL in HTML
|
| |
| |
| |
| | |
Specifying the URL in a similar way as other IDs
|
|/
|
|
|
| |
- missing colon (`:`) at irc
- adding irc, sftp and ftps
|
|
|
|
| |
Add in the `@` sign as possible character in a FILEMASK
|
|
|
|
|
|
|
|
|
|
| |
Removing compiler warnings like:
```
.../src/doctokenizer.l(101): warning C4267: '=': conversion from 'size_t' to 'int', possible loss of data
.../src/doctokenizer.l(844): warning C4267: 'initializing': conversion from 'size_t' to 'int', possible loss of data
...
```
(analogous as done in e.g. `commentscan.l`)
|
|
|
|
|
|
| |
for blank lines (hindering certain manual parsing)
Don't terminate a paragraph and remove the whitespace when inside a pre block, but output the blanks.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When having examples like:
```
Steps
1. \aa2
2. \aa3
3. \aa4
\aa5
```
and
```
Steps
- \bb2
- \bb3
- \bb4
\aa5
```
we get warnings like:
```
.../aa_list.md:3: warning: Found unknown command '\aa2'
.../aa_list.md:4: warning: Found unknown command '\aa3'
.../aa_list.md:5: warning: Found unknown command '\aa4'
.../aa_list.md:6: warning: Found unknown command '\aa5'
.../bb_list.md:3: warning: Found unknown command '\bb2'
.../bb_list.md:4: warning: Found unknown command '\bb3'
.../bb_list.md:5: warning: Found unknown command '\bb4'
.../bb_list.md:6: warning: Found unknown command '\aa5'
```
instead off:
```
.../aa_list.md:2: warning: Found unknown command '\aa2'
.../aa_list.md:3: warning: Found unknown command '\aa3'
.../aa_list.md:4: warning: Found unknown command '\aa4'
.../aa_list.md:5: warning: Found unknown command '\aa5'
.../bb_list.md:2: warning: Found unknown command '\bb2'
.../bb_list.md:3: warning: Found unknown command '\bb3'
.../bb_list.md:4: warning: Found unknown command '\bb4'
.../bb_list.md:5: warning: Found unknown command '\aa5'
```
this is due to the fact that there is a line le counting. In case of REJECT no lineCount should be performed and otherwise just once.
|
|
|
|
|
|
|
|
|
| |
With the doctokinizer.l we get the warnings like:
```
doctokenizer.l(502): warning C4018: '<': signed/unsigned mismatch
```
The casting of `(int)` is also used on other places in this file like in `handleHtmlTag`.
|
|
|
|
|
|
| |
- lineCount() without arguments was unused
- converted lineCount(...) into a macro with yytext and yyleng as
arguments
|
|\
| |
| |
| | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_doctok_cnt
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When having a file like:
```
@page md_aa aa
Last \error2
- Install \error3
```
we get the warnings:
```
aa.md:3: warning: Found unknown command '\error2'
aa.md:7: warning: Found unknown command '\error3'
```
instead of
```
aa.md:3: warning: Found unknown command '\error2'
aa.md:5: warning: Found unknown command '\error3'
```
Investigation lead to that this is due to the fact that with a `REJECT` the line counter in `doctokinizer.l` is not reset. By counting the lines ourselves we can properly count the lines.
(Other lexers don't have this problem as here we already do the counting ourselves)
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When we have a, stripped down, example like:
```
\mainpage the page
<tt>$PATH:</tt>$x86$<tt>bin</tt>
```
we get the warning like:
```
aa.md:4: warning: end of comment block while expecting command </tt>
```
this is due to the fact that `$PATH:</tt>$` is seen as a RCS tag although `PATH` is not a RCS keyword.
Limiting the number of allowed keywords to the real RCS tags (for CVS the list is the same).
See also:
- https://www.gnu.org/software/trans-coord/manual/cvs/cvs.html#Keyword-substitution
- https://www.gnu.org/software/rcs/manual/rcs.html#Keywords
|
|
|
|
|
| |
Also replaced tabs by spaces and removed trailing whitespace
And fixed line counting issue.
|
|
|
|
| |
The pattern `\ilinebr` is actually also a line break, but was not handled.
|
|\
| |
| |
| | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_direction
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In the current version a line like:
```
uint8_t innInstances, ///< [inn]Number of CIP node instances.
```
was seen as an input parameter.
Also not all combinations were checked (`[inout]` was OK but `[outin]` wasn't although `[in,out]` and `[out,in]` were working in the tokenizer.
Line up the detection of the direction between the tokenizer and the method `extractDirection`
Note: this problem was found when working on #7879.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
- White space around \\ilinebr is not preserved in commentscan
- Cases where \n was unput in doctokenizer are now handled in the same
way for \\ilinebr
|
| |
| |
| |
| |
| |
| |
| | |
- Routines to strip leading and trailing whitespace now also take
\\ilinebr into account
- Added a number of cases in doctokenizer.l where \\ilinebr wasn't
handled yet.
|
|/
|
|
|
|
|
|
|
|
| |
- Changed \_linebr to \ilinebr
- \ilinebr is now also passed to doctokenizer
- Also fixes issue #7493 regarding \snippet inside markdown tables and
dealing with wrong line on issues detected by docparser after a
markdown table.
- Added function tracing to markdown (enabled with -d markdown in a
debug build)
|
| |
|
|
|
|
| |
Implementation of the C++2x three-way / spaceship operator.
|