After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 780439 - C# Generic and non-generic classes with the same name generate documentation for only one of them
C# Generic and non-generic classes with the same name generate documentation ...
Status: RESOLVED OBSOLETE
Product: doxygen
Classification: Other
Component: general
1.8.13
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
[moved_to_github]
Depends on:
Blocks:
 
 
Reported: 2017-03-23 10:36 UTC by Piotr Karasinski
Modified: 2018-07-30 10:15 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Config file and source example (3.54 KB, application/x-zip-compressed)
2017-03-23 10:36 UTC, Piotr Karasinski
Details

Description Piotr Karasinski 2017-03-23 10:36:29 UTC
Created attachment 348556 [details]
Config file and source example

When I have two C# classes, one generic and one specific, e.g. `InNamespace` and `InNamespace<T>` the documentation output (in Class List) contains only one of the classes.

Now there are two sub-situations:

1) if the class is contained in a namespace, the non-generic class documentation is generated, but its methods are not documented.

2) if the class is not contained in a namespace, only the generic class appears in ClassList, and the documentation contains methods from both generic and non-generic classes.

Please take a look at the attached example that covers all of those situations.
Comment 1 André Klapper 2018-07-30 10:15:11 UTC
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!