Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-crg!nike!think!ima!haddock!karl
From: karl@haddock
Newsgroups: net.lang.c
Subject: Re: Orphaned Response
Message-ID: <86900008@haddock>
Date: Tue, 12-Aug-86 14:09:00 EDT
Article-I.D.: haddock.86900008
Posted: Tue Aug 12 14:09:00 1986
Date-Received: Wed, 13-Aug-86 01:42:33 EDT
References: <273@watmath.UUCP>
Lines: 19
Nf-ID: #R:watmath.UUCP:273:haddock:86900008:000:864
Nf-From: haddock!karl    Aug 12 14:09:00 1986


dg_rtp!throopw (Wayne Throop) writes:
>(As a small nit, I'd druther that the draft standard would allow a void
> expression to be cast to void, but that's a fairly small quibble.)

Void to void is illegal?  Sonofagun, you're right, and they even made it
explicit.  How strange.

Here's another restriction I just encountered: you can't typedef to void.
This is probably because typedef is syntactically a storage class specifier,
so it "looks like" an attempt to declare a void variable.

I was trying to declare "typedef void dead;" so that I could distinguish
between functions that return nothing (void perror(char *), setbuf(FILE *,
char *), nullf(void)) from those that don't return (dead exit(int),
abort(void), longjmp(jmp_buf, int)).  Again, it's a small quibble; I'll
just use #define instead.

Karl W. Z. Heuer (ihnp4!ima!haddock!karl), The Walking Lint