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

Doxygen - Comments parser - 3 #452

Closed
toninlg opened this issue Apr 23, 2014 · 2 comments
Closed

Doxygen - Comments parser - 3 #452

toninlg opened this issue Apr 23, 2014 · 2 comments

Comments

@toninlg
Copy link

toninlg commented Apr 23, 2014

In the same workspace, if a function is defined in a C file of a library project with a Doxygen comment in front of it and if the prototype is defined in the corresponding header file : in the main project, the Doxygen comment is not displayed.
ie :
if I define print_hello() in .c and .h : print_hello() is displayed in the in main project's auto-completion box but with no comment. But if I define print_hello() in .c and print_hello(void) in .h, both functions appear in the main project's auto-completion box and the doxygen comment is displayed for print_hello() from .c.
doxygen-2

@eranif
Copy link
Owner

eranif commented May 5, 2014

This is because codelite sees them as different functions (because of the 'void' argument)
Simply avoid that kind of syntax...

I am not going to fix this, since its not worth the effort.
Patches however, are most welcomed

@eranif eranif closed this as completed May 5, 2014
@toninlg
Copy link
Author

toninlg commented May 5, 2014

Maybe my explanation isn't good. If I use the same syntax in header and code (which is normal), the parser sees the same function, but no comment is displayed. Maybe it looks only at header and displays nothing because the comment is in code file?. The parser would ideally look in header and in code if there is a comment before the function or is prototype. The example with void was an example where the parser is working since the function declaration in code isn't "overriden" with the one in header file.

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

2 participants