You are quite right. That is an issue that should be solved. There is Doc++ for Linux, there are also others that should be looked at.
The most advantageous would be one that doesn't require any special tagging, although the capability to generate useful documentation (class browse, hierarchy, html format, etc) seems to require some tagging.
Thoughts?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Personally I like Doc++; it has some tagging but the tagging isn't necessary for straight forward class and member documentation. I haven't surveyed the landsacpe though I'm not sure what is out there that is newer.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I added it to the requirements. Take a look at the mailing list. This is a way to open communications from e-mail instead of going through here every time.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I didn't see any approach/guideline for source documentation. Did I miss it?
You are quite right. That is an issue that should be solved. There is Doc++ for Linux, there are also others that should be looked at.
The most advantageous would be one that doesn't require any special tagging, although the capability to generate useful documentation (class browse, hierarchy, html format, etc) seems to require some tagging.
Thoughts?
Personally I like Doc++; it has some tagging but the tagging isn't necessary for straight forward class and member documentation. I haven't surveyed the landsacpe though I'm not sure what is out there that is newer.
I added it to the requirements. Take a look at the mailing list. This is a way to open communications from e-mail instead of going through here every time.