Suggestions for documentation generation?

K

kpd

Hello,

I have written a C++ library that I've then wrapped with Pyrex.
Any suggestions to the best-in-class tool to create documentation for
the libraries?

I would love to document things in one spot (could be the code) and
generate html and PDF from there.

Doxygen (www.doxygen.org) looks to be about the best so far.

Thanks,
 
J

John M. Gabriele

kpd said:
Hello,

I have written a C++ library that I've then wrapped with Pyrex.
Any suggestions to the best-in-class tool to create documentation for
the libraries?

I would love to document things in one spot (could be the code) and
generate html and PDF from there.

Doxygen (www.doxygen.org) looks to be about the best so far.

Thanks,

I've heard that some folks use pythondoc:
http://starship.python.net/crew/danilo/pythondoc/
http://effbot.org/zone/pythondoc.htm

There's also HappyDoc http://happydoc.sourceforge.net/
and EpyDoc http://epydoc.sourceforge.net/ .
 
K

kpd

Thanks - I took at both. Also at 'percepts', which I used a long time
ago (had forgotten about it). Percepts has a great little java applet
for viewing the class hierarchy. I don't think it works for python,
just C++ though. Looks like doxygen will fit the bill.
 
M

Michael Ekstrand

Thanks - I took at both. Also at 'percepts', which I used a long time
ago (had forgotten about it). Percepts has a great little java applet
for viewing the class hierarchy. I don't think it works for python,
just C++ though. Looks like doxygen will fit the bill.

An excellent choice IMHO.

Doxygen has recently added support for Python, so if there is
pure-Python code interfacing with the rest of your work, that can be
documented also.

- Michael
 
B

Bo Peng

kpd said:
Hello,

I have written a C++ library that I've then wrapped with Pyrex.
Any suggestions to the best-in-class tool to create documentation for
the libraries?

I would love to document things in one spot (could be the code) and
generate html and PDF from there.

Doxygen (www.doxygen.org) looks to be about the best so far.

I was facing the same problem and took the following approach:

1. write c++ code with doxygen-complaint comments
2. generate XML comments using doxygen
3. parse XML and generate Python docstring
4. insert the docstring into SWIG interface file

I can send you the parser but I do not know if pyrex support python
docstring.

Bo
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
474,432
Messages
2,571,680
Members
48,796
Latest member
Greg L.

Latest Threads

Top