Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utcs!mnetor!seismo!columbia!caip!princeton!allegra!ulysses!mhuxr!mhuxn!ihnp4!inuxc!pur-ee!uiucdcs!uicsrd!parafras
From: parafras@uicsrd.UUCP
Newsgroups: net.arch
Subject: Re: Orphaned Response
Message-ID: <1000020@uicsrd>
Date: Mon, 14-Jul-86 16:35:00 EDT
Article-I.D.: uicsrd.1000020
Posted: Mon Jul 14 16:35:00 1986
Date-Received: Wed, 16-Jul-86 22:31:42 EDT
References: <1000014@uicsrd>
Lines: 17
Nf-ID: #R:uicsrd:1000014:uicsrd:1000020:000:831
Nf-From: uicsrd.CSRD.UIUC.EDU!parafras    Jul 14 15:35:00 1986


The input language to Parafrase is FORTRAN 66 with some extensions.  The 
output is a FORTRAN-like language that cannot be compiled on any FORTRAN
compiler.  The most noticeable differences are:

	1) loop types other than DO, notably DOALL, DOPIPE, DOACROSS, etc.

	2) non-standard variable names.  &, ', lower case, etc. are
	   included in variable names.  This is good in that a user of
	   Parafrase can tell what transformation caused some temporaries
	   to be created.  This is bad because it's not standard.

It would not be much trouble to write a pass that would convert Parafrase
output FORTRAN back to standard serial FORTRAN, but then you really haven't
gained a whole lot.  It would be more useful to convert Parafrase output
to a general standard parallel FORTRAN, but unfortunately such a beast does
not yet exist.