More ANSI comment help wanted: #define void int vs. #define void char
Arthur David Olson
ado at elsie.UUCP
Mon Jun 6 23:47:01 AEST 1988
< < 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 at ncifcrf.gov ADO is a trademark of Ampex.
More information about the Comp.lang.c
mailing list