summaryrefslogtreecommitdiffstats
path: root/src/docparser.cpp
Commit message (Collapse)AuthorAgeFilesLines
* More indicative warning for wrong nesting of sectionsalbert-github2020-02-081-3/+3
| | | | In case we have a "*section" outside the hierarchy it is useful also have the id of the misbehaving "*section" even though line numbers are given , they might be misleading.
* More accurate warning message.albert-github2020-01-301-1/+1
| | | | | | | | | | | in code like `this command @unkn` would give (whilst all information is present) ``` warning: Found unknown command '\unkn' ``` instead of ``` warning: Found unknown command '@unkn' ```
* Adding commands `\rtfinclude`, `\docbookinclude`, `\maninclude` and ↵albert-github2020-01-091-2/+16
| | | | | | `\xmlinclude` Adding for consistency with `\*only`, `\htmlincclude` and `\latexinclude` the commands: `\rtfinclude`, `\docbookinclude`, `\maninclude` and `\xmlinclude`
* Replaced \_fakeform by \_formDimitri van Heesch2019-12-261-2/+2
|
* Merge branch 'feature/bug_formula' of ↵Dimitri van Heesch2019-12-261-2/+2
|\ | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_formula
| * Better warning in case of `@form`albert-github2019-11-061-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When having a problem like: ``` /** \file */ /** * The fie * * @form: the new format * @content: the content of the form * * Sets @form content to be @content. * * \f$ \alpha \f$ \f[ \beta \f] */ void fie(char *form, char *content); ``` we get warnings like: ``` .../aa.h:5: warning: Wrong formula id -1 .../aa.h:6: warning: Found unknown command '\content' .../aa.h:8: warning: Wrong formula id -1 .../aa.h:8: warning: Found unknown command '\content' ``` The `@form:` is in RST analogue to the doxygen `@param form` but not understood by doxygen. The result is that it is seen as an formula as doxygen translates the formula commands to `\form`. For `@content` is handled properly as this is not a doxygen command. In this patch a more unique name is chosen so these type of conflicts don't appear (that easy). The resulting, better, warnings are now: ``` .../aa.h:5: warning: Found unknown command '\form' .../aa.h:6: warning: Found unknown command '\content' .../aa.h:8: warning: Found unknown command '\form' .../aa.h:8: warning: Found unknown command '\content' ```
* | Merge branch 'feature/bug_html_s' of ↵Dimitri van Heesch2019-12-261-1/+17
|\ \ | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_html_s
| * | Adding HTML s tag, XML corrections for other tagsalbert-github2019-08-161-1/+17
| | | | | | | | | | | | | | | | | | Adding the HTML `<s>` tag (https://www.w3schools.com/tags/tag_s.asp). Adding 's' and correcting 'inc' to 'ins' in compound.xsd
* | | Minor tweaksDimitri van Heesch2019-12-251-3/+4
| | |
* | | Merge branch 'feature/bug_style_change' of ↵Dimitri van Heesch2019-12-251-64/+70
|\ \ \ | | | | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_style_change
| * \ \ Merge branch 'master' into feature/bug_style_changeDimitri van Heesch2019-12-251-90/+99
| |\ \ \
| * | | | Warning with XML / HTML style commandsalbert-github2019-10-201-64/+70
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When having a problem like: ``` /// set <var> var start_interp </em> void fie(void); /// set <i> i start_interp void fie1(void); ``` we get the warnings (doubles omitted): ``` .../bb.h:5: warning: end of comment block while expecting command </em> ``` so - discrepancy between `<var>` and closing `</em>` is not reported, but wrong for as opening and closing tag should have the same tag name. - the missing `</i>` is reported as a missing `</em>` The problems here are due to the fact that `<var>`, `<i>` and `<em>` share all the style `HTML_EMPHASIS`, this problem has been fixed by adding the used tag name to the style information and testing o n the name and not the style type. The result is now: ``` .../bb.h:1: warning: found </em> tag while expecting </var> .../bb.h:2: warning: end of comment block while expecting command </var> .../bb.h:5: warning: end of comment block while expecting command </i> ``` so now the real problems are reported.
* | | | | Fixed compiler warnings in docparser.cppDimitri van Heesch2019-12-231-4/+4
| |/ / / |/| | |
* | | | Merge branch 'master' into spellingDimitri van Heesch2019-12-231-39/+37
|\ \ \ \
| * \ \ \ Merge pull request #7211 from albert-github/feature/issue_7210Dimitri van Heesch2019-12-231-32/+30
| |\ \ \ \ | | | | | | | | | | | | issue #7210: 1.8.16: Image inclusion is inconsistent
| | * | | | issue #7210: 1.8.16: Image inclusion is inconsistentalbert-github2019-08-201-32/+30
| | | |/ / | | |/| | | | | | | | | | | | | | | | | The consequence of #7084 (Missing warning about ambiguous files) was that in case a file was ambiguous only a message was given. Now a warning is given plus one of the ambiguous files is used (might be the wrong one).
| * | | | Merge branch 'feature/bug_unsupported_html' of ↵Dimitri van Heesch2019-12-181-1/+1
| |\ \ \ \ | | | | | | | | | | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_unsupported_html
| | * | | | Output of unknown xml/html tagalbert-github2019-11-061-1/+1
| | | |_|/ | | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When having a problem like: ``` /** \file - Just name <name> - name plus subname <name subname> - name plus twice subname <name subname subname> - name plus subname subname="" <name subname subname=""> */ ``` we get correctly the warnings: ``` .../aa.h:3: warning: Unsupported xml/html tag <name> found .../aa.h:4: warning: Unsupported xml/html tag <name> found .../aa.h:5: warning: Unsupported xml/html tag <name> found .../aa.h:6: warning: Unsupported xml/html tag <name> found ``` but the output doesn't look good as there is `=""` added: ``` Just name <name> name plus subname <name subname=""> name plus twice subname <name subname="" subname=""> name plus subname subname="" <name subname="" subname=""> ``` This patch fixes this output.
| * | | | Fix logic bug in SVG detectionDimitri van Heesch2019-12-141-1/+1
| | | | |
| * | | | Renamed Portables to PortableDimitri van Heesch2019-12-081-5/+5
| | | | |
| * | | | Refactoring of portable.h and portable.cpp functions to be contained in a ↵Tobias Off2019-11-281-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | namespace Fixing some memory issues caused by not correctly freed pointers
* | | | | spelling: embeddingJosh Soref2019-11-121-2/+2
|/ / / /
* | | | Merge branch 'feature/bug_warn_illegal_command' of ↵Dimitri van Heesch2019-11-101-6/+12
|\ \ \ \ | | | | | | | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_warn_illegal_command
| * | | | Better warning message in case of illegal commandalbert-github2019-11-061-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Correcting compilation errors and warnings like: ``` error: invalid conversion from ‘const char*’ to ‘char*’ [-fpermissive] char *cmd_start = (tok==TK_COMMAND_AT ? "@" : "\\"); warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings] char *cmd_start = "\\"; ```
| * | | | Better warning message in case of illegal commandalbert-github2019-11-061-6/+12
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When having a problem like: ``` /** \file * * \link Something \see nothing2 \endlink * * \link Something @see nothing3 \endlink */ ``` We will get a.o. the warnings: ``` .../aa.h:3: warning: Illegal command see as part of a \link .../aa.h:5: warning: Illegal command see as part of a \link ``` it is not clear what the problem is. With this patch we get a little bit clearer warning: ``` .../aa.h:3: warning: Illegal command \see as part of a \link .../aa.h:5: warning: Illegal command @see as part of a \link ```
* | | | Spelling corrections for src directoryalbert-github2019-11-051-1/+1
|/ / / | | | | | | | | | | | | | | | | | | | | | Spelling corrections as found by codespell and in #561. Some reported problems were already fixed, others are fixed here, with some exceptions (a,o.): - "referenceby" in defgen.cpp as this is in the output and I cannot oversee the consequences (looks like none, but ...) - "HANGEUL_CHARSET" left as is as in some MS documentation is written: 'HANGUL_CHARSET: Also spelled "Hangeul". Specifies the Hangul Korean character set.' (https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-wmf/0d0b32ac-a836-4bd2-a112-b6000a1b4fc9).
* | | Merge pull request #7323 from albert-github/feature/bug_empty_html_tagDimitri van Heesch2019-11-021-18/+26
|\ \ \ | | | | | | | | Skip empty HTML tag
| * | | Skip empty HTML tagalbert-github2019-10-151-18/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Due to the fact that an empty HTML tag (like `<strike/>` is seen as a start tag the rest of a documentation block is handled with the strikethrough. Same problem occurs for other tags as well, in most cases empty HTML tags should be left out of the output (and just give the warning about the empty tag). Mentioned example: ``` /** Before a strike: <strike/> after strike */ void fie_b_strike(void); ```
* | | | Merge branch 'master' into feature/bug_param_missing_warnDimitri van Heesch2019-11-011-24/+20
|\ \ \ \
| * \ \ \ Merge branch 'std'Dimitri van Heesch2019-10-271-19/+14
| |\ \ \ \ | | |_|_|/ | |/| | |
| | * | | Changed ArgumentList to be an STL containerDimitri van Heesch2019-10-271-19/+14
| | |/ /
| * | | Support for <a id="label">albert-github2019-10-161-1/+1
| |/ / | | | | | | | | | Support besides `<a name="label">` also `<a id="label">` as `id=` is the HTML attribute to define an ad for an HTML element.
| * | Warning when using empty HTML tagalbert-github2019-10-141-3/+4
| | | | | | | | | | | | | | | | | | - 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>`)
| * | Warning when using empty p HTML tagalbert-github2019-10-121-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | Nicer warning for missing parameteralbert-github2019-09-301-5/+7
|/ / | | | | | | In case of just 1 missing parameter use the singular form (checking was already done, now we just count).
* | Reduce the use of QString in favor of the more efficient QCStringDimitri van Heesch2019-09-211-5/+9
| |
* | issue #7216: non-const getGroupDef() called on aliased member (cleanup + ↵Dimitri van Heesch2019-08-261-3/+2
|/ | | | null pointer fix)
* spelling error: suported -> supportedJoenio Costa2019-08-081-1/+1
|
* Merge pull request #7042 from albert-github/feature/bug_632754Dimitri van Heesch2019-08-071-1/+2
|\ | | | | Bug 632754 - The \copydoc Command Requires The Use of C++ Syntax in C# Code
| * Bug 632754 - The \copydoc Command Requires The Use of C++ Syntax in C# Codealbert-github2019-06-071-1/+2
| | | | | | | | Replace the scope separators to the default scope separators (::) of doxygen.
* | Merge pull request #7084 from albert-github/feature/bug_img_ambigDimitri van Heesch2019-08-071-14/+17
|\ \ | | | | | | Missing warning about ambiguous files
| * | Missing warning about ambiguous filesalbert-github2019-06-271-14/+17
| |/ | | | | | | | | - Handling of ambiguous files (in case of an ambiguous file `fd` does return a value) - using correct dictionary for warning
* | Merge branch 'feature/bug_endblock_msg' of ↵Dimitri van Heesch2019-08-041-16/+16
|\ \ | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_endblock_msg
| * | Correction warning messagealbert-github2019-06-011-13/+13
| |/ | | | | | | Consistency
* | Merge branch 'feature/issue_6831' of ↵Dimitri van Heesch2019-08-041-5/+13
|\ \ | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/issue_6831
| * | issue #6831 Failure to recognize class array with PHP in @varalbert-github2019-02-151-3/+19
| | | | | | | | | | | | | | | | | | | | | | | | There are 2 different situations here: - @var, here a special change is necessary to check and handle whether or not we are in PHP (declinfo.*, doxygen.cpp) - @param - the type recognition for the PHP type has to be extended with the `[]` possibility and subsequently the `[]` part has to be handled separately from the 'datatype' (doctokinizer.l, docparser.*). - In the output we now can have multiple text strings resulting in a small change in handling of the separator between the data type (*docvisitor.*)
* | | Merge branch 'fetaure/bug_html_ins_del_tag' of ↵Dimitri van Heesch2019-08-031-0/+34
|\ \ \ | | | | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-fetaure/bug_html_ins_del_tag
| * | | Adding HTML tags ins and delalbert-github2019-04-041-0/+34
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Github does not support the `<u>` tag for underlined text, in HTML there exists the tag `<ins>`. On https://www.w3schools.com/tags/tag_ins.asp is written: The `<ins>` tag defines a text that has been inserted into a document. Browsers will normally strike a line through deleted text and underline inserted text. Most browsers will display the `<ins>` element with the following default values: ``` ins { text-decoration: underline; } ``` analogous there exists the tag `<del>` (https://www.w3schools.com/tags/tag_del.asp): The `<del>` tag defines text that has been deleted from a document. Browsers will normally strike a line through deleted text and underline inserted text. Most browsers will display the `<del>` element with the following default values: ``` del { text-decoration: line-through; } ``` Definitions analogue to the underline and strike through tag the implementation for the other formats has been chosen.
* | | | issue 7068: "QGDict::hashAsciiKey: Invalid null key" error messages (part 5)Dimitri van Heesch2019-08-031-1/+1
| | | |
* | | | issue 7068: "QGDict::hashAsciiKey: Invalid null key" error messages (part 3)Dimitri van Heesch2019-08-011-29/+62
| | | |
generated by cgit v0.12 at 2024-11-16 00:08:20 (GMT)