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!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!panda!talcott!harvard!seismo!brl-tgr!ron
From: ron@brl-tgr.ARPA (Ron Natalie <ron>)
Newsgroups: net.lang.c
Subject: Re: typedef'ing void
Message-ID: <9137@brl-tgr.ARPA>
Date: Mon, 11-Mar-85 22:27:20 EST
Article-I.D.: brl-tgr.9137
Posted: Mon Mar 11 22:27:20 1985
Date-Received: Thu, 14-Mar-85 04:41:34 EST
References: <454@harvard.ARPA>
Distribution: net
Organization: Ballistic Research Lab
Lines: 13

> I just discovered that our C compiler (4.2 cc) does not allow
> void to be typedef'ed; furthermore, it gives an error message
> that I haven't otherwise seen.  This suggests that this is its
> intended behaviour, and not another void bug.
> 
> Is there any reason to disallow new names for void?  Is this
> a bug or a feature?
> 
Doesn't surprise me.  Void seems to be a second class citizen in
the 4.2 compiler, kinda hacked in.  You can't declare pointers
to functions returning void.

-Ron