GNOME Bugzilla – Bug 736992
Member functions omitted from tagfile
Last modified: 2014-12-25 16:03:01 UTC
Virtual member functions are omitted from the tag file for base classes, and are instead listed only under the *first* derived class to occur in alphabetical order. To illustrate the problem,
Created attachment 286658 [details] file that contains the derived class declaration
Whoops, submitted accidentally while adding attachments. Anyway, use both BaseClass.h and DerivedClass.h to generate a tag file. You'll see that BaseClass::functionOne() gets listed *only* under the compound for DerivedClass. Also, note that alphabetical order and order of appearance in the tag file appears to play a role: if you rename ADerivedClass to simply "DerivedClass" or "ZDerivedClass" or something that comes *after* "BaseClass", the entry for functionOne() in the tag file gets placed where it should, under the BaseClass. By trial and error, I discovered that this problem was introduced in 1.8.3.1. In 1.8.3 and before, the functions were always listed correctly. In 1.8.3.1 up to 1.8.8, virtual functions are getting put only under whatever child class comes up first in the order.
Hi Robb, Can you please attach the whole example (source+config file in a zip). Now I have only DerivedClass.h
Created attachment 286813 [details] Simple test case that contains .h files and doxygen config
Sorry about that. The attached test case (tagfile_testcase.zip) has two headers, with a simple base class and derived class. The only things I changed in the config were to set up the input, and to set the GENERATE_TAGFILE. When you run the build, you'll see that the generated tagfile (mytagfile.tag) contains entries for both the base and derived classes. But the function BaseClass::functionOne() is only listed under the derived class, not under the base class. -r
Confirmed. Should be fixed in the next GIT update.
This bug was previously marked ASSIGNED, which means it should be fixed in doxygen version 1.8.9. Please verify if this is indeed the case. Reopen the bug if you think it is not fixed and please include any additional information that you think can be relevant (preferrably in the form of a self-contained example).