Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!emory!mephisto!mcnc!uvaarpa!murdoch!astsun.astro.Virginia.EDU!gl8f
From: gl8f@astsun.astro.Virginia.EDU (Greg Lindahl)
Newsgroups: comp.lang.fortran
Subject: Re: f2c used as fortran error checker: one experience
Message-ID: <1990Aug28.051657.11791@murdoch.acc.Virginia.EDU>
Date: 28 Aug 90 05:16:57 GMT
References: <11678@chaph.usc.edu>
Sender: news@murdoch.acc.Virginia.EDU
Organization: Department of Astronomy, University of Virginia
Lines: 13

In article <11678@chaph.usc.edu> ajayshah@aludra.usc.edu (Ajay Shah) writes:
>
>In this demo below, f2c traps one of the few million problems with
>fortran: not checking for the number of parameters across call,
>but isn't able to find inconsistent types.  Any ideas on how that
>is to be done?  

Run the program through f2c -A -P, then edit the .c file to include
the prototypes generated by f2c, then run it through an ANSI C
compiler, such as gcc.

--
"In fact you should not be involved in IRC." -- Phil Howard