tag file: Unknown compound attribute `singleton' found! (Origin: bugzilla #735376)

[doxygen]

status RESOLVED severity major in component documentation for ---
Reported in version 1.8.8 on platform Other
Assigned to: Dimitri van Heesch

On 2014-08-25 11:51:51 +0000, Markus Eisenmann wrote:

Hi!

I have two C++ projects (using name A and B afterwards). Project B depends on A; Ie. doxygen-generation of B depends on ../A/A.tag, which is created in a previous build-step.

There was no error or warning in doxygen-pass A, but the second doxygen-generation of B results in following warnings:
../A/A.tag:16087: warning: Unknown compound attribute singleton' found! ../A/A.tag:16088: warning: Unexpected tag name' found
../A/A.tag:16089: warning: Unexpected tag filename' found ../A/A.tag:16090: warning: Unexpected tag templarg' found
../A/A.tag:16091: warning: tag `compound' was not expected!

After some investigations, Ie. comparing the output of doxygen 1.8.8 to the previous release 1.8.7, I've determined following issue:

A C++ header-file of project A does contain a forward-declaration of a template-class, like:
template class Delegate; /FORWARD-DECLARATION/

Doxygen 1.8.7 has generated a documentation (snippet) like:

Delegate< TFnc > Class Template Reference
and in 'Detailed Description':
template
class Gmc::util::Delegate< TFnc >

, but the HTML-result of Doxygen 1.8.8 was:

Delegate< TFnc > Singleton Reference
and in 'Detailed Description':
template
singleton Gmc::util::Delegate< TFnc >

At least, it seems, that doxygen 1.8.8 has changes the (principal) type/classification from 'class template' to 'singleton' for this templated class-declaration. The warnings afterwards (Unknown compound attribute) for "doxygen" project B are subsequent issues.

I've also searched for some information a similar Singleton-issue or whether this is a special kind of (doxygen-) region/type; but w/o success :-(

Best regards from Salzburg,
Markus

On 2014-09-22 20:10:43 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next GIT update.

On 2014-12-25 16:02:54 +0000, Dimitri van Heesch wrote:

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).