Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Bug 652086 - does ALIAS work for VHDL code? | albert-github | 2017-06-04 | 1 | -13/+57 |
| | | | | | Terminating of the VHDL comment was not found as a result of the test against python. Added handling of end of python '#' comment and VHDL '--!' comment | ||||
* | flex: use %option instead of command line options. | Adrian Negreanu | 2016-09-21 | 1 | -0/+2 |
| | |||||
* | Bug 767171 - ALIASES stop working after verbatim with formula and /** */ | albert-github | 2016-06-05 | 1 | -3/+3 |
| | | | | | | | A formula should not not end a "verbatim" type of block. A "verbatim" type of block should only stop at the corresponding end command. In case of a formula with an environment (i.e. f{) the name of the environment can be parsed separately. Corrected end condition for docbookonly. | ||||
* | Bug 752712 - last entry missing in a @name group of typedefs | Dimitri van Heesch | 2016-02-06 | 1 | -0/+6 |
| | |||||
* | Changed configuration mechanism to directly access options in order to ↵ | Dimitri van Heesch | 2016-01-17 | 1 | -3/+3 |
| | | | | improve performance | ||||
* | Markdown with @cond and @endcond | albert-github | 2015-11-22 | 1 | -0/+2 |
| | | | | | In case markdown files are processed and they contain @cond and @endcond these are replaced wit C-style end and begin comments (and code in between is correctly removed). The C-Style comments should not be placed as they are not understood in a markdown context (analogous to what happens in Fortram, Pythone etc.). Note: in principle @cond should not be used as a markdown file is one "comment" block and thus @if should be used, though in any case no unwanted characters should be added. | ||||
* | Bug 752712 - last entry missing in a @name group of typedefs | Dimitri van Heesch | 2015-07-26 | 1 | -0/+8 |
| | |||||
* | drop #include <unistd.h> | Adrian Negreanu | 2015-05-15 | 1 | -3/+2 |
| | | | | Signed-off-by: Adrian Negreanu <adrian.m.negreanu@intel.com> | ||||
* | Bug 746614 - Bogus warning regarding nested comments | albert-github | 2015-03-22 | 1 | -0/+1 |
| | | | | | In case the previous file gives a warning regarding the wrong used nested comments and the next file does not have any doxygen comment there is still the message that there is a nested comment but even without probable line numbers. The variable counting the nested comment level was not reset, this has been corrected with this patch. | ||||
* | Bump copyright year | Dimitri van Heesch | 2015-02-26 | 1 | -1/+1 |
| | |||||
* | Bug 735584 - Reached end of file while still insided a (nested) comment in ↵ | Dimitri van Heesch | 2014-12-19 | 1 | -1/+1 |
| | | | | Markdown | ||||
* | Fixed problem finding \enduml when using /// style comments. | Dimitri van Heesch | 2014-09-26 | 1 | -2/+9 |
| | |||||
* | Bug 731947 - Support for PlantUML | Dimitri van Heesch | 2014-08-10 | 1 | -3/+3 |
| | |||||
* | Updated copyright | Dimitri van Heesch | 2014-02-11 | 1 | -1/+1 |
| | |||||
* | Fixed memory leak in nested comment administration | Dimitri van Heesch | 2014-02-03 | 1 | -4/+4 |
| | |||||
* | Add line numbers in case comment is not closed properly. | albert-github | 2014-01-26 | 1 | -1/+40 |
| | | | | | This bug fix is an extension to the bug fix: Add warning when encountering a nested comment start (/*) without matching end (*/). It is quite hard to find the place in the source file where the problem occurs. This bug fix helps to locate part of the problems, it is not perfect it only gives the starting comment tags that give a problem (other problems also occur e.g. when // is followed by */). | ||||
* | Bug 683115 - Command ignored when using umlauts in markdown and also ↵ | Dimitri van Heesch | 2014-01-08 | 1 | -2/+2 |
| | | | | C-comments in markdown didn't work properly | ||||
* | Add warning when encountering a nested comment start (/*) without matching ↵ | Dimitri van Heesch | 2014-01-08 | 1 | -0/+5 |
| | | | | end (*/). | ||||
* | Bug 721032 - Trouble with /cond /endcond | Dimitri van Heesch | 2013-12-25 | 1 | -1/+1 |
| | |||||
* | Debug output for lexical analyzer | Albert | 2013-11-13 | 1 | -0/+2 |
| | | | | | | | | | | | | | | 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) | ||||
* | Removed redundant backslashes in regexp pattern | Dimitri van Heesch | 2013-11-11 | 1 | -7/+7 |
| | |||||
* | Merge branch 'master' of github.com:doxygen/doxygen | Dimitri van Heesch | 2013-11-11 | 1 | -3/+6 |
|\ | |||||
| * | Bug 711787 - Long initialization line in C stops doxygen | Albert | 2013-11-10 | 1 | -3/+6 |
| | | | | | | | | An extra "breakpoint" in the input string has been created in the form of a , (comma), so for initialization lines the line will be shorter and the , (comma) will be copied later on. | ||||
* | | Bug 711723 - Comment /**/ confuses doxygen | Dimitri van Heesch | 2013-11-11 | 1 | -0/+3 |
|/ | |||||
* | Bug 709706 - Terminating C comments within markdown files breaks aliases | Dimitri van Heesch | 2013-10-12 | 1 | -3/+23 |
| | |||||
* | Bug 701919 - VHDL cross-references fail when unpaired apostrophe present | Dimitri van Heesch | 2013-08-04 | 1 | -1/+4 |
| | |||||
* | Release-1.8.3.1-20130402 | Dimitri van Heesch | 2013-04-02 | 1 | -22/+4 |
| | |||||
* | Release-1.8.3.1-20130324 | Dimitri van Heesch | 2013-03-24 | 1 | -1/+2 |
| | |||||
* | Release-1.8.3.1-20130209 | Dimitri van Heesch | 2013-02-09 | 1 | -2/+2 |
| | |||||
* | Release-1.8.3.1 | Dimitri van Heesch | 2013-01-20 | 1 | -17/+104 |
| | |||||
* | Release-1.8.3 | Dimitri van Heesch | 2012-12-26 | 1 | -17/+30 |
| | |||||
* | Release-1.8.2-20121118 | Dimitri van Heesch | 2012-11-18 | 1 | -15/+9 |
| | |||||
* | Release-1.8.2-20120930 | Dimitri van Heesch | 2012-09-30 | 1 | -6/+35 |
| | |||||
* | Release-1.8.2 | Dimitri van Heesch | 2012-08-11 | 1 | -1/+24 |
| | |||||
* | Release-1.8.1.2-20120729 | Dimitri van Heesch | 2012-07-29 | 1 | -0/+2 |
| | |||||
* | Release-1.8.1.2 | Dimitri van Heesch | 2012-07-12 | 1 | -58/+2 |
| | |||||
* | Release-1.8.1.1 | Dimitri van Heesch | 2012-06-10 | 1 | -2/+3 |
| | |||||
* | Release-1.8.0-20120408 | Dimitri van Heesch | 2012-04-08 | 1 | -1/+8 |
| | |||||
* | Release-1.8.0 | Dimitri van Heesch | 2012-02-25 | 1 | -4/+14 |
| | |||||
* | Release-1.7.6.1-20120220 | Dimitri van Heesch | 2012-02-20 | 1 | -1/+1 |
| | |||||
* | Release-1.7.6.1-20120122 | Dimitri van Heesch | 2012-01-22 | 1 | -51/+51 |
| | |||||
* | Release-1.7.5 | Dimitri van Heesch | 2011-08-14 | 1 | -5/+5 |
| | |||||
* | Release-1.7.4-20110629 | Dimitri van Heesch | 2011-06-29 | 1 | -4/+30 |
| | |||||
* | Release-1.7.3-20110123 | Dimitri van Heesch | 2011-01-23 | 1 | -1/+1 |
| | |||||
* | Release-1.7.3 | Dimitri van Heesch | 2011-01-03 | 1 | -2/+15 |
| | |||||
* | Release-1.7.2-20101118 | Dimitri van Heesch | 2010-11-18 | 1 | -27/+36 |
| | |||||
* | Release-1.7.1-20100822 | Dimitri van Heesch | 2010-08-22 | 1 | -0/+11 |
| | |||||
* | Release-1.7.0 | Dimitri van Heesch | 2010-06-15 | 1 | -1/+3 |
| | |||||
* | Release-1.6.3-20100507 | Dimitri van Heesch | 2010-05-07 | 1 | -3/+15 |
| | |||||
* | Release-1.6.2-20100124 | Dimitri van Heesch | 2010-01-24 | 1 | -1/+1 |
| |