Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TCL lines of ##### are shown in the description (Origin: bugzilla #662289) #4444

Closed
doxygen opened this issue Jul 2, 2018 · 0 comments
Closed

Comments

@doxygen
Copy link
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity normal in component build for ---
Reported in version 1.7.5.1 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2011-10-20 12:28:30 +0000, John Wayne wrote:

Created attachment 199518
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

On 2011-12-29 20:48:10 +0000, r.zaumseil@freenet.de wrote:

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

On 2011-12-29 23:07:44 +0000, Dimitri van Heesch wrote:

Thanks, I'll include the patch in the next subversion update.

On 2012-02-25 15:37:25 +0000, Dimitri van Heesch wrote:

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.

@doxygen doxygen closed this as completed Jul 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant