summaryrefslogtreecommitdiffstats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* issue #7271 Tilde in preprocessor macro disappears in latexalbert-github2019-09-191-1/+1
| | | | In pre part always use `\string~` for `~` otherwise it will be translated to a space.
* Merge pull request #7260 from albert-github/feature/bug_xref_pageDimitri van Heesch2019-09-174-2/+6
|\ | | | | Warning with xrefitem from documentation
| * Warning with xrefitem from documentationalbert-github2019-09-134-2/+6
| | | | | | | | | | | | | | | | | | | | 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.
* | Merge pull request #7263 from albert-github/feature/issue_7262Dimitri van Heesch2019-09-171-1/+2
|\ \ | | | | | | issue #7262 ALIASES not found when filename has more than one dot
| * | issue #7262 ALIASES not found when filename has more than one dotalbert-github2019-09-151-1/+2
| |/ | | | | | | | | | | 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" branchalbert-github2019-09-172-2/+3
| | | | | | | | | | | | | | | | Missing configimpl.l.h: - added dependency for doxycfg problems with tabs" - replaced tabs by spaces
* | Generalized the HTML comment detection and handlingDimitri van Heesch2019-09-161-8/+3
| |
* | Merge branch 'feature/bug_html_comment' of ↵Dimitri van Heesch2019-09-161-1/+6
|\ \ | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_html_comment
| * | HTML start comment with 3 dashesalbert-github2019-09-051-1/+6
| | | | | | | | | | | | | | | | | | | | | A normal HTML comment `<!--` has 2 `-` signs but it is not prohibited to have 3, but doxygen translates `<!---` into `<!-&ndash;` and thus the comment is not recognized. By checking and consequently handling, doing the right skipping, also the 3 `-` sign version the problem can be solved. An end comment cannot contain 3 `-` signs, so here no changes have to take place. The version with 3 or more `-` are in a start HTML comment does not give a problem with xmllint either.
* | | Merge pull request #7264 from albert-github/feature/bug_164073Dimitri van Heesch2019-09-161-0/+17
|\ \ \ | | | | | | | | Bug 164073 - There should be a dummy tag that Doxygen ignores
| * | | Bug 164073 - There should be a dummy tag that Doxygen ignoresalbert-github2019-09-151-0/+17
| | |/ | |/| | | | | | | Introduced the `\noop` command to ignore text till end of the line.
* | | Merge pull request #7266 from luzpaz/typosDimitri van Heesch2019-09-163-4/+4
|\ \ \ | | | | | | | | Fix some typos
| * | | Fix some typos luz.paz2019-09-163-4/+4
| |/ /
* | | Simplified code generated by scan_states.pyDimitri van Heesch2019-09-161-12/+8
| | |
* | | Merge branch 'feature/bug_consistency_state_2' of ↵Dimitri van Heesch2019-09-1220-78/+167
|\ \ \ | |/ / |/| | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_consistency_state_2
| * | Consistent way to show scanner statealbert-github2019-09-0520-78/+167
| |/ | | | | | | | | Create a consistent way to display the state mnemonics of the different scanners (analogous to the fortranscanner.l) Use an automatic procedure to generate the routine with the translation of the states to a string.
* | Merge pull request #7251 from albert-github/feature/bug_674005Dimitri van Heesch2019-09-121-2/+16
|\ \ | | | | | | Bug 674005 - Crop png formula environnment problem for HTML output
| * | Bug 674005 - Crop png formula environnment problem for HTML outputalbert-github2019-09-091-2/+16
| | | | | | | | | | | | | | | | | | `divips -E` does not always return the correct bounding box. The program `ps2epsi` returns a good bounding box. - don't use the `-E` with `dvips` - convert the file from `dvips` with `ps2epsi` to an encapsulated postscript file
* | | Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2019-09-121-3/+4
|\ \ \
| * \ \ Merge pull request #7253 from albert-github/feature/bug_ircDimitri van Heesch2019-09-111-3/+4
| |\ \ \ | | | | | | | | | | Bogus explicit link warning message from irc protocol name
| | * | | Bogus explicit link warning message from irc protocol namealbert-github2019-09-111-3/+4
| | |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When having: ``` * IRC: irc://irc.gimp.org/#gsconnect ``` we get: ``` warning: explicit link request to 'gsconnect' could not be resolved ``` When using the 'news:" protocol we don't get this message, adding 'irc' to the list of possibilities. (Found in https://github.com/andyholmes/gnome-shell-extension-gsconnect )
* | | | Fixed a couple of compiler warnings on WindowsDimitri van Heesch2019-09-121-2/+2
|/ / /
* | | Refactoring code for dot related source filesDimitri van Heesch2019-09-1018-405/+406
|/ /
* | issue #6715: Errorneous matching of the immediately following block command ↵Dimitri van Heesch2019-09-072-7/+2
| | | | | | | | after @ref (try 2)
* | issue #6715: Errorneous matching of the immediately following block command ↵Dimitri van Heesch2019-09-071-0/+5
|/ | | | after @ref
* issue #7189: wrong warning on ambiguous image filesDimitri van Heesch2019-09-021-8/+23
|
* Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2019-09-021-0/+1
|\
| * Backslash in href.albert-github2019-09-021-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When having a backslash in a href like: ``` <a href="C:\boost">`C:\boost`</a> ``` we get in LaTeX the error: ``` (aa_8h.tex ! Undefined control sequence. <argument> C:\boost l.6 \href{C:\boost} {\texttt{ {\ttfamily C\+:\textbackslash{}boost}}} ``` this can be overcome by escaping the backslash. Note this is just an example, for an URI actually forward slashes should be used. It is just about the backslash not generating an error.
* | issue #7243: Some PHP classes are not properly extracted/documentedDimitri van Heesch2019-09-021-7/+6
|/
* Merge pull request #7202 from albert-github/feature/issue_7200Dimitri van Heesch2019-08-311-4/+44
|\ | | | | issue #7200 Fortran warning: type not declared or defined
| * issue #7200 Fortran warning: type not declared or definedalbert-github2019-08-151-4/+44
| | | | | | | | | | | | | | | | | | | | | | | | | | problem in the statement: ``` type(log_handle_type), protected, save, & bind(c, name="LOG_HANDLE_one") & :: log_handle_one ``` is the fact that the "bind" attribute is not handled. - added handling of the bind attribute - extending the bind definition also with the single quote version.
* | Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2019-08-312-1/+4
|\ \
| * | Parsing `#` sign inserted by preprocessor in fixed Form Fortranalbert-github2019-08-301-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In Fortran a file that is included is replaced by the doxygen preprocessor by something like: `# 11 "<path>/<filename>" 2` when this is in fixed form Fortran and the `<path>/<filename>` is long it is possible that the closing double quote is beyond position 72 and thus not seen resulting in: ``` Error in file <path>/<filename> line: 73, state: 22(String) ``` this is caused as the `#` is not handled properly in prepassFixedForm. The `#` should be handled analogous to e.g. `C`.
| * | Merge pull request #7220 from albert-github/feature/issue_7218Dimitri van Heesch2019-08-291-1/+3
| |\ \ | | | | | | | | issue #7218 Doxygen parsing word documents
| | * | issue #7218 Doxygen parsing word documentsalbert-github2019-08-231-1/+3
| | | | | | | | | | | | | | | | | | | | making list consistent again. See also table in chapter "Getting Started"
* | | | Made check for void return more strictDimitri van Heesch2019-08-311-14/+14
| | | |
* | | | Merge branch 'feature/issue_7212' of ↵Dimitri van Heesch2019-08-311-3/+3
|\ \ \ \ | |/ / / |/| | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/issue_7212
| * | | issue #7212 1.8.16: Function returning void pointer generates warningalbert-github2019-08-201-3/+3
| |/ / | | | | | | | | | Have to see that the argument is not a void pointer but just a void
* | | issue #7236: C++: bug when using function as parameterDimitri van Heesch2019-08-291-3/+15
| | |
* | | Merge pull request #7224 from mordante/doxygen_comment_fixesDimitri van Heesch2019-08-272-9/+9
|\ \ \ | | | | | | | | Doxygen comment fixes
| * | | Fixes a @param's parameter name.Mark de Wever2019-08-241-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This was found while testing with Clang's -Wdocumentation -Wdocumentation-pedantic options. Note from the coding style used it would seem useDict would be the more appropriate name, but usedict is used on multiple occasions in this file.
| * | | Use the proper trailing comment.Mark de Wever2019-08-241-8/+8
| |/ / | | | | | | | | | | | | This was found while testing with Clang's -Wdocumentation -Wdocumentation-pedantic options.
* | | issue #7216: non-const getGroupDef() called on aliased member (cleanup + ↵Dimitri van Heesch2019-08-2614-52/+30
| | | | | | | | | | | | null pointer fix)
* | | issue #7216: non-const getGroupDef() called on aliased memberDimitri van Heesch2019-08-2510-112/+137
|/ /
* | Strange '*/' in Fortran nad Markdown with conditional sectionsalbert-github2019-08-171-1/+3
|/ | | | | | | | | | | | | | | | In case of a construct like (Markdown, analogous for Fortran): ``` test text @cond: after cond whatever @endcond some more text ``` we get a `*/` after `test text` that should not be present. Other places exclude besides Pyton and VHDL also Fortran and Markdown and that should happen here as well.
* issue #7190 1.8.16: Blank FILE_PATTERNS => no files processedalbert-github2019-08-132-3/+10
| | | | This is actually a regression on #7195. Due to the fact that the init() routine has moved up, the settings for `FILE_PATTERNS` have already been done and a call to init does not operate on the `FILE_PATTERNS` variable but on the structure from which the `FILE_PATTERNS` was derived. We have should here operate on the `FILE_PATTERNS` directly as well., bu getting the default values out of the underlying structure.
* Reduce boilerplate code by using C++11 variadic templates and perfect forwardingDimitri van Heesch2019-08-113-281/+32
|
* Problem with '<td nowrap>'albert-github2019-08-103-1/+11
| | | | | | In the docbook ouput this was shown with the attribute `nowrap>=''`, in HTML this empty tag was skipped. Normally a HTML attribute will have a value but in some cases it is possible without attribute and when this is the last attribute the `>` was accidently added to the attribute (in case of the value the `>` was already considered). Furthermore `In XHTML, attribute minimization is forbidden, and the nowrap attribute must be defined as <td nowrap="nowrap">.`, this is now handled for HTML and docbook as well.
* Merge branch 'master' of github.com:doxygen/doxygenRelease_1_8_16Dimitri van Heesch2019-08-081-5/+5
|\
| * Fixing redirection linksalbert-github2019-08-081-5/+5
| | | | | | | | | | Fixing a number of redirecting links in the doxygen documentation. (Note the redirects from http://www.doxygen.org to http://www.doxygen.nl are not corrected)
generated by cgit v0.12 at 2024-11-20 02:30:42 (GMT)