Path: utzoo!attcan!uunet!cs.utexas.edu!hellgate.utah.edu!helios.ee.lbl.gov!pasteur!ucbvax!ucsfcgl!pixar!fishkin
From: fishkin@pixar.UUCP (Ken Fishkin)
Newsgroups: comp.lang.c++
Subject: Re: Class documentation -- invitation for discussion.
Message-ID: <9730@pixar.UUCP>
Date: 22 Mar 90 15:43:05 GMT
References: <BESHERS.90Mar18161436@division.cs.columbia.edu>
Reply-To: fishkin@pixar.UUCP (Ken Fishkin)
Distribution: comp
Organization: Pixar -- Marin County, California
Lines: 20

In article <BESHERS.90Mar18161436@division.cs.columbia.edu> beshers@division.cs.columbia.edu (Clifford Beshers) writes:
]I would like to see discussion on the current and future state of
]standard class documentation formats and construction/maintenance
]tools.
]
]I have seen a tool for creating graphic representations of class
]hierarchies directly from code, but I haven't seen any standard
]format for textual descriptions of classes.

    I've seen two programs posted to the net to do this.
"classdoc", was written by Dag Michael Bruck (dag@control.lth.se), and
posted to this group.
"genman" was written by Bab Mastors (...palladium!bby), and posted
to comp.sources.misc.

    We haven't used "genman" yet. "classdoc" we use, and it produces
a pretty reasonable first-order man page (we've hacked it do to better
on processing comments).
-- 
Ken Fishkin	...ucbvax!pixar!fishkin