Xref: utzoo comp.lang.c:32412 comp.lang.fortran:3866
Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!julius.cs.uiuc.edu!ux1.cso.uiuc.edu!harriett!hirchert
From: hirchert@harriett.ncsa.uiuc.edu (Kurt Hirchert)
Newsgroups: comp.lang.c,comp.lang.fortran
Subject: Re: Fortran Main with C I/O
Keywords: peace, calm, smart
Message-ID: <1990Oct1.155217.24452@ux1.cso.uiuc.edu>
Date: 1 Oct 90 15:52:17 GMT
References: <1044@helens.Stanford.EDU> <1990Sep20.221007.8515@cs.dal.ca> <1990Sep21.132232.11305@DRD.Com>
Sender: news@ux1.cso.uiuc.edu (News)
Reply-To: hirchert@harriett.ncsa.uiuc.edu (Kurt Hirchert)
Distribution: usa
Organization: National Center for Supercomputing Applications
Lines: 18

In article <1990Sep21.132232.11305@DRD.Com> mike@DRD.Com (Mike Rovak) writes:
>bill%biomel@cs.dal.ca wrote:
>} This would be an absolute disaster.  We use C I/O extensively for things
>} like graphics, raw input, and to do things like display a file directory
>} when asking the user to input a data file name.  If true, someone had
>} better come up with a fix awfully fast!
>
>Not a problem, guys.  Make a C main function whose sole purpose is to call
>the Fortran routine.  Change the word "PROGRAM" in each Fortran routine
>to "SUBROUTINE" and your job is done.

This "solution" works only if you are willing to give up using Fortran I/O.
There are a number of people who want to be able to use _both_ Fortran I/O
and C I/O.  (In the future, similar issues may apply to error handling and
memory management.)
--
Kurt W. Hirchert     hirchert@ncsa.uiuc.edu
National Center for Supercomputing Applications