Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cwjcc!gatech!hubcap!ncrcae!ncr-sd!hp-sdd!hplabs!hpda!hpwala!cfisun!ima!mirror!ssi3b1!ssibbs!jac
From: jac@ssibbs.UUCP (James Crotinger)
Newsgroups: comp.sys.amiga.tech
Subject: Re: New RKM:AutoDocs & Includes  MAJOR problem!
Summary: Prototypes
Message-ID: <108@ssibbs.UUCP>
Date: 12 Mar 89 05:55:36 GMT
References: <1467@percival.UUCP> <6195@cbmvax.UUCP> <15751@oberon.USC.EDU>
Organization: Sangho's Public Access Unix, Cambridge, MA
Lines: 26

In article <15751@oberon.USC.EDU>, papa@pollux.usc.edu (Marco Papa) writes:
> 
> "Any actual argument of type float are converted to double before the call;
> any of type char or short are converted to int;"
>                     ^^^^^                  ^^^

   If a function is prototyped, this is no longer necessarily the case. 
These required conversions used to be a major source of inefficiency in
trying to do numerical work with C since you really don't need double
precision for most things. ANSI addressed this issue by stating that if
a function is prototyped then the extension does not have to take place.

   Speaking of numerical work, when are we likely to see single precision
IEEE libraries, and when we do finally get them, will the compilers support
using both float and double in the same program? Many numerical problems
only require double precision in a few critical areas to eliminate accuracy
problems, and it is a waste to use double precision everywhere else. 
> 
> -- Marco Papa 'Doc'
> 
   jim

-- 
                                        
                               Jim Crotinger
                               crotinger%mit.mfenet@nmfecc.arpa