Xref: utzoo comp.lang.c:32068 comp.lang.fortran:3832
Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!apctrc!drd!mike
From: mike@DRD.Com (Mike Rovak)
Newsgroups: comp.lang.c,comp.lang.fortran
Subject: Re: Fortran Main with C I/O
Summary: Don't panic
Keywords: peace, calm, smart
Message-ID: <1990Sep21.132232.11305@DRD.Com>
Date: 21 Sep 90 13:22:32 GMT
References: <1044@helens.Stanford.EDU> <1990Sep20.221007.8515@cs.dal.ca>
Sender: Mike Rovak
Followup-To: comp.lang.c,comp.lang.fortran
Distribution: usa
Organization: DRD Corporation
Lines: 29

bill%biomel@cs.dal.ca wrote:
} In article <1044@helens.Stanford.EDU> joe@hanauma.Stanford.EDU (Joe Dellinger) writes:
} >
} >We just got the latest OS upgrade, which is the first one to be
} >"POSIX-compliant". Now we are told "if you want to be able to use C I/O
} >you'll have to have your mains in C"! This means rewriting a LOT of software.
} >
} >	OK. Are we really a special case? Is there anybody else out there
} >that writes Fortran mains but uses C to do the I/O? If so, let me know, so
} >we can make a case to them not to do this!
} 
} 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.

-- Mike

------------------------------------------------------------------------
Disclaimer: My opinions do not necessarily reflect those of my employer.
========================================================================
------------------------------------------------------------------------
     mike@DRD.Com  
     uunet!apctrc!drd!mike
========================================================================