Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!convex!mozart!metzger
From: metzger@mozart.uucp (Robert Metzger)
Newsgroups: comp.lang.apl
Subject: Fortran to 77 to APL via vectorization
Keywords: Fortran, APL, vectorization
Message-ID: <3987@convex.UUCP>
Date: 15 Dec 89 15:24:47 GMT
References: <180556@<1989Dec12> <49700018@uicsrd.csrd.uiuc.edu>
Sender: usenet@convex.UUCP
Reply-To: metzger@convex.COM (Robert Metzger)
Organization: Convex Computer Corporation, Richardson, Tx.
Lines: 27

In article <49700018@uicsrd.csrd.uiuc.edu> jaxon@uicsrd.csrd.uiuc.edu writes:
>
>I have a question on a different subject:
>
>Would anyone support modifying a Fortran 77 vectorizer to produce APL or APL2
>(or even Dictionary APL) output?  Reply to jaxon@uicsrd.uiuc.edu (or here).

If others are interested, we could define the problem in this newsgroup,
and then those of us with access to Fortran vectorizers will see what we
can do about it.

I would suggest that input be restricted to true Fortran 77
(maybe plus the MilStd extensions, which everyone seems to have implemented).

A second restriction would be to simply transfer all I/O statements to
the target program, encapsulated in comments, so that the programmer can
convert them manually.  This covers
	BACKSPACE, CLOSE, ENDFILE, FORMAT, INQUIRE, OPEN, PRINT, 
	READ, REWIND, WRITE

I don't know what to do with ENTRY statements and alternate RETURNs,
I suggest that routines that use them be excluded.  Same for PAUSE and STOP.

There are lots of other problems.  I'll post some more if anyone else responds.

As for output, either APL Classic (pre nested/general/enclosed/accursed)
arrays, or Dictionary APL.