| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
- handling of the used filename, sometimes the filename was not set resulting in case of a warning with file `<unknown>`, also improving, slightly, the line reference.
- in case of `##` comment blocks the last line was not always show
- in case of multiple comment blocks, properly separate them
- correct handling tab character in source code output (*gen)
|
|\
| |
| | |
Support for <a id="label">
|
| |
| |
| |
| | |
Support besides `<a name="label">` also `<a id="label">` as `id=` is the HTML attribute to define an ad for an HTML element.
|
|\ \
| | |
| | | |
Discrepancy between vhdl input and generated sources
|
|/ /
| |
| |
| |
| |
| | |
The generated vhdl code files (.cc and .h) and didn't match the vhdl input source (vhdlpardser.jj).
When regenerating with javacc the vhdl code file they didn't compile.
vhdlparser.jj has been corrected.
|
|/
|
|
| |
This reverts commit ed4515149fd0839dba1f59858aec37b73c0ac805.
|
|\
| |
| | |
Incorrect warning for ALIASES
|
| |
| |
| |
| |
| |
| |
| |
| | |
In case we have an alias in the form: `mine_err(1)=\1` we get the warning:
```
error: Illegal alias format 'mine_err(1)=\1'. Use "name=value" or "name(n)=value", where n is the number of arguments
```
Note the round brackets in the explanation., these have to be curly brackets.
|
|\ \
| | |
| | | |
Properly close quotes in warning
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Found warning like:
```
Possible candidates:
'template < T >
gmic::gmic(const T &pixel_type=(T) 0)
'template < T >
gmic::gmic(const char *const commands_line, const char *const custom_commands=0, const bool include_stdlib=true, float *const p_progress=0, bool *const p_is_abort=0, const T &pixel_type=(T) 0)
'template < T >
gmic::gmic(const char *const commands_line, cimg_library::CImgList< T > &images, cimg_library::CImgList< char > &images_names, const char *const custom_commands=0, const bool include_stdlib=true, float *const p_progress=0, bool *const p_is_abort=0)
```
Note the starting quote `'` but there is no closing quote (in case of a file and line the closing quote is present.
|
|\ \ \
| | | |
| | | | |
Warning when using empty HTML tag
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- the HR tag has in xhtml the form <HR/>. Supporting empty tag
- better warning (with tag name, for empty tag.
- `</hr>` does not exist, correcting warning (analogous to `</br>`)
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When we use the construct:
```
<p/>
```
we get the warning:
```
warning: HTML tags may not use the 'empty tag' XHTML syntax.
```
tough the construct is handled properly, so we can omit the warning.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
albert-github/feature/issue_cgal_2095_pull_cgal_4282
Also span entire line in case of a memTemplItemRight
|
| |/ /
| | |
| | |
| | | |
Based on the CGAL issue https://github.com/CGAL/cgal/issues/2095 (and pull request https://github.com/CGAL/cgal/pull/4282) to see to it that all relevant table span the page.
|
|\ \ \
| |/ / |
|
| |\ \
| | | |
| | | | |
Bug 570798 - \\\< does not work for php constants
|
| | |/
| | |
| | |
| | | |
Handle comment for define analogous to a normal php variable, the closing part is automatically done when the comment is finished (rule: `<DefinePHPEnd>";"`).
|
| |\ \
| | | |
| | | | |
issue 7302: Parsing of template args in single-quotes is incorrect.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
In case we encounter an unescaped single or double quote during specialization we search for the closing quote.
We are cionnsidering potential escape sequences in the strings as well.
|
| |\ \ \
| | | | |
| | | | | |
Fix typos
|
| | | |/
| | |/|
| | | |
| | | |
| | | |
| | | | |
Found via
```
codespell -q 3 -S *.js,*.po,./src/translator*,*.eps,./doc/changelog.doc -L ang,ans,attribs,ba,behaviour,classe,colour,german,iff,initialise,nam,nd,que,russian,statics,te,tim,uint
```
|
| |\ \ \
| | | | |
| | | | | |
issue #7285 git executable required
|
| | |/ /
| | | |
| | | |
| | | | |
Test showed that the REQUIRED is not necessary for the doxygen build process. The git version available will not be available.
|
| |\ \ \
| | |_|/
| |/| | |
Problem with round brackets in PS output
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In case we use the doxygen inheritance diagrams in doxygen (i.e. `HAVE_DOT=NO`) for a construct like (based on #7302):
```
template <char C>
struct one { };
/// The struct str_040
struct str_040 : one<'('> { };
```
this will lead to a postscript error (epstopdf) as the `(` (and analogous the `)`) have to be escaped.
|
|/ / |
|
|\ \
| |/
|/| |
|
| | |
|
|\ \
| |/
|/| |
issue #7274 Subpages no longer possible under mainpage
|
|/
|
|
| |
Regression on #7050 / #7053 (Physical newlines (^^) not working in group names and without spaces in 1.8.15), in case the current name was explicitly set to mainpage it was still overwritten.
|
|
|
|
| |
with same name
|
|
|
|
| |
to process the string contents
|
|\ |
|
| |\
| | |
| | | |
HTML attribute name
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
A HTML attribute name can have e.g. a XML namespace in it and thus containing a colon (`:`) like:
```
<span xmlns:dct="http://purl.org/dc/terms/" property="dct:title">Social Icons</span>
```
but this results in
```
warning: found </span> tag without matching <span>
```
and grabled outpuzt.
allowing a colon in the attribute name solves this problem
|
|\ \ \
| |/ /
|/| | |
|
| | | |
|
| |\ \
|/ / /
| | |
| | | |
https://github.com/albert-github/doxygen into albert-github-fetaure/bug_340202
|
| |/
| |
| |
| |
| |
| |
| | |
The `*_cast` had already been introduced, but there were some other places that needed the "REJECT" as well.
Also the cast was missing a whitesace between the cast name and the `<`.
Tested also against he doxygen internal documentation.
|
|/ |
|
|\ |
|
| |\
| | |
| | | |
issue #7271 Tilde in preprocessor macro disappears in latex
|
| |/
|/| |
|
|/
|
|
| |
In pre part always use `\string~` for `~` otherwise it will be translated to a space.
|
|\
| |
| | |
Warning with xrefitem from documentation
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The example code with the `xrefitem` in the documentation gives a warning:
```
my_errors:1: warning: multiple use of page label 'my_errors', (other occurrence: .../aa.h, line: 4)
```
it is possible (and explicitly stated) to have an `\page` with the same name giving some extra information.
The warning regarding the multiple page is removed in case of a xrefitem page.
|
|\ \
| | |
| | | |
issue #7262 ALIASES not found when filename has more than one dot
|
| |/
| |
| |
| |
| |
| | |
Take the part after the last '.', method 'extension` gives the extension after the first '.' of a filename.
This is a regression on pull request #7121 (issue #7120)
|
|\ \
| | |
| | | |
issue #7268 Unable to build "master" branch
|