Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!pt.cs.cmu.edu!rochester!rit!tropix!moscom!ur-valhalla!uhura.cc.rochester.edu!sunybcs!rutgers!cs.utexas.edu!csd4.milw.wisc.edu!uxc.cso.uiuc.edu!uxc.cso.uiuc.edu!ux1.cso.uiuc.edu!uxe.cso.uiuc.edu!mcdonald
From: mcdonald@uxe.cso.uiuc.edu
Newsgroups: comp.lang.fortran
Subject: Re: Digital Review Article: VAX Fortran
Message-ID: <50500132@uxe.cso.uiuc.edu>
Date: 22 Jul 89 13:27:00 GMT
References: <19553@cup.portal.com>
Lines: 19
Nf-ID: #R:cup.portal.com:19553:uxe.cso.uiuc.edu:50500132:000:769
Nf-From: uxe.cso.uiuc.edu!mcdonald    Jun 18 08:27:00 1989


>There was an article on the front page of DIGITAL REVIEW this week that said 
>VAX FORTRAN will break under F88 if implemented. 


 >Is this true?  I have a lot of source codes that made extensive use of VAX
>Extensions.  Will these codes have to be modified to F77 so it will be
>compatible with F88 when it comes out?  Or, should I start looking at other
>languages?


By the time F88 compilers come out, you probably won't be running on
Vaxes any more. It will have already been more cost-effective to 
recode in F77 or ANSI C and run on far, far, cheaper machines. 
That has already happened here. You can buy a PC that runs Fortran
code as fast as the fastest mono-processor VAX (floating point).
RISC boxes are even faster and as cost-effective.

Doug McDonald