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 331519 - template explicite instantiation
template explicite instantiation
Status: RESOLVED OBSOLETE
Product: doxygen
Classification: Other
Component: general
1.4.x
Other All
: Normal minor
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
[moved_to_github]
Depends on:
Blocks:
 
 
Reported: 2006-02-17 09:16 UTC by Seweryn Habdank-Wojewódzki
Modified: 2018-07-30 10:26 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Seweryn Habdank-Wojewódzki 2006-02-17 09:16:12 UTC
Please describe the problem:
When in the code is used template explicite instantiation then doxygen interpret
it as something like operator().

Steps to reproduce:
The example of that problem is below. In my file configuration.cpp I have
explicit instantiation of the template - is shown in \code section.

\code
	template Loki::SingletonHolder < Configuration >;
\endcode

Loki - Andrei Alexandrescu namespace for Loki library.
SingletonHolder - template class.
Configuration - my own class.

Such a construction is allowed in C++, see "C++ Templates, The Complete Guide",
Vandevoorde D., Josuttis N.M.

Actual results:
and doxygen produces:

\verbatim

configuration.cpp:21: Warning: no matching class member found for template
config::Loki::SingletonHolder< Configuration >()

\endverbatim

It tries to fit explicit instantiation as member function of the class, it is
not correct.

Expected results:
Either omit such a place or proper recognize it.

Does this happen every time?
Yes.

Other information:
I think that Doxygen is the best one :-).
Comment 1 André Klapper 2018-07-30 10:26:32 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!