Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!IRO.UMontreal.CA!kovic.IRO.UMontreal.CA!martin
From: martin@IRO.UMontreal.CA (Daniel Martin)
Newsgroups: comp.sys.amiga.tech
Subject: Re: functions.h
Message-ID: <1990Dec31.193848.26538@IRO.UMontreal.CA>
Date: 31 Dec 90 19:38:48 GMT
References: <9871@fy.sei.cmu.edu> <1990Dec17.144036.4219@diku.dk>
Sender: news@IRO.UMontreal.CA
Reply-To: martin@IRO.UMontreal.CA (Daniel Martin)
Organization: Universite de Montreal
Lines: 50

In article <1990Dec17.144036.4219@diku.dk> bombadil@diku.dk (Kristian Nielsen) writes:
>jol@sei.cmu.edu (Jun Lee) writes:
>>Hi.
>>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.  
>
>The Lattice/SAS equivalent is <proto/all.h>. It contains function
>definitions with type checking as provided in ANSI-C, and also saves you
>some typecasts.
...
>  As an added bonus, the Lattice include (I dunno about Aztec) also has
>(optional) #pragma - definitions, enabling the compiler to make more
>efficient system calls than is possible using the stubs in amiga.library.

   <functions.h> is a general include file defining globals and return
values of functions for the Aztec Compiler.  With the 2.0 includes, the
functions.h contains among other things the clib/all_protos.h  and
pragma/all_lib.h wich are equivalent to Lattice proto/all.h and pragma
definitions.


>BTW, at least with Lattice, you needn't include the definitions for ALL the
>system calls, you can restrict you program to only include the parts of the
>system that you are using, by specifying, for example 
>   #include <proto/intuition.h>

   You can restrict includes with all versions (3.6 and up) of MANX Aztec C.
I wonder wich C compiler woudn't allow restrictions.

>Of course, if you don't mind about compile times, it is more comfortable
>just to include the entire set.

   Or you just make a big precompiled header file, put it in ram, and use
it when compiling.  Mines 300k, and the compile times are reasonnably fast
(EASILY under 30 sec. to compile AND link a 1000 lines source code, and
around 3.5 sec. to compile AND link an "Hello World" program, on a 
A3000/25MHz/10Meg RAM.).

>Kristian Nielsen
   Daniel.

Disclaimer: I'm only a satisfied user of MANX Aztec C compiler since 87.
            Now if only I could put my hand on a good C++...

--
    // Daniel Martin                            Universite de Montreal   \\
   //  MediaLab, ca vous regarde!               C.P. 6128, Succursale A,  \\
\\//   Mail: martin@IRO.UMontreal.CA            Montreal (Quebec), CANADA, \\//
 \/    Tel.: (514) 343-6111 poste 3494          H3C 3J7                     \/