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=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,a81a0e2a4b8ecf3c X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1994-12-16 11:01:59 PST Path: nntp.gmd.de!newsserver.jvnc.net!nntpserver.pppl.gov!princeton!rutgers!sgigate.sgi.com!sgiblab!darwin.sura.net!source.asset.com!source.asset.com!not-for-mail From: weisek@source.asset.com (Kevin Weise) Newsgroups: comp.lang.ada Subject: Re: In search of Set/Get Variable reference tool Date: 16 Dec 1994 14:01:59 -0500 Organization: Asset Source for Software Engineering Technology Message-ID: <3cso77$129q@source.asset.com> References: NNTP-Posting-Host: 530tr0 Keywords: doc tool variables Date: 1994-12-16T14:01:59-05:00 List-Id: In article , Mike Winslow wrote: > > Is anyone familiar with a tool to build a table of variables used in >an Ada program, annotated with info on 1) which module(s) *write* each >variable, and (2) which module(s) *read* it?? > > Ideally, this tool would run on a SPARC SunOS 4.1.3 environment, but >VMS and Solaris 2.3 are also possibilities. This particular question seems to come up on a regular basis. I wonder if it is in the FAQ. Anyway, I recall using a tool called AdaQuest by General Research Corporation out of Santa Barbara, CA. The last contacts I had were Chuck Hobin (Staff Scientist) and Thomas Strelich (S/W Engr Ops); voice phone (805) 964-7724. There were two versions of this tool, one running under VMS and the other under DEC/Ultrix (perhaps retargeted to generic Unix workstation?). However, the tool worked somewhat differently and gave somewhat different results between the two versions. It basically walks DIANA trees to satisfy user queries. Since VADS keeps its DIANA code around, the UNIX version just ran off existing Ada libraries, meaning that you had to have compiled your code already. Since DEC Ada doesn't keep DIANA code around, the VAX/VMS version comes with a preprocessor to create it. This means the VMS version is "slower", consumes lots more disk space, and has some incompatabilities with the DEC Ada interpretation of legal Ada code (since the front end was actually the Intermetrics front end repackaged for VMS, a la Byron.) I believe the only problem has to do with what operators associated with a generic actual type parameter are visible at the point of an instantiation. Unfortunately, I believe only the VMS version has a Set/Use report. That's the long answer. For a short answer, I would check the DEC VAX tool SCA (Source Code Analyzer). Its built to interface with the VAX Ada compiler, and I believe can generate a Set/Use report. Comments, anyone from DEC or GRC? (Or Sun, or Verdix [oops, Rational] for that matter?) ---------------------------------------------------------------- Kevin J. Weise weisek@source.asset.com COLSA Corporation Voice - (205) 922-1512 ext. 2115 6726 Odyssey Drive FAX - (205) 971-0002 Huntsville, AL 35806 {Standard Disclaimers about my opinions & my employer's opinions} {... which are in conflict often enough} ---------------------------------------------------------------- "Admire those who seek the truth; avoid those who find it." Marcel Proust