GNOME Bugzilla – Bug 134719
typedefs with same name from different namespaces not resolved correctly
Last modified: 2018-07-30 11:01:01 UTC
If two different namespaces have a typedef of the same name, doxygen ignores all except one of them. Given the following two namespaces: namespace A { typedef float foo_t; static inline void bar_A(foo_t& fooval) { foo_t hi_dad; fooval += 2; } } namespace B { typedef int foo_t; static inline void bar_B(foo_t& fooval) { foo_t hi_mom; fooval *= 2; } } These have nothing in common, other than the foo_t name for a typedef. However, if doxygen is run (using EXTRACT_ALL=YES, SOURCE_BROWSER=YES, and INLINE_SOURCE=YES), a few anomalies are noticed: - B's foo_t has no 'Referenced By' entries (A's foo_t does), and bar_B has no 'References' entries (bar_A does). Presumably related to this, the uses of foo_t in bar_B are not links in the source browser. - The foo_t in bar_B's code gets linked to A's foo_t for the inline code listing. Oddly enough, bar_B does NOT get listed in the 'Referenced By' section of the A::foo_t entry. Note: in the source I originally noticed this behaviour in, the bar_B function (well, its equivalent anyway) DID have a 'References' entry, but it listed A::foo_t. Other types with the same name in multiple namespaces are handled just fine, as evidenced by the results for the above after changing foo_t to a struct (although in that case the inline code does not contain a link for the occurrences of foo_t, which might be another bug).
This also occurs with classes with the same name in different namespaces (or nested namespaces), even if (as templates) they have different template parameters. For example (qick pseudo code) namespace container { /*! * @addtogroup Containers * @{ */ /*! * -- Documentation -- */ template< typename T, class Alloc = alloc::simple_alloc > class array { //... }; /** @} */ // end of Containers } namespace container { namespace fixed { /*! * @addtogroup Fixed_Containers * @{ */ /*! * -- Documentation -- */ template<typename T, size_t N> class array { //... }; /** @} */ // end of Containers }} In the generated documentation, the same class (array< T, Alloc >) is displayed in both documentation groups, rather than the each different classes. Interestingly no warnings or errors are generated when building the documentation. I have gotten around this by calling the second class farray, but I really don't like altering the code based to make the documentation tool work! :) This is occuring in v. 1.5.3
Both test cases work for me without problems (doxygen 1.5.3 for Windows).
As discussed in https://github.com/doxygen/doxygen/pull/734 , Doxygen has moved its issue tracking to https://github.com/doxygen/doxygen/issues All Doxygen tickets in GNOME Bugzilla have been migrated to Github. You can subscribe and participate in the new ticket in Github. You can find the corresponding Github ticket by searching for its Bugzilla ID (number) in Github. Hence I am closing this GNOME Bugzilla ticket. Please use the corresponding ticket in Github instead. Thanks a lot!