Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!usc!samsung!olivea!uunet!cbmvax!cbmehq!cbmdeo!adspdk!hclausen
From: hclausen@adspdk.UUCP (Henrik Clausen)
Newsgroups: comp.sys.amiga.tech
Subject: Re: functions.h
Message-ID: <185dbccc.ARN1280@adspdk.UUCP>
Date: 15 Dec 90 09:32:44 GMT
References: <1951.AA1951@caleb>
Reply-To: hclausen@adspdk.UUCP
Followup-To: comp.sys.amiga.tech
Organization: Graffiti Data
Lines: 28

In article <1951.AA1951@caleb>, Jim Pritchett writes:

> 
> In article <9871@fy.sei.cmu.edu> jol@sei.cmu.edu (Jun Lee) wrote:
> 
> > Can anyone tell me what is contained in <function.h?  I take it this is
> > a Aztec C thing and I was wondering what would be a comparable include
> > file on a Lattice 5.1.  
> 
> It contains the type definitions for the Amiga functions.  Using it properly
> should eliminate many ptr->int type errors.  I don't know what Lattice
> does for this.

   The Prototype files that come with Lattice are the equivalent. This is
great for catching incorrect parameter passings and such. Using prototypes
for your own functions (compiler generated) is very neat, I set the
compiler up to warn me about functions without proto's, and catch quite a
few bugs at compile time rather than at link or execute time.

   Use the pragma include files as well, that's quite a reduction in code
size. Precompiled headers is almost a must for that many header files.

                                         -Henrik

______________________________________________________________________________
| Henrik Clausen, Graffiti Data | If the Doors of Perception where cleansed, |
| ...{pyramid|rutgers}!cbmvax!  | Man would see Reality as it is - Infinite. |
\______cbmehq!adspdk!hclausen___|_________________________________W. Blake___/