Workflow for Automatically Documenting APIs?

[ezra <ezra@xxxxxxxxxxxx>]

Does anyone out there have a well-developed, robust, and (at least
partially, if not fully) automated workflow for documenting 
voluminous and complex APIs from C and C++ (and possibly Java) 
source code for both printed and online delivery for use both 
internally and by paying customers of the software products that
the source code is written to implement?

If so, can you describe the workflow, the tools involved, the quality of
the vendors for any commercial tools used, the problems encountered in
implementing the work flow (including both the technical and
organizational/political issues), maintenance and change issues, etc. etc.

We are now grappling with this issue the present time; no need to point
out this is very non-trivial task.

Thanks in advance.
Ezra

-------------------------------------------------------------------------
Ezra Steinberg				Resonate, Inc.
Senior Technical Writer			385 Moffett Park Drive, Suite 205
mailto:ezra@resonate.com		Sunnyvale, CA 94089-1208      USA
Voice: 408.548.5529			FAX: 408.548.5679


** To unsubscribe, send a message to majordomo@omsys.com **
** with "unsubscribe framers" (no quotes) in the body.   **