Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!umd5!cvl!elsie!ado
From: ado@elsie.UUCP (Arthur David Olson)
Newsgroups: comp.lang.c
Subject: Re: #define void int vs. #define void char
Message-ID: <8092@elsie.UUCP>
Date: 11 Jun 88 15:38:39 GMT
References: <8085@elsie.UUCP> <8023@brl-smoke.ARPA> <8087@elsie.UUCP> <8068@brl-smoke.ARPA>
Organization: NIH-LEC, Bethesda, MD
Lines: 27

A response to an earlier article of mine convinces me that I failed to be
clear and succinct.  Let me try again.

QUESTION 1.
	What's an example of code that compiles but does the wrong thing if you
		#define void int
	?

QUESTION 2.
	What's an example of code that compiles but does the wrong thing if you
		#define void char
	?
==============================================================================
Here are my best answers so far:

ANSWER 1.
	The code
		extern void * malloc();

		char * getten() { return malloc(10); }
	on machines where (int *) != (char *).

ANSWER 2.
	I know of no such code.
==============================================================================
If you have better answers, I'd appreciate hearing from you.
-- 
	ado@ncifcrf.gov			ADO is a trademark of Ampex.