🚀 go-pugleaf

In article <1992Oct12.160833.731@e2big.mko.dec.com>, sharone@shar.zko.dec.com (Sharon Eikenberry) writes:
> 
> Are you looking for help with the REPORT command, or are you unaware of their
> existence?
> 
No, I am very aware of the reports, but I want to use any procedures that have
already been written if possible.  I have looked at the procedures in
sca$root:[example], but have been unwilling to take the time to modify the
internals report for my purposes.  I really want to automatically generate much
of the SDD section 4 stuff, instead of using the tags provided in the 2167A
report.  The tags idea is great, but as you know, most engineers fail to keep
that kind of information up to date.  What is really needed is a tool to pull
the design out of the code since that is where the rubber meets the road.  SCA
comes pretty close, although I've had a hard time selling the rest of the group
on it.  They prefer dcl searches to sca>find ***** .

What I am really looking for is someone who has used SCA to automatically
generate what they thought they could (imports,exports,globals,locals) and use
tags for the rest.  I envision this as some kind of a mix between an internals
report and a 2167A report.  I like the internals report for its content and the
fact that it uses the code only if there are no tags, but I need the 2167A
format for contractual purposes.  I guess if I don't get any response, I will
bite the bullet and figure out what   SCA$REPORT_INTERNALS.TPU;1 and
SCA$REPORT_2167A_DESIGN.TPU;1 do and make the necessary changes.  I have
written a few TPU procedures and have the most experience with SCA at this
site, but I think I need a much better handle on TPU and SCA before I can make
changes that will work.  I may have a lot of questions are you a good person to
ask?  Do you prefer posts or email?  When I'm in the middle of doing this, I
will probably like some relatively quick response.  I know that we have a
support contract, but usually one of the system managers has to send the
message I think.


> In LSE V3.0 and later, the REPORT command generates reports based on 
> comments within the source code.  One of the available reports is 2167A.
> 
> If you have specific questions about the REPORT command, ask away.
> 
> --Sharon Eikenberry			! eikenberry@tle.enet.dec.com
>   LSE Developer
>   Digital Equipment Corporation
>   
>   Opinions are my own.
-- 
-------------------------------------------------------------------------------
Todd A Sorensen               Honeywell Defense Avionics Systems Division
(505) 828-5611                internet: tas@dasd.honeywell.com
                              fax: (505) 828-5500
------------------------------------------------------------------------------- 
You live in a Free country, but are you really free?
-------------------------------------------------------------------------------