Xref: utzoo comp.lang.c:34263 comp.lang.fortran:4151
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!src.honeywell.com!msi.umn.edu!noc.MR.NET!uc!shamash!timbuk!juniper09!ds
From: ds@juniper09.cray.com (David Sielaff)
Newsgroups: comp.lang.c,comp.lang.fortran
Subject: Re: Fortran vs. C for numerical work (SUMMARY)
Message-ID: <131854.15591@timbuk.cray.com>
Date: 27 Nov 90 19:29:47 GMT
References: <BGLENDEN.90Nov21003342@mandrill.cv.nrao.edu> <21884@orstcs.CS.ORST.EDU> <1990Nov21.220816.15220@rice.edu> <2173@tuvie> <BGLENDEN.90Nov26162335@mandrill.cv.nrao.edu> <1990Nov27.175023.26039@zoo.toronto.edu>
Organization: Cray Research, Inc., Eagan, MN
Lines: 21

In article <1990Nov27.175023.26039@zoo.toronto.edu> henry@zoo.toronto.edu (Henry Spencer) writes:
>In article <BGLENDEN.90Nov26162335@mandrill.cv.nrao.edu> bglenden@mandrill.cv.nrao.edu (Brian Glendenning) writes:
>>3. In fortran functions like sin, cos, ** are intrinsic.
>>
>>I think that ANSI C has a method by which compilers may make sin, cos
>>etc intrinsic, but I don't remember how it works...
>
>It's really very simple:  they are allowed to be intrinsic, essentially.
>There is no complexity or mystery.  C and Fortran are no longer different
>in this regard, except insofar as the Fortran libraries are larger.
>

At the risk of beating a dead horse, the only gotcha here is that
if `static double sin(double);' is seen in a compilation unit, the
compiler had better wait to find the definition in the compilation
unit, and not treat calls to sin() as an intrinsic (after it has seen
the declaration, anyway).  This is a situation which does not arise
in FORTRAN.

Dave Sielaff
Cray Research, Inc.