GNOME Bugzilla – Bug 611193
Doxygen thinks catch(...) is a function
Last modified: 2011-03-28 14:19:07 UTC
Created attachment 154769 [details] Example code to reproduce the problem The catch(...) clause of one of my functions is always documented as a function. I have Windows 7 Proffesional 6.1.7600, 64 bit. The sample code is minimal, but the original code compiles successfully with Visual C++ 2008.
Created attachment 154770 [details] Doxyfile for the doxygen session, setting Doxygen to treat all entities as documented.
Still present with 1.6.3
Looks like it happens on any try/catch function of the form retval FuncName(params, ...) try { // ... // function body // ... } catch (exception...) { // catch handler } catch (...) { // catch handler }
Confirmed. Should be fixed in the next subversion update.
This bug was previously marked ASSIGNED, which means it should be fixed in doxygen version 1.7.0. 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.
Yes it works now Thank you
Created attachment 181103 [details] Constructor function tryblock example
I have the same problem when using a constructor function try block, see attached file. I use Doxygen 1.7.2. The code compiles with mingw32 gcc 4.5.0.
Confirmed. The "try:" is causing the problem. Workaround: use "try :". Should be corrected in the next subversion update.
This bug was previously marked ASSIGNED, which means it should be fixed in doxygen version 1.7.4. 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.