Developer forums (C::B DEVELOPMENT STRICTLY!) > CodeCompletion redesign

Doxygen documentation with code completion?

(1/2) > >>

gokudo:
Hi everyone.
I mainly program with java, and with a good IDE in this language we can always see the javadoc near the code completion window.
I've never seen this feature in a c++ ide (except visual studio which uses its own type of documentation - not doxygen, the most commonly used type of documentation).
I don't know if this would easy to implement or if everyone don't care, but I really think this could be useful.

killerbot:
nice idea for an extension, but the first topic we need to solve is, getting a good code completion. For the moment there are several issues with it. ;-)

gokudo:
Yep, I now that.
But, by experience, I know that when a project become too big it's very difficult to add new features.
I really thing this type of feature could be the big "+" to make Code::Blocks one of the greatest ide for C++. So I try to point that, if you think this is interresting maybe you will create you project to make it easy-to-implement.

PS: please forgot my poor writting, my main language is not english.

Michael:

--- Quote from: gokudo on February 28, 2006, 01:48:46 pm ---But, by experience, I know that when a project become too big it's very difficult to add new features.

--- End quote ---

Yes, IMHO it is so. But if you design your project in a modular and scalable way and you avoid unnecessary hard-coding, then it would be easier to add new features.

Anyway, your suggestion is interesting :).

Best wishes,
Michael

TDragon:
gokudo: I agree wholeheartedly that this would be an excellent feature to have.

Albeit behind the scenes, I am working on building a code-completion parser with the potential for integration with Code::Blocks. Though I don't yet have the actual parser done at all (I'm struggling to come up with a good, modular and flexible design), the overall structure allows the ability to parse comments (and thus documentation of any style, including Doxygen-style) alongside the code itself, rather than extracting all commentary during a "preprocessing" stage. I implemented a "multilexer" (to coin a term) that directly tokenizes streams of characters into a stream of C or C++ tokens, whitespace, preprocessor directives, and commentary. I envision an "Overseer" class that will then direct this stream to appropriate subtasking classes including a "TokenFilter" class that can remove unneeded tokens from the stream (compiler-specific extensions, such as GCC's __attribute__, come to mind), a "CommentParser" and a "CxxParser" which will act in tandem to parse commentary and code, and any others as needed.

However the code completion redesign happens, it should definitely include functionality to handle all the contents of a source file. This will allow features like accompanying documentation to fall into our collective laps, so to speak.

Navigation

[0] Message Index

[#] Next page