|
|
Home » Community » Coffee corner » in code comments - doxygen
in code comments - doxygen [message #6642] |
Tue, 21 November 2006 12:24  |
qwerty
Messages: 130 Registered: May 2006
|
Experienced Member |
|
|
just thought :
using some specificaly syntax offered by upp ide or in comment syntax(aka visual studio 2005 xml comments)
...
to generate documentation from your code or from upp under specifical circumstances
maybee in future
|
|
|
|
|
|
|
|
|
Re: in code comments - doxygen [message #7951 is a reply to message #6642] |
Thu, 01 February 2007 18:27   |
mr_ped
Messages: 826 Registered: November 2005 Location: Czech Republic - Praha
|
Experienced Contributor |
|
|
I've been using Doxygen for my own projects, and once you work with it since the very start, it does produce at least average documentation. In case you really pay time and attention, there's no problem to get on good level. (In my eyes most of SW documentations out there are either utter bad, bad or average, so suggesting "good" level is something like admiration)
While Topic++ allows for excellent documentation if enough time and attention is used, I sort of dislike splitting the documentation from the actual code itself.
For high level documentation of course there's no real code, and it starts to be cumbersome to hold this one directly in sources (for Doxygen), and trying out really high abstraction docs was too complex for me. (while I believe that exactly the area where Topic++ can shine)
But when we get back down to commenting the code on low level, I think Doxygen is pretty much ultimate tool.
|
|
|
|
|
Re: in code comments - doxygen [message #8075 is a reply to message #8074] |
Tue, 06 February 2007 10:27   |
 |
mirek
Messages: 14255 Registered: November 2005
|
Ultimate Member |
|
|
mr_ped wrote on Tue, 06 February 2007 04:11 |
luzr wrote on Mon, 05 February 2007 22:57 | I would like to postpone the final judgement until we have new class browser with Topic++ integration.
|
IMHO it's not as much about what Topic++ *can* do.
It's simply the docs stored not in code, what is main problem.
So whenever you change code, you must run Topic++ to change the help, which will never (ok, with absolutely disciplined programmers it will work superb, but we live in real world) work as good as doxygen's comments which reside inside of the code itself.
Still any lazy programmer will break even doxygen documentation, but the the some-what lazy programmer (who's too lazy to launch Topic++ but not enough lazy to not change comment) will produce better results with doxygen-like approach.
So the Topic++ will be always 1 step behind doxygen on the low level documentation, unless you merge the best of both worlds i.e. add features into Topic++ which will analyze the code itself and extract the low level documentation directly from code and comments just like doxygen does.
|
Well, these arguments are considered and valid.
On the other side of equation there is comfort of Topic++ editor... I can have advanced WYSIWYG formatting, spell checking, pictures...
Mirek
|
|
|
|
|
|
|
|
|
|
Goto Forum:
Current Time: Mon Apr 28 00:55:38 CEST 2025
Total time taken to generate the page: 0.00821 seconds
|
|
|