Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!linus!philabs!cmcl2!seismo!brl-tgr!gwyn
From: gwyn@brl-tgr.ARPA (Doug Gwyn )
Newsgroups: net.lang.c
Subject: Re: (void) and printf
Message-ID: <566@brl-tgr.ARPA>
Date: Fri, 9-Aug-85 04:25:44 EDT
Article-I.D.: brl-tgr.566
Posted: Fri Aug  9 04:25:44 1985
Date-Received: Mon, 12-Aug-85 01:23:26 EDT
References: <431@brl-tgr.ARPA> <152@laidbak.UUCP> <344@link.UUCP>
Organization: Ballistic Research Lab
Lines: 13

> In System V, they have changed the free() function to "return" void.
> Presumably this was to indicate that it doesn't return any usable
> value.  Trouble is, lint now complains about a return value mis-match,
> since most code hasn't been changed to include a "void free()" line.

Any code that was using the return value of free needed to be fixed
anyway.  The same is true of perror() and several other functions.
My pet gripe was the result type of a signal-catching function, which
should have been void but could not be declared correctly until they
fixed PCC to handle (void (*)()) properly.  Now that the compiler is
working this should be fixed.

Let's get all the types CORRECT.