summaryrefslogtreecommitdiffstats
path: root/src/message.cpp
Commit message (Collapse)AuthorAgeFilesLines
* Flush warnings file (#8069)albert-github2020-10-031-0/+6
| | | | | | | | | | | | | | | | | * Flush warnings file When having a large project the warnings file is buffered but when a long time there are no warnings emitted the last warnings are not yet written. During testing tis is most obvious when the `dot` process starts and one needs the `.dot` files but not the converted files at hat moment one wants to kill the doxygen process but the result is an incomplete warnings file of the warnings that should already be written. Created a flush function for the warnings file and placed it at a few strategic points. * Flush warnings file Last minute change without proper testing ( :-( ) * Flush warnings file void is the default changed for consistency and due to (http://www.dietmar-kuehl.de/mirror/c++-faq/newbie.html#faq-29.4): > C programmers often use f(void) when declaring a function that takes no parameters, however in C++ that is considered bad style. In fact, the f(void) style has been called an "abomination" by Bjarne Stroustrup, the creator of C++, Dennis Ritchie, the co-creator of C, and Doug McIlroy, head of the research department where Unix was born.
* Using f() instead f(void) in C++ , consistencyalbert-github2020-10-021-1/+1
| | | | Seen the discussion in the pull request #8069, for consistency change occurrences of f(void) into f().
* issue #7970 Doxygen doesn't stop on errorsalbert-github2020-08-191-0/+14
| | | | Routines doing their own formatting should also stop when `WARN_AS_ERROR` is set.
* New option allowing processing using multiple threadsDimitri van Heesch2020-08-051-10/+0
| | | | | | | | | | | | | | | | | | Introduces new option NUM_PROC_THREADS. It specifies the number threads doxygen is allowed to use during processing. When set to 0 doxygen will based this on the number of cores available in the system. You can set it explicitly to a value larger than 0 to get more control over the balance between CPU load and processing speed. At this moment only the input processing can be done using multiple threads. I plan to extend this with more parallel processing in the future. Since this is still an experimental feature the default is set to 1, which efficively disables parallel processing. Please report any issues you encounter that appear when changing the default. Note that generating dot graphs in parallel is still controlled separately by the DOT_NUM_THREADS setting.
* Compilation warning in debug.cppalbert-github2020-07-061-1/+1
| | | | | | | | | | | | | When compiling debug.cpp on a 32-bit Windows system we get the warning: ``` ...\doxygen\src\debug.cpp(121): warning C4244: 'return': conversion from '_Rep' to 'int', possible loss of data with [ _Rep=__int64 ] ``` as we only use the seconds representation of the elapsed time we can do the conversion to seconds in the Timer class.
* Added experimental multi-thread input processing support.Dimitri van Heesch2020-05-311-9/+33
| | | | | This is disabled by default. It can be enabled by setting MULTITHREADED_INPUT to 1 in doxygen.h. Still has many data races, so don't use for anything other than development!
* RefactoringDimitri van Heesch2020-05-151-15/+2
| | | | | | | | | | | - Makes doxycfg library more self contained - renames _doxygen library to doxymain - Modernizes Debug implementation - Moves Doxygen::runningTime into Debug - Moves full version string to libversion - Removed mentioning of file version in messages (when FILE_VERSION_FILTER is used) - Move substitute functions into QCString
* Replaced FileNameDict/FileNameList by FileNameLinkedMapDimitri van Heesch2020-04-061-1/+1
|
* Fix a number of compiler warnings in the 64bit build for WindowsDimitri van Heesch2020-03-021-1/+1
|
* Fix compiler warnings on Windows (Visual Studio)Dimitri van Heesch2020-02-121-1/+1
|
* Removed exitCode parameter as it is always 1Dimitri van Heesch2019-12-221-16/+2
|
* Merge branch 'feature/bug_terminate' of ↵Dimitri van Heesch2019-12-221-0/+28
|\ | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_terminate
| * Better termination messagealbert-github2019-11-221-0/+28
| | | | | | | | | | 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.
* | Renamed Portables to PortableDimitri van Heesch2019-12-081-1/+1
| |
* | 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
* Fixed segmentation fault in do_warnMatthew Hatch2019-05-081-1/+5
| | | | Copied va_list to avoid reuse causing crash
* Truncated warning messagealbert-github2019-05-061-3/+11
| | | | | | | | | In case of extremely long warning messages (e.g. in case of overloaded methods with a lot of alternatives) the warning message is truncated due to the "limited" buffer size. By using `vsnprintf(NULL, 0, fmt, args)` it is possible to determine the length of the message based on format and actual arguments. `char text[bufSize]` cannot be used as some older compilers don't accept it. (reference: https://stackoverflow.com/questions/3919995/determining-sprintf-buffer-size-whats-the-standard/30909417#30909417)
* Changed configuration mechanism to directly access options in order to ↵Dimitri van Heesch2016-01-171-18/+18
| | | | improve performance
* Reverted change that caused doxygen to return error code 2 when it produced ↵Dimitri van Heesch2015-12-191-5/+6
| | | | a warning
* Add WARN_AS_ERROR option to stop execution at first warning (equivalent of ↵Gautier Pelloux-Prayer2015-12-161-10/+24
| | | | compilers' -Werror option)
* Bug 333106 - $line paramalbert-github2015-07-281-3/+3
| | | | Due to the order of the substitutions the $line was also substituted in the text part. Now the text part is added at the end and the substitution does not take place.
* Guarded debug prints against printing a NULL pointer.Dimitri van Heesch2015-04-061-4/+4
|
* Merge pull request #303 from albert-github/feature/bug_idl_errorDimitri van Heesch2015-03-051-1/+9
|\ | | | | Better error message in case of IDL inconsistency
| * Better error message in case of IDL inconsistencyalbert-github2015-03-041-1/+9
| | | | | | | | | | | | | | | | In case of an IDL internal doxygen inconsistency ("error: Internal inconsistency: namespace in IDL not module, library or constant group ", see forum report: http://doxygen.10944.n7.nabble.com/Internal-inconsistency-Which-file-td7057.html) it is hard to find out which file causes the problem. In this case the comment block with @namespace was the "problem"). This patch solves this by adding the file and line number of the source file causing the problem.
* | Bump copyright yearDimitri van Heesch2015-02-261-1/+1
|/
* Fixed several Coverity warningsDimitri van Heesch2014-11-151-4/+5
|
* Messages truncated in warnings filealbert-github2014-07-301-3/+3
| | | | | | | The current limit for a message length in the messages file is 4095 characters. Most of the time this is more than sufficient, but in case of Fortran and a lot of arguments this might not be sufficient. With Fortran the "data type" can be quite long as it can also includes words like: double precision, dimension, intent(inout) etc. When we have a lot of arguments and just one is described it also tries to write out the names of the non-described parameter/ arguments with the word parameter prepended resulting in an even longer line. This patch increases the size of the buffer.
* Updated copyrightDimitri van Heesch2014-02-111-1/+1
|
* Fixed potential crash caused by overloading the variadic warn functionDimitri van Heesch2014-01-181-1/+1
|
* More work on the template and context mechanismsDimitri van Heesch2013-12-291-2/+7
|
* Fixed constness warningDimitri van Heesch2013-11-171-7/+4
|
* Debug output for lexical analyzerAlbert2013-11-131-0/+28
| | | | | | | | | | | | | | In case of error messages like: input buffer overflow, can't enlarge buffer because scanner uses REJECT it is not always directly clear from which lexical analyzer (.l file) this problem comes. This patch helps to find these problems and does the following things: - when using the option -d lex with doxygen each time a lexical analyzer is called at the start a line like the following line will be given: Entering lexical analyzer: pre.l (for: ..../file.c) and at the end: Finished lexical analyzer: pre.l (for: ..../file.c) - in case the lexical analyzer has been translated with the -d option of lex / flex the above mentioned lines will be given as part of the lexical analyzer output (to stderr) and look like: --entering lexical analyzer: pre.l (for: ..../file.c) --finished lexical analyzer: pre.l (for: ..../file.c)
* Bug 701550 - Error List window in Visual Studio no longer recognizes doxygen ↵Dimitri van Heesch2013-06-041-2/+2
| | | | warnings
* Release-1.8.3.1-20130512Dimitri van Heesch2013-05-121-7/+23
|
* Release-1.8.3.1Dimitri van Heesch2013-01-201-1/+1
|
* Release-1.8.2-20121118Dimitri van Heesch2012-11-181-0/+1
|
* Release-1.7.6.1-20120220Dimitri van Heesch2012-02-201-1/+1
|
* Release-1.7.4Dimitri van Heesch2011-03-281-10/+18
|
* Release-1.7.3-20110123Dimitri van Heesch2011-01-231-1/+1
|
* Release-1.7.1-20100920Dimitri van Heesch2010-09-201-2/+3
|
* Release-1.7.0Dimitri van Heesch2010-06-151-1/+2
|
* Release-1.6.3-20100603Dimitri van Heesch2010-06-031-10/+0
|
* Release-1.6.2-20100124Dimitri van Heesch2010-01-241-1/+1
|
* Release-1.5.9-20090814Dimitri van Heesch2009-08-141-1/+1
|
* Release-1.5.4-20080101Dimitri van Heesch2008-01-171-2/+2
|
* Release-1.5.4Dimitri van Heesch2008-01-161-1/+1
|
* Release-1.5.1-20070219Dimitri van Heesch2007-02-191-1/+1
|
* Release-1.5.1-20070107Dimitri van Heesch2007-01-071-1/+1
|
* Release-1.5.1-20061202Dimitri van Heesch2006-12-021-1/+1
|
* Release-1.4.6-20060507Dimitri van Heesch2006-05-071-1/+1
|
generated by cgit v0.12 at 2024-11-16 00:05:59 (GMT)