Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!mcvax!ukc!cstvax!simon
From: simon@cstvax.UUCP (Simon Brown)
Newsgroups: net.lang.c
Subject: Re: expr?(void):(void)
Message-ID: <2@cstvax.UUCP>
Date: Mon, 4-Aug-86 13:37:30 EDT
Article-I.D.: cstvax.2
Posted: Mon Aug  4 13:37:30 1986
Date-Received: Wed, 6-Aug-86 02:26:01 EDT
References: <501@bunny.UUCP> <500@copper.UUCP> <273@watmath.UUCP> <1327@ncoast.UUCP>
Reply-To: simon@cstvax.UUCP (Simon Brown)
Distribution: net
Organization: Comp. Sc., Edinburgh Univ., Scotland
Lines: 33

In article <1327@ncoast.UUCP> allbery@ncoast.UUCP (Brandon Allbery) writes:
>
>| void f3(which)
>| {
>|     extern void f1(),f2();
>|     which?f1():f2();
>| }
>| cc(1) gives an "incompatible types" error.
>
>That's not a bug, it's a feature.  Literally.
>

Is this the same feature that disallows

	f(which)
	{
		extern void f1(), f2();
		void (*fp)();
		fp = which? f1 : f2;
		(*fp)();
	}


which gives the same "incompatible types" error, but which can't be explained
as a confusion between functions and precedures.

-- 

			-------------------------------------------------
			| Simon Brown,	Dept. of Computer Science,	|
			|		Edinburgh University		|
			| ...!mcvax!ukc!cstvax!simon			|
			-------------------------------------------------