summaryrefslogtreecommitdiffstats
path: root/src/doctokenizer.l
Commit message (Collapse)AuthorAgeFilesLines
* 64-bit Windows compiler warnings doctokinizer.lalbert-github2020-11-011-10/+11
| | | | | | | | | | 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`)
* issue #8127 Java: xml output of preformatted (`<pre>`) block adds para-block ↵albert-github2020-10-261-10/+18
| | | | | | 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.
* Miscounting in respect to lists in markdownalbert-github2020-10-161-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Warnings during compilation of doctokinizeralbert-github2020-10-071-1/+1
| | | | | | | | | 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`.
* Minor tweaksDimitri van Heesch2020-10-051-60/+47
| | | | | | - lineCount() without arguments was unused - converted lineCount(...) into a macro with yytext and yyleng as arguments
* Merge branch 'feature/bug_doctok_cnt' of ↵Dimitri van Heesch2020-10-051-10/+85
|\ | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_doctok_cnt
| * Miscounting lines in doctokinizeralbert-github2020-09-201-10/+85
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* | Incorrect recognition as RCS tagalbert-github2020-10-041-1/+2
|/ | | | | | | | | | | | | | | | | | | | 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
* Split lexer rulesDimitri van Heesch2020-09-111-353/+361
| | | | | Also replaced tabs by spaces and removed trailing whitespace And fixed line counting issue.
* issue #8015 Special command \skip and \until no longer functional in ALIASESalbert-github2020-09-071-0/+6
| | | | The pattern `\ilinebr` is actually also a line break, but was not handled.
* Merge branch 'feature/bug_direction' of ↵Dimitri van Heesch2020-07-301-1/+1
|\ | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_direction
| * More flexible and correct detection of direction of an argumentalbert-github2020-06-281-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | 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.
* | And one more fix for \ilinebr handlingDimitri van Heesch2020-07-291-4/+4
| |
* | More fixes regarding \ilinebr handlingDimitri van Heesch2020-07-291-7/+7
| |
* | Fixed typoDimitri van Heesch2020-07-281-1/+1
| |
* | More \ilinebr related cleanup and combined some rulesDimitri van Heesch2020-07-281-29/+19
| |
* | More improvement regarding \\ilinebr handlingDimitri van Heesch2020-07-281-0/+6
| | | | | | | | | | | | - 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
* | Better handling of \\ilinebrDimitri van Heesch2020-07-281-4/+26
| | | | | | | | | | | | | | - 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.
* | Additional tweaks to get markdown tables inside ALIASES workDimitri van Heesch2020-07-271-22/+39
|/ | | | | | | | | | - 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)
* Refactor: modernize markdown and make it thread-safeDimitri van Heesch2020-06-161-7/+9
|
* issue #7747 Three-way comparison operatoralbert-github2020-05-041-1/+1
| | | | Implementation of the C++2x three-way / spaceship operator.
* Refactoring: size_t type conversions and QList in DotManagerDimitri van Heesch2020-05-021-1/+1
|
* Combined both rules in one to reduce code duplicationDimitri van Heesch2020-04-091-6/+1
|
* Link in case of comma at end of URLalbert-github2020-04-081-0/+5
| | | | | | | | | | | | | | | | | | When having a text like: ``` https://storm-irit.github.io/OpenGR/, 2017. ``` the corresponding link will contain the comma as well although this is not intended. The original problem comes from CGAL, where we have a bibliography entry: ``` @misc{ cgal:m-ogr-17, author = {Nicolas Mellado and others}, title = {OpenGR: A C++ library for 3D Global Registration}, howpublished = {https://storm-irit.github.io/OpenGR/}, year = {2017} } ```
* Enabled stricter compiler warnings and fixed all new warningsDimitri van Heesch2020-03-081-5/+11
|
* Restructure section handlingDimitri van Heesch2020-02-211-11/+11
|
* Fix compiler warnings on Windows (Visual Studio)Dimitri van Heesch2020-02-121-0/+3
|
* Consistency `\*only` and `\end*only` commandsalbert-github2020-01-091-0/+8
| | | | | | | | | | | | | | | | | Not all possibilities in respect of `\*only` and `\end*only` commands were present which could lead to messages like: ``` .../aa.h:4: warning: reached end of comment while inside a \rtfonly block; check for missing \endrtfonly tag! ../.aa.h:4: warning: rtfonly section ended without end marker .../aa.h:4: warning: rtfonly section ended without end marker ``` in case of a problem like: ``` /** \file * \rtfonly * RTF /* Nested */ * \endrtfonly */ ```
* Replaced \_fakeform by \_formDimitri van Heesch2019-12-261-3/+3
|
* Merge branch 'feature/bug_formula' of ↵Dimitri van Heesch2019-12-261-3/+3
|\ | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_formula
| * Better warning in case of `@form`albert-github2019-11-061-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-2/+2
|\ \ | | | | | | | | | 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-2/+2
| | | | | | | | | | | | | | | | | | Adding the HTML `<s>` tag (https://www.w3schools.com/tags/tag_s.asp). Adding 's' and correcting 'inc' to 'ins' in compound.xsd
* | | Merge branch 'feature/bug_unsupported_html' of ↵Dimitri van Heesch2019-12-181-3/+5
|\ \ \ | | | | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_unsupported_html
| * | | Output of unknown xml/html tagalbert-github2019-11-061-10/+21
| | |/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | Made regexp more strictDimitri van Heesch2019-12-181-5/+6
| | |
* | | Merge branch 'feature/bug_nospam_email' of ↵Dimitri van Heesch2019-12-181-0/+5
|\ \ \ | | | | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_nospam_email
| * | | Simple nospam email addressalbert-github2019-11-051-0/+5
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When having a simple nospam email address coded like: ``` /** \file * Big Unknown <big at none dot com> */ ``` this results in the warning: ``` aa.c:2: warning: Unsupported xml/html tag <big> found ``` and in the HTML output it looks like: ``` Big Unknown <big at none dot com> ``` instead of: ``` Big Unknown <big at none dot com> ``` (Found in a couple of open source projects).
* | | Renamed Portables to PortableDimitri van Heesch2019-12-081-1/+1
| | |
* | | Merge branch 'memory_leakage_fix' of https://github.com/virusxp/doxygen into ↵Dimitri van Heesch2019-12-081-1/+1
|\ \ \ | | | | | | | | | | | | virusxp-memory_leakage_fix
| * | | Refactoring of portable.h and portable.cpp functions to be contained in a ↵Tobias Off2019-11-281-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | namespace Fixing some memory issues caused by not correctly freed pointers
* | | | Remove bogus flex codeDimitri van Heesch2019-11-181-5/+0
|/ / /
* | | Spelling corrections for src directoryalbert-github2019-11-051-2/+2
|/ / | | | | | | | | | | | | | | 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).
* | HTML attribute namealbert-github2019-09-231-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | Merge branch 'feature/bug_consistency_state_2' of ↵Dimitri van Heesch2019-09-121-0/+2
|\ \ | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_consistency_state_2
| * | Consistent way to show scanner statealbert-github2019-09-051-0/+2
| | | | | | | | | | | | | | | 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.
* | | 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 )
* | | issue #6715: Errorneous matching of the immediately following block command ↵Dimitri van Heesch2019-09-071-2/+2
|/ / | | | | | | after @ref (try 2)
* | issue #7216: non-const getGroupDef() called on aliased member (cleanup + ↵Dimitri van Heesch2019-08-261-10/+4
|/ | | | null pointer fix)
* Problem with '<td nowrap>'albert-github2019-08-101-1/+1
| | | | | | 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.
generated by cgit v0.12 at 2024-09-03 09:34:59 (GMT)