Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!oddjob!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.lang.c
Subject: Re: Type checking in conditional expressions
Message-ID: <9065@mimsy.UUCP>
Date: Wed, 21-Oct-87 13:52:23 EDT
Article-I.D.: mimsy.9065
Posted: Wed Oct 21 13:52:23 1987
Date-Received: Sat, 24-Oct-87 06:50:15 EDT
References: <186@wright.EDU>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 21
Keywords: HELP!

In article <186@wright.EDU> jholbach@wright.EDU (Jim Holbach) writes:
<... I tried some simple test cases like
<	main()
<		{ void function();
<		  void (*name)();
<		  name = function;
<		  name = (0?name:function);
<		}
<I figured if name and function were truly incompatible, the first 
<assignment should fail to compile, but it didn't. At the same time, 
<the compiler complained about the conditional expression in the last line.

You have a buggy compiler.  A number of compilers cannot handle
pointer-to-function-returning-void (4.2BSD in particular).  If
you `#define void int' the problem sort of goes away.

On the other hand, all the type checking you are getting via preprocessor
macros you can also get by using lint, and lint will do a better job.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7690)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris