Path: utzoo!attcan!uunet!husc6!ukma!uflorida!umd5!cvl!elsie!ado From: ado@elsie.UUCP (Arthur David Olson) Newsgroups: comp.lang.c Subject: Re: More ANSI comment help wanted: #define void int vs. #define void char Message-ID: <8087@elsie.UUCP> Date: 6 Jun 88 13:47:01 GMT References: <8085@elsie.UUCP> <8023@brl-smoke.ARPA> Organization: NIH-LEC, Bethesda, MD Lines: 16 < < The response I received (was marked "Not an official X3J11 document"), < < said that while "#define void char" might be better when it comes to < < pointers, there were other cases where "#define void int" was better. < < Can anyone give a concrete example? < < . . .when compiling code such as < void func() { extern void exit(); /* ... */ } < . . .[u]sing char instead of int would not only gain nothing, but it would < introduce possible error (since in such an implementation, exit() would < probably be defaulted to return int). If someone could explain the error possibly being introduced here, I'd appreciate it. -- Market swaps ends for Chinese native. (5) ado@ncifcrf.gov ADO is a trademark of Ampex.