Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!ptsfa!pttesac!vanam
From: vanam@pttesac.UUCP (Marnix van Ammers)
Newsgroups: comp.sys.amiga
Subject: Re: replacement for frags
Message-ID: <413@pttesac.UUCP>
Date: Sun, 19-Apr-87 14:11:50 EST
Article-I.D.: pttesac.413
Posted: Sun Apr 19 14:11:50 1987
Date-Received: Sun, 19-Apr-87 20:57:06 EST
References: <3148@jade.BERKELEY.EDU> <2362@cit-vax.Caltech.Edu> <671@unccvax.UUCP> <3204@jade.BERKELEY.EDU>
Reply-To: vanam@pttesac.UUCP (Marnix van Ammers)
Organization: Pacific*Bell ESAC, San Francisco
Lines: 39

In article <3204@jade.BERKELEY.EDU> mwm@eris.BERKELEY.EDU (Mike (My watch has windows) Meyer) writes:
>In article <671@unccvax.UUCP> fwp@unccvax.UUCP (Rick Pasotto) writes:
>>Why do I get the following errors when I try to compile the frags

>Your problem is your compiler. There are two possible solutions:
>
>1) Buy a compiler that understands function prototypes, and use it
>	instead (1/2 :-).

I had never heard of prototypes before.  Don't recall reading about
them in my (old) C books.  But they sound like a good idea.  I guess
they show the types of arguments passed to a function as well as
what the function returns.

Maybe Manx will add prototypes to their Aztec-C compiler one day.  In
the meantime I guess Manx users can change

void Long_To_ASCII(long, char *, int);

to

#ifndef AZTEC_C
  void Long_To_ASCII(long, char *, int);
#else
  void Long_To_ASCII();
#endif

or if that looks too messy, to

void Long_To_ASCII(/* long, char *, int */);

I really liked the heavy documentation in the frags program.  I also
like the small executable.

Marnix
-- 
Marnix (ain't unix!) A.  van\ Ammers	Work: (415) 545-8334
Home: (707) 644-9781			CEO: MAVANAMMERS:UNIX
UUCP: {ihnp4|ptsfa}!pttesac!vanam	CIS: 70027,70