Xref: utzoo comp.lang.c:32492 comp.lang.fortran:3877
Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!zaphod.mps.ohio-state.edu!ncar!ico!haddock!karl
From: karl@haddock.ima.isc.com (Karl Heuer)
Newsgroups: comp.lang.c,comp.lang.fortran
Subject: Re: Fortran Main with C I/O
Message-ID: <18388@haddock.ima.isc.com>
Date: 3 Oct 90 03:37:44 GMT
References: <1990Sep21.132232.11305@DRD.Com> <1990Oct1.155217.24452@ux1.cso.uiuc.edu> <9794@ccncsu.ColoState.EDU> <1990Oct2.124559.19410@cunixf.cc.columbia.edu>
Reply-To: karl@haddock.ima.isc.com (Karl Heuer)
Distribution: usa
Organization: Interactive Systems, Cambridge, MA 02138-5302
Lines: 17

In article <1990Oct2.124559.19410@cunixf.cc.columbia.edu> shenkin@cunixf.cc.columbia.edu (Peter S. Shenkin) writes:
>No one here has mentioned just why or how the POSIX standard mandates that C
>IO can't be used with a Fortran main.
>
>How/why does this limitation arise in POSIX?

POSIX does not mandate any such thing.  The situation is just that one
particular vendor, in the process of providing POSIX support, no longer
allows that particular mixed-language kludge.

The problem is that there is some initialization that needs to be done
before the program starts.  Evidently this is done by the C linkage but not
by Fortran.  If the vendor is committed to supporting the language-mixing
you need, then they ought to be able to put the appropriate hooks into the
Fortran startup as well.

Karl W. Z. Heuer (karl@kelp.ima.isc.com or ima!kelp!karl), The Walking Lint