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 662289 - TCL lines of ##### are shown in the description
TCL lines of ##### are shown in the description
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: build
1.7.5.1
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2011-10-20 12:28 UTC by John Wayne
Modified: 2012-02-25 15:37 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Config-file and tcl-file (15.50 KB, application/x-tar)
2011-10-20 12:28 UTC, John Wayne 		Details

Description John Wayne 2011-10-20 12:28:30 UTC 
Created attachment 199518 [details]
Config-file and tcl-file

I have old documented TCL-files and there are many lines with ##### in it.
I don't want this comments in the doxygen documentation.
It was better to check whether there are exactly two ## at the beginning of the comment.
Like in C++ /*** is no legal beginning of a doxygen comment.

Furthermore there is a different whether there are #-lines before and behind the comment o if there is a brief-description before the next object.

################
# old comment
################

################
# old comment

Now I have to change all lines to
# ##########
# new comment with space
Comment 1 r.zaumseil 2011-12-29 20:48:10 UTC 
Your suggestion is good. I have changed the parser to recognize
doxygen comments when starting with ## (two hash chars followed
by a non hash char).

The changed tclscanner.l file is in the attachment to bug #662286.

Sorry for the delay but I found abut the bug just recently.

Better put also a notice on http://wiki.tcl.tk/27011
Comment 2 Dimitri van Heesch 2011-12-29 23:07:44 UTC 
Thanks, I'll include the patch in the next subversion update.
Comment 3 Dimitri van Heesch 2012-02-25 15:37:25 UTC 
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.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.