summaryrefslogtreecommitdiffstats
path: root/src/configimpl.l
Commit message (Collapse)AuthorAgeFilesLines
* issue #8343 doxygen-1.9.1 crashes when parsing config file (part 2)albert-github2021-01-191-3/+2
| | | | | - In the past in case of a quoted string there was a space at the end of the string (as also indicated in the comment), now this space is gone so the `wasQuoted` would not kick in. A string with an escaped double quote should be / has to be escaped so it should also be included in the `wasQuoted` - missing one `data()` -> `str()` (should not give a problem due to the guard, but better for consistency).
* issue #8343: doxygen-1.9.1 crashes when parsing config fileDimitri van Heesch2021-01-181-6/+6
|
* issue #8297 fails to parse list of INPUT filesalbert-github2021-01-021-1/+1
| | | | The rule also caught a `\n` at the second position.
* issue #8282 Error on ALIAS declaration without quotesalbert-github2020-12-291-1/+1
| | | | | - also escape a "," (comma) when writing out string values (doxygen and doxywizard) - check on empty lists in stringlist for the wizard
* Refactoring: removed some dead codeDimitri van Heesch2020-12-251-2/+0
|
* Refactoring: better processing of (un)quoted values for tags in the ↵Dimitri van Heesch2020-12-251-46/+46
| | | | configuration file (part 2)
* Refactoring: better processing of (un)quoted values for tags in the ↵Dimitri van Heesch2020-12-241-318/+427
| | | | configuration file
* Silently ignoring unexpected characters in configurationalbert-github2020-11-181-1/+1
| | | | Should also ignore `\r` as white space
* Silently ignoring unexpected characters in configurationalbert-github2020-11-181-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | When having a doxygen configuration file like: ``` QUIET=YES @INPUT = file @UNKNOWN = @UNKNOWN1 @UNKNOWN 1 @UNK # test ``` we get the warnings ``` warning: ignoring unsupported tag 'UNKNOWN' at line 3, file Doxyfile warning: ignoring unknown tag 'UNKNOWN1' at line 4, file Doxyfile warning: ignoring unknown tag 'UNKNOWN' at line 5, file Doxyfile warning: ignoring unknown tag '1' at line 5, file Doxyfile warning: ignoring unknown tag 'UNK' at line 6, file Doxyfile # Difference with default Doxyfile 1.9.0 (fa65bb38f81457d00f9c900bb57eb68bea59b1b4) QUIET = YES INPUT = file ``` especially the missing of a warning about the `@` in `@INPUT` can be a bit misleading (it might be that the user wanted to use `@INCLUDE` and and specified `@INPUT` It would be better to have a warning about a not handled character instead of just ignoring it.
* Merge pull request #8128 from albert-github/feature/bug_configDimitri van Heesch2020-11-061-41/+61
|\ | | | | Incorrect handling of string with spaces and no quotes
| * Incorrect handling of string with spaces and no quotesalbert-github2020-10-251-1/+0
| | | | | | | | Correcting some (Cygwin) compilation warnings / errors
| * Incorrect handling of string with spaces and no quotesalbert-github2020-10-251-40/+61
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | During some tests on the documentation of LLVM the (CMake generated) doxygen configuration file contained the line: ``` DOT_PATH=D:\Program Files (x86)\Graphviz2.38\bin\dot.exe ``` and this was interpreted by doxygen as ``` DOT_PATH = D:\ProgramFiles(x86)\Graphviz2.38\bin\dot.exe ``` without any message other than that later on the `dot` executable could not be found. It is clear that here the double quotes were missing. This problem has been solved by giving a warning and setting the value to the default value. - configimpl.l - config_doxyw.l during the checking some debug facilities for the doxywizard were required and this has been implemented: - config_doxyw.l - doxywizard.h - doxywizard.cpp it was also discovered that in case of none existing int or bool values were specified the wrong "defaults" were taken (it was set to `0` / `false`), now the correct defaults are taken - inputbool.cpp - inputint.cpp
* | Problem with `\\` at end of an ALIASES in the configuration filealbert-github2020-10-301-0/+3
|/ | | | | In principle a configuration file should not know anything about the doxygen commands, but the handling of the escaped `\` and `@` are an exception of this rule (especially in `ALIASES`). The mentioned escaped characters were not handled properly.
* issue #7951: Doxywizard 1.8.19 (Windows): Source code directory seems to be ↵Dimitri van Heesch2020-08-101-2/+2
| | | | ignored
* Merge branch 'feature/bug_chm_tests' of ↵Dimitri van Heesch2020-08-011-0/+8
|\ | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_chm_tests
| * Creating chm files for doxygen testsalbert-github2020-05-301-0/+5
| | | | | | | | | | | | | | By means of `nmake tests TEST_FLAGS="--xhtml --keep --cfg GENERATE_HTMLHELP=YES --cfg HHC_LOCATION=C:/PROGRA~2/HTMLHE~1/hhc.exe --cfg SEARCHENGINE=NO" it is possible to generate for each doxygen test an index.chm, but there are a number of problems: - it is only possible to use extension `.html` so this is now automatically done (configimpl.l) otherwise when opening the file an error is displayed. - it is not [possible to use "empty" hhc / hhk file (i.e. no `<li>` elements), in this case the files are still generated but not used anymore (error like `error: failed to run html help compiler on index.hhp` e.g. for test 1). - a full qualified / absolute is not allowed for e.g msc images (test 37) the files should anyway be on the "html" directory so just using the filename in the "hhp" file (` t << QFileInfo(imageFiles.at(i)).fileName().data() << endl;`)
* | Prevent potential empty stringDimitri van Heesch2020-06-061-1/+1
| |
* | issue #7833 Empty string in PREDEFINED throwsalbert-github2020-06-061-1/+1
| | | | | | | | Ignore empty strings
* | Refactor: modernize configuration valuesDimitri van Heesch2020-06-041-294/+268
| |
* | Empty enum setting in configuration filealbert-github2020-05-291-0/+5
|/ | | | | | | | | | | | | | In case we have an empty setting in the doxygen configuration file, where an enum value is expected like: ``` OUTPUT_LANGUAGE = ``` we get the warning: ``` warning: argument '(null)' for option OUTPUT_LANGUAGE is not a valid enum value Using the default: English! ``` The default value should immediately have been used.
* Merge branch 'remove_tcl'Dimitri van Heesch2020-03-221-3/+0
|\
| * Remove support for TCL (code is too buggy and unmaintained, language not ↵Dimitri van Heesch2020-03-151-3/+0
| | | | | | | | very popular)
* | Remove last QThread-ReferenceMoritz 'Morty' Strübe2020-03-211-3/+3
| |
* | Doxygen version information (#7645)albert-github2020-03-171-6/+2
|/ | | | | - add doxygen version to rtf, comment, output - remove duplicate code (getFullVersion) - more clear name to get doxygen version (getVersion becomes getrDoxygenVersion). Also to overcomecofusion with the version information for files.
* Enabled stricter compiler warnings and fixed all new warningsDimitri van Heesch2020-03-081-149/+162
|
* Problem in case using PREDEFINED with comma and using +=albert-github2020-02-271-1/+8
| | | | In pull request #7603 the problem regarding `PREDEFINED = A(x,y)`, but the same patch must be applied to the construct `PREDEFINED += A(x,y)`
* Problem in case using PREDEFINED with commaalbert-github2020-02-201-5/+24
| | | | | | | | | | | | | | | | | | | | | | In the pull request "Enable comma as separator in configuration lists enhancement " (#6563) it was made possible to have commas as separators for lists. In case we have: ``` PREDEFINED = A(x,y)=sin(x),cos(y) ``` and use `doxygen -x` (or usethe define): this results in: ``` PREDEFINED = A(x \ y)=sin(x) \ cos(y) ``` this can be overcome by means of: ``` PREDEFINED = "A(x,y)=sin(x),cos(y)" ``` But for a lot of existing packages this poses a problem. (Found by looking at the doxygen configuration files as used by Fossies).
* Unknown configuration enum valuesalbert-github2020-02-131-0/+19
| | | | | | | | | | | | In case we set for instance `DOT_IMAGE_FORMAT = SVG` (and generate call graphs) we get messages from the `dot` tool like: ``` error: Problems running dot: exit code=1, command='dot', arguments='".../example/html/test_8cpp_a764ac60c654173eb1a0afd0906ad5a12_icgraph.dot" -TSVG -o ".../example/html/test_8cpp_a764ac60c654173eb1a0afd0906ad5a12_icgraph.SVG"' ``` on other places (e.g `HTML_FORMULA_FORMAT`) and an unknown or enum value with a wrong case, the default value is (silently) taken. We now check: - is the enum value of the correct case otherwise (silently) set it to the correct case. - in case of an unknown enum value a warning is given and the default value is used
* Fix compiler warnings on Windows (Visual Studio)Dimitri van Heesch2020-02-121-0/+3
|
* Adding check on configuration setting EXTENSION_MAPPINGalbert-github2019-12-281-0/+3
| | | | In #7419 the EXTENSION_MAPPING test was omitted
* Removed exitCode parameter as it is always 1Dimitri van Heesch2019-12-221-23/+23
|
* Merge branch 'feature/bug_terminate' of ↵Dimitri van Heesch2019-12-221-42/+31
|\ | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_terminate
| * Better termination messagealbert-github2019-11-221-42/+31
| | | | | | | | | | In case a `WARN_LOGFILE` is used it in this file no clear whether doxygen finished correctly or exited beforehand in case a fatal error. Now a 'Exiting...' is also given in the warning log file in case an error is a fatal error.
* | Reduced code duplicationDimitri van Heesch2019-12-211-148/+37
| |
* | Merge branch 'feature/bug_config' of ↵Dimitri van Heesch2019-12-201-3/+183
|\ \ | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_config
| * | Checking of right usage of configuration list itemsalbert-github2019-11-251-3/+183
| |/ | | | | | | In case of a configuration list item has an equal sign in it ('=') some extra restriction are imposed / made more understandable.
* | Renamed Portables to PortableDimitri van Heesch2019-12-081-8/+8
| |
* | Refactoring of portable.h and portable.cpp functions to be contained in a ↵Tobias Off2019-11-281-8/+8
|/ | | | | | namespace Fixing some memory issues caused by not correctly freed pointers
* Incorrect warning for ALIASESalbert-github2019-10-051-1/+1
| | | | | | | | 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.
* Reduce the use of QString in favor of the more efficient QCStringDimitri van Heesch2019-09-211-5/+4
|
* Merge branch 'feature/bug_consistency_state_2' of ↵Dimitri van Heesch2019-09-121-0/+3
|\ | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_consistency_state_2
| * Consistent way to show scanner statealbert-github2019-09-051-0/+3
| | | | | | | | | | 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.
* | Refactoring code for dot related source filesDimitri van Heesch2019-09-101-0/+27
|/
* issue #7190 1.8.16: Blank FILE_PATTERNS => no files processedalbert-github2019-08-131-3/+9
| | | | 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.
* Merge pull request #7095 from albert-github/feature/bug_config_consistDimitri van Heesch2019-08-061-80/+81
|\ | | | | Consistency of configuration parameters
| * Consistency of configuration parametersalbert-github2019-07-011-80/+81
| | | | | | | | | | | | | | | | Configuration parameters were used 2 forms in the code bare name like `PAPER_TYPE` and as string `"PAPER_TYPE"`. In case of a non existing "bare name" (or misspelling) this is signaled by the compiler but in case of the string this was only shown at runtime. In case of the usage of an obsolete configuration parameter the "bare name" was signaled as not existing (anymore). The essential change here is the place where the ConfigValues are initialized.
* | Merge branch 'feature/bug_endblock_msg' of ↵Dimitri van Heesch2019-08-041-28/+28
|\ \ | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_endblock_msg
| * | Correction warning messagealbert-github2019-06-011-28/+28
| | | | | | | | | | | | Consistency
* | | Merge branch 'feature/bug_gitversion' of ↵Dimitri van Heesch2019-07-301-2/+7
|\ \ \ | |_|/ |/| | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_gitversion
| * | Show git version informationalbert-github2019-05-311-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
generated by cgit v0.12 at 2024-08-20 10:16:54 (GMT)