Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!mailrus!iuvax!rutgers!bellcore!tness7!ninja!cpe!tif
From: tif@cpe.UUCP
Newsgroups: comp.sys.ibm.pc
Subject: Re: Function declarations (was: MSC
Message-ID: <12400016@cpe>
Date: 6 Sep 88 16:59:00 GMT
References: <64@cybaswan.UUCP>
Lines: 22
Nf-ID: #R:cybaswan.UUCP:64:cpe:12400016:000:601
Nf-From: cpe.UUCP!tif    Sep  6 11:59:00 1988


Written  6:40 pm  Sep  4, 1988 by bigtex.UUCP!james in cpe:comp.sy.ibm.pc
>It's worse than all that.  ANSI C permits conflicting function
>declarations without a warning - indeed it is required that no warning
>be given. ...
>... and I can't conceive of any
>implementation where the ANSI C requirement is actually useful.

I can.  When you want to use a return value in more than one way.

a() {
	int *malloc(), *x;
	x = malloc(sizeof(int));
}

b() {
	long *malloc(), *x;
	x = malloc(sizeof(long));
}

			Paul Chamberlain
			Computer Product Engineering, Tandy Corp.
			{convex,killer}!ninja!cpe!tif