Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | issue #7635: Incorrect location for enum in XML file (part 2) | Dimitri van Heesch | 2020-03-15 | 1 | -2/+2 |
| | |||||
* | issue #7302: Determination of anonymous is too restrictive | Dimitri van Heesch | 2019-11-05 | 1 | -4/+4 |
| | |||||
* | regression #7061 Rename test file | albert-github | 2019-06-27 | 1 | -0/+0 |
| | | | | | | | | | | Due to a regression on #7061 travis showed message: ``` not ok 71 - [071_enum_in_anon_ns.cpp]: test that enum values in anonymous namespaces produce no warning ------------------------------------- /home/travis/build/doxygen/doxygen/testing/071/namespace_a_namespace_1_1_0d0.xml absent ------------------------------------- ``` | ||||
* | Upper case characters in filename despice CASE_SENSE_NAME=NO | albert-github | 2019-06-17 | 1 | -1/+1 |
| | | | | 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`. | ||||
* | Remove persistent storage of Entry objects | Dimitri van Heesch | 2019-02-17 | 1 | -4/+4 |
| | |||||
* | XML output: avoid warnings with scoped enum values in anonymous namespaces. | Vladimír Vondruš | 2017-12-29 | 1 | -0/+45 |
When a C++11 `enum class` was present in an anonymous namespace (usually in *.cpp files), the XML output was emitting warnings similar to the following: Internal inconsistency: member False does not belong to any container! And the XML output was rendering bogus IDs for enum values starting with `dummy_`, such as: dummy_1a96ab6574751fdf6a53ceec8a3896c45daf8320b26d30ab433c5a54546d21f414c The fix is to call memberOutputFileBase() on the enumeration itself and not on the enum value, that way it provides correct file base that corresponds to file base of the enumeration. There's also a new test that checks this. Note: this assumes that enum values belong to the same compound as enums themselves. In my experience that was always the case and there's no broken test after this change, so I hope I didn't break anything. |