Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!noose.ecn.purdue.edu!mentor.cc.purdue.edu!seaman.cc.purdue.edu!ags
From: ags@seaman.cc.purdue.edu (Dave Seaman)
Newsgroups: comp.lang.fortran
Subject: Re: What is the FORTRAN for ?
Message-ID: <13035@mentor.cc.purdue.edu>
Date: 16 Aug 90 14:34:04 GMT
References: <MAINE.90Aug13204121@altair.dfrf.nasa.gov> <60202@lanl.gov>
Sender: news@mentor.cc.purdue.edu
Reply-To: ags@seaman.cc.purdue.edu (Dave Seaman)
Organization: Purdue University
Lines: 24

In article <60202@lanl.gov> jlg@lanl.gov (Jim Giles) writes:
>If
>I were designing a new HLL, I would make Fortran call compatibility a
>required part of the language specification.  That is, if the target
>machine has a Fortran implementation, any conforming implementation of
>_my_ language would be required to be able to interface to it in a
>uniform manner.  

So what do you do if the target machine has more than one Fortran
implementation and the different versions are not even compatible with each
other?

I suppose you could rule that the first Fortran implementation is the only one
allowed, thus ruling out improvements in the implementation that would change
the interface.

But what if there is no vendor-supplied Fortran, and only third-party
implementations exist?  Do you say the first one to ship is the official
version, and all others are barred from the market unless they change their
interface to conform?

--
Dave Seaman	  					
ags@seaman.cc.purdue.edu