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 319820 - "protoType =" showing on Doxygen Output
"protoType =" showing on Doxygen Output
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.5.3-SVN
Other Linux
: Normal trivial
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2005-10-26 05:15 UTC by Kevin McBride
Modified: 2005-11-10 07:34 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Kevin McBride 2005-10-26 05:15:29 UTC
Version details: 1.4.5-20051024
Distribution/Version: 2.6.12

I noticed that doxygen is now showing "protoType =" through stdout on every
protoType parsed.  Is this a new feature that can be turned off, or is it a bug
in the source code?  If it's a bug in the source code, then I think there should
be an option to turn it off.

And, as usual, I am using 1.4.5-20051024.
Comment 1 Dimitri van Heesch 2005-10-26 20:26:51 UTC
It is probably a debug print I forgot to remove/comment. But the strange thing
is that: 

grep protoType *.h *.l *.cpp *.y

on the source dir yields no result. So please check if there is typo in your bug
report.
Comment 2 Raimondo Giammanco 2005-10-27 14:39:28 UTC
Maybe he meant "functionProto=" ?

I have this sort of debug infos, with Doxygen version 1.4.5-20051024
Comment 3 Kevin McBride 2005-10-28 01:11:53 UTC
What Raimondo was saying is what I meant.  Re-opening bug.
Comment 4 Dimitri van Heesch 2005-10-30 13:10:07 UTC
Should be fixed in the next CVS update.
Comment 5 Kevin McBride 2005-11-10 07:01:06 UTC
This has not yet been fixed since 20051109.  I'll just take a look myself and
upload a patch.
Comment 6 Kevin McBride 2005-11-10 07:34:06 UTC
Never mind.  It appears that the debug print has been removed.  I had .l files
in my patch, and when they got applied, the debug print continued.