summaryrefslogtreecommitdiffstats
path: root/src/util.cpp
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #7377 from albert-github/feature/bug_spell_srcDimitri van Heesch2019-11-061-1/+1
|\ | | | | Spelling corrections for src directory
| * 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).
* | issue #7302: Determination of anonymous is too restrictiveDimitri van Heesch2019-11-051-1/+1
|/
* Replaced QList<ListItemInfo> with std::vector<ListItemInfo>Dimitri van Heesch2019-10-291-12/+10
|
* Replaced QList<SectionInfo> by std::vector<SectionInfo>Dimitri van Heesch2019-10-291-1/+0
|
* Embed TagInfo struct inside EntryDimitri van Heesch2019-10-281-1/+1
|
* Merge pull request #7341 from ellert/source-date-yearDimitri van Heesch2019-10-281-3/+9
|\ | | | | Let $year support SOURCE_DATE_EPOCH
| * Let $year support SOURCE_DATE_EPOCHMattias Ellert2019-10-191-3/+9
| |
* | Changed ArgumentList to be an STL containerDimitri van Heesch2019-10-271-403/+247
|/
* Problem with round brackets in PS outputalbert-github2019-10-091-0/+20
| | | | | | | | | | | 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 #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-171-1/+2
|\ | | | | Warning with xrefitem from documentation
| * Warning with xrefitem from documentationalbert-github2019-09-131-1/+2
| | | | | | | | | | | | | | | | | | | | 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 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)
* Refactoring code for dot related source filesDimitri van Heesch2019-09-101-3/+3
|
* 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 #7216: non-const getGroupDef() called on aliased memberDimitri van Heesch2019-08-251-2/+0
|
* issue #7147: No warning when same page createdalbert-github2019-08-071-0/+2
| | | | Creating warning when adding documentation to an already existing page.
* Merge pull request #7042 from albert-github/feature/bug_632754Dimitri van Heesch2019-08-071-0/+5
|\ | | | | 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-0/+5
| | | | | | | | Replace the scope separators to the default scope separators (::) of doxygen.
* | Some fixes and restructuringDimitri van Heesch2019-08-061-0/+70
| | | | | | | | | | | | - moved unescapeCharsInString to util.cpp - restructured flow keyword counting - make flow keyword counting work for python and fortran code as well
* | Merge branch 'feature/bug_endblock_msg' of ↵Dimitri van Heesch2019-08-041-62/+62
|\ \ | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_endblock_msg
| * | Correction warning messagealbert-github2019-06-011-62/+62
| |/ | | | | | | Consistency
* | issue 7068: "QGDict::hashAsciiKey: Invalid null key" error messages (part 2)Dimitri van Heesch2019-07-311-0/+4
| |
* | Merge branch 'feature/bug_gitversion' of ↵Dimitri van Heesch2019-07-301-1/+1
|\ \ | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_gitversion
| * | Show git version informationalbert-github2019-05-311-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The original version has as features: - getting the git version number for usage in doxygen - making the doxygen version number inclusion dependent on the VERSION file The disadvantage of the chosen methodology was that an extra correction step was necessary, by defining getter methods to retrieve the values this correction can be hidden. The information is coming from different sources: - the VERSION file - the git "repository and build system (when present) Furthermore there are a couple of places where the version information is used (a.o. doxygen and doxywizard executable, though the doxygenwizard was only done "half hearted") The handling of the VERSION file has been made in such a way that it is comparable with the generation of the git version changes. For a better abstraction the version handling is all done in a separate directory.
* | | Improved constness and avoid using non-const members of aliasesDimitri van Heesch2019-07-291-29/+31
| | |
* | | Some code simplificationsDimitri van Heesch2019-07-291-4/+3
| | |
* | | Merge branch 'feature/issue_6950' of ↵Dimitri van Heesch2019-07-291-3/+9
|\ \ \ | | | | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/issue_6950
| * | | issue #6950 XML - <initializer> for array of structure only contains ↵albert-github2019-05-011-3/+9
| | | | | | | | | | | | | | | | | | | | | | | | references in first array element Don't stop at a hexadecimal number, but output the hexadecimal number (plus the part that has not been printed yet) and continue with the next input part.
* | | | issue #7120 Markdown generator does not consider extension mapping for files ↵albert-github2019-07-121-12/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | with no extension Better handling of the determination of what is an extension. - don't see a file references like: `./LICENSE` as extension - use the qt way of extension determination and in case of no extension use the no extension placeholder for it.
* | | | issue #7110 URL Encoding for Hyperlinks in PDFalbert-github2019-07-081-0/+1
| | | | | | | | | | | | | | | | For an URL also the percentage (`%`)sign has to be escaped
* | | | Bug 566109 - unable to resolve links to java functions with array argumentsDimitri van Heesch2019-06-221-0/+1
| | | |
* | | | Merge pull request #7034 from albert-github/feature/issue_7033Dimitri van Heesch2019-06-221-0/+8
|\ \ \ \ | | | | | | | | | | issue #7033 Syntax highlighting doesn't work when calling \dontinclude from Markdown files
| * | | | issue #7033 Syntax highlighting doesn't work when calling \dontinclude from ↵albert-github2019-06-061-0/+8
| | |_|/ | |/| | | | | | | | | | | | | | | | | | Markdown files Don't use the file name extension of the including file but of the included file. In case of no included filename or no extension, fall back of the file extension of the including file.
* | | | Merge branch 'feature/bug_case_sense' of ↵Dimitri van Heesch2019-06-221-6/+6
|\ \ \ \ | | | | | | | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_case_sense
| * | | | Upper case characters in filename despice CASE_SENSE_NAME=NOalbert-github2019-06-171-4/+4
| | | | | | | | | | | | | | | | | | | | In case special characters in a filename need escaping into something like: `_0` the `0` should not be followed by an uppercase character as this would be in contradiction wit the setting `CASE_SENSE_NAMES=NO`.
* | | | | (X)HTML warning when `[` or `]` in constructed idsalbert-github2019-06-161-0/+2
|/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When we have a construct like: ``` template <typename Element, size_t N> class StlContainerView<Element[N]> { public: typedef internal::NativeArray<RawElement> type; }; ``` this will lead to files with `[` and `]` in it, as such not nice, but it is used in ids inside the code as well like: ``` id="aclass_stl_container_view_3_01_element[_n]_4_html_a1bf60158ff15896f2b53af11c09524fb" ``` running ``` xmllint --path ..../testing/dtd --noout --nonet --postvalid html_org/*html ``` this leads to the message: ``` Syntax of value for attribute id of div is not valid Document html_org/test_8h_source.html does not validate ``` escaping the `[` and `]` as done with other special characters solves this problem
* | | | Cygwin should by default also have `CASE_SENS_NAMES=NO`albert-github2019-06-151-2/+2
|/ / / | | | | | | | | | | | | Cygwin should by default also have `CASE_SENS_NAMES=NO` like is the case for the underlying Windows. In case of Cygwin the define `_WIN32` is not set so we also have to test for `__CYGWIN__`
* | | Merge pull request #6913 from albert-github/feature/url_to_md_fileDimitri van Heesch2019-05-121-4/+8
|\ \ \ | | | | | | | | Markdown file as internet link
| * | | Markdown file as internet linkalbert-github2019-04-051-4/+8
| | |/ | |/| | | | | | | | | | | | | | | | | | | See a link in case of a md file only as local link if it doesn't start with a supported protocol. Example found was: ``` [Ansibullbot](https://github.com/ansible/ansibullbot/blob/master/ISSUE_HELP.md) ```
* | | Add const correctness for argument listsDimitri van Heesch2019-05-051-9/+9
| | |
* | | Further const correctness changesDimitri van Heesch2019-05-051-5/+5
| |/ |/|
* | Avoid endless namespace lookup for C# code.Dimitri van Heesch2019-04-271-9/+12
| |
* | Merge pull request #6922 from albert-github/feature/issue_6917Dimitri van Heesch2019-04-211-4/+4
|\ \ | | | | | | issue #6917 Crash in php with UTF-8 character
| * | issue #6917 Crash in php with UTF-8 characteralbert-github2019-04-101-4/+4
| |/ | | | | | | | | | | Problem is that a value is fed to isspace that is not in the correct range and has to be converted to this range. compare also Assertion failure generation documentation (fdefe70a955c8140f080974319bbf97364d3e610 of March 30 2016).
* | Improved const correctness and added support for inline namespacesDimitri van Heesch2019-04-211-86/+85
|/
* Fixed a few compiler warnings on win32Dimitri van Heesch2019-03-101-1/+1
|
* Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2019-02-281-0/+1
|\
| * Latex code double minus goes to endashalbert-github2019-02-221-0/+1
| | | | | | | | | | | | | | In case in code 2 consecutive minus signs are present they are shown as endash. using the same code as in the non code part solves the issue. Issue can e.g. be seen in cpp source code (with e.g. i--) and in the doxygen documentation in the paragraph "Comment blocks in VHDL" This is a regression in 1.8.15
generated by cgit v0.12 at 2024-11-18 05:11:30 (GMT)