From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,2a5467dded7223af X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-11-06 04:24:35 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!cyclone.bc.net!snoopy.risq.qc.ca!newsfeed.news2me.com!newsfeed2.earthlink.net!newsfeed.earthlink.net!stamper.news.pas.earthlink.net!newsread2.prod.itd.earthlink.net.POSTED!not-for-mail Message-ID: <3DC919DD.7A419D28@earthlink.net> From: "Marc A. Criley" Organization: Quadrus Corporation X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.14-5.0 i686) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Building documentation from comments References: <3dc7f605$0$303$bed64819@news.gradwell.net> <3dc8d6e1$0$301$bed64819@news.gradwell.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 06 Nov 2002 12:24:35 GMT NNTP-Posting-Host: 63.190.233.0 X-Complaints-To: abuse@earthlink.net X-Trace: newsread2.prod.itd.earthlink.net 1036585475 63.190.233.0 (Wed, 06 Nov 2002 04:24:35 PST) NNTP-Posting-Date: Wed, 06 Nov 2002 04:24:35 PST Xref: archiver1.google.com comp.lang.ada:30439 Date: 2002-11-06T12:24:35+00:00 List-Id: Victor Porton wrote: > P.S. May be the best solution would be if I would find time to modify > Booch source in such the way that it would become fully compatible with > AdaBrowse. Is Boch author here? Would you include my changes in the > next release and continue to follow my policy for compatibility with > AdaBrowse? This is the approach I've taken with some brand new Ada that I'm writing. I'm trying AdaBrowse out as a documentation aid, and am finding that by tweaking the configuration file a bit, and then ensuring my comments are in the right locations, that the docs are coming out pretty good. I find it most effective to write some code and associated comment docs, then run AdaBrowse and review the output, to ensure that everything is being properly grouped together. I don't find the comment positioning requirements too onerous, it's certainly no worse than, say, having to do manual indenting of source code statements. Marc A. Criley Quadrus Corporation www.quadruscorp.com