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,
	MSGID_SHORT autolearn=no autolearn_force=no version=3.4.4
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!mcnc!rti-sel!jb
From: jb@rti-sel.UUCP (Jeff Bartlett)
Newsgroups: net.lang.ada
Subject: Re: Fortran/Ada
Message-ID: <833@rti-sel.UUCP>
Date: Tue, 27-May-86 23:10:11 EDT
Article-I.D.: rti-sel.833
Posted: Tue May 27 23:10:11 1986
Date-Received: Thu, 29-May-86 07:31:42 EDT
References: <8605211948.AA00588@ucbvax.Berkeley.EDU>
Organization: Research Triangle Institute, NC
List-Id: <comp.lang.ada>

Some of the gotcha's I found in Xlating 'tran --> Ada were:
1.	a subroutine that wrote N elements of an array to an unformatted file.

	Of course, the array, N, and the logical unit number were parameters.

	And the actual parameters were arrays of almost anything, including
	the first elements of common blocks (yes, they wrote the whole block).
	(BTW, there was a matching read subroutine).

2.	Passing a slice of a multi-dim array to subroutines.
		(row-major vs column major).

3.	Run-time generated format lists. (nasty, but legal)

4.	Jumping out of case statements with GOTOs.  Can't with Ada.

5.	Equivalaces.  (arrays mapped into matrices, RM vs CM again).

6.	Of course, there is no compiler checks for parameter type or number.

7.	Statement operator precedence.

I think mechanical translation is difficult, but do-able.  It would
require the global 'view' of things.

Jeff Bartlett
Center for Digital Systems Research
Research Triangle Institute              rti-sel!jb@mcnc