Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!caen!malgudi!sunc!cis.ohio-state.edu!tut.cis.ohio-state.edu!udecc.engr.udayton.edu!blackbird.afit.af.mil!dlindsle
From: dlindsle@afit.af.mil (David T. Lindsley)
Newsgroups: comp.lang.fortran
Subject: Re: Difference between Lahey Fortran and Microsoft Fortran
Message-ID: <1991Jun13.153846.22563@afit.af.mil>
Date: 13 Jun 91 15:38:46 GMT
Article-I.D.: afit.1991Jun13.153846.22563
References: <1991Jun12.205040.9649@noose.ecn.purdue.edu>
Organization: Air Force Institute of Technology
Lines: 17

I haven't worked with Lahey, but several people I know and trust have,
amd they _all_ say it's better than MS Fortran.  (We're talking about
the full-blown version.)

I have worked with MS Fortran (v4.01, not 5), and I wasn't overly
impressed.  It didn't include any of the extensions from MIL-STD 1753
(DO-WHILE, ENDDO).  I couldn't get their MAKE utility to work either. 
The manual describes it as operating almost exactly like the Unix MAKE
-- this would have been nice, but I certainly couldn't get it to do that.  
Dependencies had to be specified in reverse order; macro substitution
was buggy; if the first object file didn't need to be recompiled, the
whole thing aborted...

-- 
Dave Lindsley	#24601#					   OPINIONS. MINE. 
dlindsle@blackbird.afit.af.mil		(The words don't come no smaller.)
			?? lamroN eb yhW ??