
From: CRDGW2::CRDGW2::MRGATE::"SMTP::WSMR-SIMTEL20.ARMY.MIL::INFO-ADA-REQUEST"
Date:  6-JUL-1989 05:31:56
Description: INFO-ADA Digest V89 #160                             

Message-Id:  <8907060906.AA12563@crdgw1.ge.com>
Date: Thu,  6 Jul 89 01:00:27 MDT
From: INFO-ADA-REQUEST@AJPO.SEI.CMU.EDU
Reply-To: INFO-ADA-REQUEST@AJPO.SEI.CMU.EDU
Subject: INFO-ADA Digest V89 #160
To: INFO-ADA@AJPO.SEI.CMU.EDU
 
INFO-ADA Digest             Thu,  6 Jul 89       Volume 89 : Issue 160
 
Today's Topics:
         Contents of ASR Newsletter, Issue 110, May-June 1989
              Debugging and source analysis tool for Ada
                            From C to Ada
                         MS-DOS ADA Compiler
                         Questions on Ada...
                    What is the origin of `pragma'
----------------------------------------------------------------------
 
Date: Tue, 4 Jul 89 15:42:36 MDT
From: Rick Conn <RCONN@WSMR-SIMTEL20.ARMY.MIL>
Subject: Contents of ASR Newsletter, Issue 110, May-June 1989
 
	The following is the contents page of the recent ASR Newsletter.
This newsletter is available in machine-readable form in PD2:<ADA.NEWS> as
ASR110.DOC on SIMTEL20.
 
           Ada Software Repository Newsletter, Issue 110, May-June 1989
 
 
                                    Edited by
                                   Richard Conn
                         Manager, Ada Software Repository
 
                                   Published by
               Management Assistance Corporation of America (MACA)
                          PO Drawer 100 - Building T148
                   White Sands Missile Range, New Mexico  88002
                                   505/678-3288
 
 
                                    THIS ISSUE
                                    ----------
 
                                 Part I - Articles
 
     600,000 Accesses of the ASR  . . . . . . . . . . . . . . . . . . . .  1
     ASR Available Thru DECUS . . . . . . . . . . . . . . . . . . . . . .  2
     File Distribution to C2MUG and PC-BLUE . . . . . . . . . . . . . . .  2
     Top-Level STARS Index Incorporated into ADA Index  . . . . . . . . .  3
     Tape Distribution Changes  . . . . . . . . . . . . . . . . . . . . .  4
     SW-COMP Now Supported by the ASR . . . . . . . . . . . . . . . . . .  5
     Tutorial: Transferring Binary Files via FTP  . . . . . . . . . . . .  6
     Floppy Disks of the ASR  . . . . . . . . . . . . . . . . . . . . . . 11
     Command & Control Components and Software Reuse Taxonomies . . . . . 11
     List of Documents and Products Relating to Reusable Ada Software . . 12
 
 
                 Part II - Ada Software Repository Release Notices
 
               Ada LRM Reader for PCs, VAXen, SUNs, etc  . . . . . 15
               Bank Demo 3 Tasking Tutorial  . . . . . . . . . . . 15
               Update of FTP Documentation in the ASR  . . . . . . 16
               May 89 Snapshot of the ASR  . . . . . . . . . . . . 16
               Update of Command Line Interface  . . . . . . . . . 17
               CAMP Parts Info and Pointer . . . . . . . . . . . . 17
               New Welcome Message and Overview Files  . . . . . . 18
               Ada-Related Document Listing  . . . . . . . . . . . 19
               Ada Books in Print and Bibliography . . . . . . . . 19
               Air Force Ada Policy Statement (New)  . . . . . . . 19
               Glossary of Ada Terms . . . . . . . . . . . . . . . 20
               Update of Info on Obtaining ACVC Test Suite . . . . 20
               Validated Ada Compilers List for June . . . . . . . 21
               Ada Bibliography Ordering Info  . . . . . . . . . . 21
               Ada Tutor, Version 1.22 . . . . . . . . . . . . . . 21
               PAGER2, Version 2.0 . . . . . . . . . . . . . . . . 23
 
 
          Part III - Calls for Papers, Press Releases, and Announcements
 
               Ada Support for Object-Oriented Programming . . . . 24
               4th Track at TRI-Ada '89  . . . . . . . . . . . . . 25
               Books and Newsletter from Grebyn Corporation  . . . 26
-------
 
------------------------------
 
Date: 5 Jul 89 16:54:20 GMT
From: spdcc!ima!compilers-sender@husc6.harvard.edu
Subject: Debugging and source analysis tool for Ada
 
		DATAFLOW and STATIC ANALYSIS TOOL for ADA (EDSA)
 
At Array Systems Computing we have just completed developing a
prototype of a static debugger for Ada. Among the features of this
tool are:
 
 - the ability to display various properly formatted but restricted
   VIEWS of source code (i.e. eliding uninteresting code in order to
   allow the logic to stand out more clearly),
 
 - the ability to BROWSE programs following the control flow or data
   flow rather than the linear syntax of the code,
 
 - maintenance of SEARCH HISTORY to facilitate automatic BACKTRACKING
   when a search in a particular direction fails to find what the user
   is looking for.
 
The Expert Dataflow and Static Analysis tool (EDSA) operates on
uninstrumented source code. It requires neither execution nor
compilation of the code to be examined. Although the EDSA parser does
give some diagnostics, EDSA assumes that the program has already been
successfully compiled. You would use EDSA to find a bug in a program's
logic or to look for unforeseen ramifications of a proposed change,
not to fix syntax or semantic errors that would be found by a compiler.
 
Admittedly such a tool is more useful for poorly structured code than
for the kind of code that the design of Ada is meant to encourage.
However, it can still be useful for analyzing structured code.
Furthermore, it is unfortunately a fact of life that not all Ada
programs are properly structured.
 
We are currently looking for Alpha test sites to try out EDSA and
provide us with some feedback on its design and implementation.
EDSA runs on either vanilla Unix systems (Sun for sure, but probably
all others because it makes no use of machine or system dependent
features other than termcap) or MS-DOS machines. It makes no use of
bitmap graphics or windows, so it works on most terminals. On MS-DOS
machines it will support a mouse -- specifically the Logitec Mouse.
The Sun version does not use the mouse.
 
If you are interested in becoming an Alpha tester, please contact me
at the address shown below. Describe your environment (e.g. hardware,
OS, size and complexity of subject programs) and how EDSA might be
useful to you. Please do not ask for a trial copy of EDSA unless you
intend to try it out immediately.
 
--------------------------------------------------------------------
Leonard Vanek                  UUCP: ... uunet!attcan!lsuc!array!len
Array Systems Computing Inc.    or ... utzoo!dciem!array!len
5000 Dufferin St. Suite 200     or lsuc!array!len@ai.toronto.edu
Downsview, Ont. M3H 5T5        Phone: (416) 736-0900
Canada                         FAX:   (416) 736-4715
--
Send compilers articles to compilers@ima.isc.com or, perhaps, Levine@YALE.EDU
Plausible paths are { decvax | harvard | yale | bbn}!ima
Please send responses to the originator of the message -- I cannot forward
mail accidentally sent back to compilers.  Meta-mail to ima!compilers-request
 
------------------------------
 
Date: 4 Jul 89 19:03:54 GMT
From: m2c!wpi!wpi.wpi.edu!tfrancis@husc6.harvard.edu  (Krishan M Nainani)
Subject: From C to Ada
 
Hi,
 
 
	In converting some C code to Ada I came across a difficulty.
	In C, I pass the address of a structure (any structure) to a
	routine that doesn't care what the structure is. The structure
	is defined in this higher-level program which contains the
	procedure call. For example :
 
 
	struct stype { int a,b,c; float d,e,f; } a_struct;
 
	x = func_name(&a_struct);
 
	/* BTW, in "func_name" I store the structure contents in
	bytes by casting (char *). */
 
	In designing the low-level routine (in which this function
	is encoded), I was wondering if I could pass the address of
	a structure as I do above in C.
 
	If not, then I would have to use a generic package with a
	private parameter.
 
******************************************************************
	Also, thanks to everyone who sent me replied to my last
	mail message regarding questions on C -> Ada.
******************************************************************
 
Krishan Nainani.	reply-to:	tfrancis@wpi.wpi.edu
------------------------------------------------------------
 
------------------------------
 
Date: 1 Jul 89 08:17:38 GMT
From: zephyr!tektronix!reed!busker!p31.f4.n105.z1.FIDONET.ORG!Tom.Coleman@uunet.uu.net  (Tom Coleman)
Subject: MS-DOS ADA Compiler
 
Does anyone know of a good Ada compiler out there for PC/MS-DOS?
I've been anxiously awaiting the Top Speed Ada compiler from Jensen Partners, because I've been so impressed with thier Modula-2 compiler.  But it isn't expected to be released until 1991 or later.  I don't want to wait that long.
 
Thanks in advance
 
Tom Coleman
 
 
 
 
--
Tom Coleman - via FidoNet node 1:105/14
	    UUCP: ...!{uunet!oresoft, tektronix!reed}!busker!4.31!Tom.Coleman
	    ARPA: Tom.Coleman@p31.f4.n105.z1.FIDONET.ORG
 
------------------------------
 
Date: 5 Jul 89 23:42:33 GMT
From: microsoft!johnro@uunet.uu.net  (John Rogers)
Subject: Questions on Ada...
 
Hi!  There is another, more standard, way of doing conditional compilation
in Ada.  The original article had something like:
 
#ifdef SOMETHING
    random_C_code;
#endif
 
In Ada, it's possible to have groups of statements that are never
executed.  For instance:
 
   procedure Example is
     Something : constant Boolean := True;    -- change and recompile...
   begin
     if (Something) then
       random_Ada_Code;
     end if;
   end Example;
 
If "Something" is set to False in some other environment, then the
statements ("random_Ada_Code") will never be executed.  The ANSI/MIL-STD
for Ada allows this, and allows compilers to completely optimize out the
code.  This acts as a sort of conditional compilation.
 
Unfortunately, this isn't a complete solution to the need for
conditional compilation.  There's no way to do this for data declarations,
or "with" clauses, or various other things - just executable statements.
 
Hope this helps...
 
------------------------------
 
Date: 6 Jul 89 04:17:33 GMT
From: ico!vail!rcd@handies.ucar.edu  (Dick Dunn)
Subject: What is the origin of `pragma'
 
In article <8906291247.AA19739@ti.com>, fmoore@skvax1.csc.ti.com (Freeman Moore [214]995-1901) writes:
 
>    Why was the word `pragma' selected?
>
> Any ideas or pointers to references would be appreciated.
 
It may or may not have any bearing, but ALGOL 68 has a construct called a
"pragmat" with very similar usage.  I recall seeing it in at least one
other language of comparably ancient vintage, but I can't lay hands on the
information, and I can't recall whether it was pragma or pragmat.  ALGOL 68
uses a symbol "pr" as the delimiter.
--
Dick Dunn     rcd@ico.isc.com    uucp: {ncar,nbires}!ico!rcd     (303)449-2870
   ...Simpler is better.
 
------------------------------
 
End of INFO-ADA Digest V89 Issue #160
*************************************
