News:

As usual while waiting for the next release - don't forget to check the nightly builds in the forum.

Main Menu

Function/Class Comments and Intellisense

Started by GravityWell, October 27, 2012, 05:40:14 PM

Previous topic - Next topic

GravityWell

I see that Codeblocks has "code completion" which is good for displaying member functions and function parameters.

There is a feature in Visual Studio where functions can have XML comments associated with them, and then intellisense and tooltips will include the comments, like this:


Is there a way to do something similar in Codeblocks?

MortenMacFly

Quote from: GravityWe11 on October 27, 2012, 05:40:14 PM
Is there a way to do something similar in Codeblocks?
Not at the moment. However, using "switch header source"/"jump to declaration/implementation" in combination with split view / editors besides each other this is kind of implemented. That's at least how I do it and its really convenient.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

killerbot

or showing the doxygen help, is also a feature sometimes found in editors ...

cacb

If a feature like this was implemented, I would want it to be compatible with Doxygen syntax, so that "intellisense" and generated documentation always showed exactly the same thing. It should work for undocumented code as well, of course, showing the class, function and variable names. It is often enough.

What bugs me a little about the way such intellisense features work in C::B, is that I often want to call functions that I have just created in another project, and that information hasn't been updated in the help system yet, so I am often left with no help (except looking up the header file manually). Perfectly understandable, but it limits the usability unless you develop against a stable library. Still I would not want C::B to use my computer resources to constantly rescan my code to fix this issue, so I am allright with how things are.

oBFusCATed

It can just show the comment above the function declaration/definitions/both.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]