| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Javadoc allows comments like this (which I refer to as "banner" comments)
/*****************
*
*****************/
but doxygen does not recognize them.
Instead, the doxygen manual says to do this
/*************//**
*
****************/
which some users aren't even aware is required. It also behaves poorly with clang-format.
I'm proposing to add a Doxyfile boolean option JAVADOC_BANNER which will default to NO. When set to YES, it will consider the first and second comments above to be equivalent.
However, I don't believe that the JAVADOC_BANNER option should default to YES, as there are likely a number of projects who have used the former syntax with full expectation that it would *not* appear in their documentation.
At least having the JAVADOC_BANNER default to NO allows users to opt-in voluntarily by adding JAVADOC_BANNER = YES to their Doxyfile. If the consensus is to make it a default at a later time, first a warning can be added during build that should trigger users to modify their comment style, and then eventually the default could be set to JAVADOC_BANNER = YES, or the config option could be removed entirely and it would just always be enabled.
|
|
|
| |
update flex and bison for the OSX build
|
|\
| |
| | |
issue #6920 Option syntax for commands is unclear
|
| |
| |
| |
| | |
Corrected typo
|
| |
| |
| |
| | |
Making documentation regarding option clearer and more consistent.
|
|\ \ |
|
| | | |
|
| |\ \
|/ / /
| | |
| | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_init_fd_line
|
| |/
| |
| |
| |
| |
| |
| |
| | |
In case thee `line` command is used without previous `\inclide` or `\dontinclude` command doxygen will crash due to a non initialized fd.
We get the message:
warning: No previous '\include' or \dontinclude' command for '\line' present
also a small correcting regarding the warning message is done.
|
|\ \
| | |
| | | |
Warning when preprocessing conditionals
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In case in a `#if` statement a space in the use of a macro is present a warning of the type:
warning: preprocessing issue while doing constant expression evaluation: syntax error
is given. Removing the white space after an ID solves the issue
In the following the first expressing gives a warning whilst the second expression doesn't:
#if (!__GNUC_PREREQ (4, 6))
int i0;
#endif
#if (!__GNUC_PREREQ(4, 6))
int k0;
#endif
|
|\ \ \
| | | |
| | | | |
Create option to enable CLANG_ASSISTED_PARSING in test suite
|
|/ / /
| | |
| | |
| | |
| | |
| | | |
Create possibility to use CLANG_ASSISTED_PARSING, works only when doxygen has been compiled with "use_libclang"
Note at this moment the test suite gives an error, see issue #6948
|
|\ \ \
| | | |
| | | | |
issue #6946 Compilation error (clangparser.cpp)
|
| | | |
| | | |
| | | |
| | | |
| | | | |
corrected clangparser conform other source code in respect to casting.
Corrected doxyapp and doxyparse make scripts for usage with clang parser.
|
|/ / /
| | |
| | | |
add paypal donation button
|
|/ / |
|
| | |
|
|\ \
| | |
| | | |
issue #6939 Build fail in Windows with build_parse turn ON (unistd.h does not exist in Windows)
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
not exist in Windows)
Made doxyparse compilable on Windows.
- removed printNumberOfConditionalPaths as it contained numberOfFlowKeywords() that was removed as dead code in 924cc02d8b7439551508a6301a3b9c762fd2d1bc or Jan 21, 2019.
- corrected casts and prototypes
- corrected include files
- got correct "getpid" for windows.
- corrected calls to OS remove functions by system independent Qt functions
|
|\ \
| | |
| | | |
issue #6917 Crash in php with UTF-8 character
|
| | |
| | |
| | |
| | | |
Also in HTML tag handling.
|
| | |
| | |
| | |
| | |
| | |
| | | |
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).
|
|\ \ \
| | | |
| | | | |
issue #6607 Don't warn about missing parameter documentation for deleted functions
|
| |/ /
| | |
| | |
| | |
| | |
| | | |
functions
Don't emit warnings in case member is deleted.
|
| | | |
|
|\ \ \
| |_|/
|/| | |
Email address not seen
|
|/ /
| |
| |
| |
| |
| | |
In case of an email address like abc@code-factory.org we get the message like:
warning: reached end of file while inside a code block!
due to the fact that the email address contains a '-'.
|
|\ \
| | |
| | | |
Correcting command name in output
|
| |/ |
|
|\ \
| |/
|/| |
Count user comment lines
|
|/
|
|
| |
The user comment lines were not counted resulting in a wrong line number in case of an error message.
|
|\
| |
| | |
issue #6896 empty sections in latex output
|
| |
| |
| |
| | |
In pull request #6832 a fix was made for section captions that ran into the margins. For sections that should not appear in the the TOC (i.e. `*`-ed sections) this led to showing a `*`, this has been corrected.
|
|\ \
| |/
|/| |
Revert "issue #6856 Doxygen only expands macro defined in header file once when referred multiple times"
|
|/
|
|
| |
when referred multiple times"
|
|\
| |
| | |
Correcting errors in xml generation and xsd schema
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- `xmlgen.cpp` make count test identical to restrictions in `generateXMLForMember`
- `index.xsd` add missing selection possibility
- `compound.xsd`
- add missing `block` possibility for htmlonly
- add missing `private` and `protected` possibilities
- get order in description type right
- make `sect[1-4]` more flexible
- adding missing elements like `msc`, `linebreak` at the appropriate places
- adding `vhdl` coloring enumeration values
- adding `docbook` possibility for images
results have been tested (a.o.) doxygen tests, doxygen examples, doxygen docu, CGAL source code.
|
|\ \
| | |
| | | |
issue #6856 Doxygen only expands macro defined in header file once when referred multiple times
|
| | |
| | |
| | |
| | |
| | |
| | | |
referred multiple times
In case the include file is already is already in the global stack it should not be added to the global stack, but still be handled for the current file
|
|\ \ \
| | | |
| | | | |
Add possibility of checking XML against XSD in doxygen tests
|
| | |/
| |/|
| | |
| | | |
Added option `--xmlxsd` to check generated XML files against XSD in the doxygen tests suite.
|
|\ \ \
| |/ /
|/| | |
issue #6892 xml not well-formed (invalid token) for c++
|
|/ /
| |
| |
| | |
the `declname` and `defname` should also be converted (compare as well the routine `generateXMLForMember`)
|
|\ \
| | |
| | | |
issue #6781 Unable to use math in markdown table headers
|
| | |
| | |
| | |
| | |
| | |
| | | |
Due to the change of the place where the markdown processing is done the end of the line must be calculated a little bit differently.
Note: translator.py gave an error due to a strange indentation (did surface now), so had to be corrected as well.
|
|\ \ \
| | | |
| | | | |
Bug 616379 - doxygen result by nested comment incorrectly
|
| | | |
| | | |
| | | |
| | | | |
Improvement on handling `///` comments in relation to `*/` during comment conversion.
|
|\ \ \ \
| | | | |
| | | | | |
Continuation lines and labels
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Better handling of continuation lines when converting from fixed form Fortran to free form Fortran, especially handling the information in columns 733 and further (which is in fixed formatted Fortran always comment)
An `end` statement can start not only on lines with spaces in front of it but also when a line has a label or the `end` can be after a `;`.
|