Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!sun-barr!cs.utexas.edu!usc!ucsd!ucbvax!AERO4.LARC.NASA.GOV!blbates
From: blbates@AERO4.LARC.NASA.GOV ("Brent L. Bates AAD/TAB MS361 x42854")
Newsgroups: comp.sys.sgi
Subject: Re:  mkf2c problems
Message-ID: <9012131205.AA24029@aero4.larc.nasa.gov>
Date: 13 Dec 90 13:05:20 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 18


    I was told that 3.3.2 should be shipping "any day now".
    Why do you need to use mkf2c?  I always though that created more pain
than was necessary.  Other machines I have used don't need anything like
mkf2c.  If you make the C routines correctly, like using pointers for the
varables passed to the C routines and other similar precausions, it
shouldn't be that difficult.  Now I haven't tried any FORTRAN to C on our
4D's, yet, and when I tried it on our 3130, long ago, it never worked to
my statisfaction, but then again there weren't a lot of things that worked
reasonably on the 3130's any way.
--

	Brent L. Bates
	NASA-Langley Research Center
	M.S. 361
	Hampton, Virginia  23665-5225
	(804) 864-2854
	E-mail: blbates@aero4.larc.nasa.gov or blbates@aero8.larc.nasa.gov