Path: utzoo!attcan!uunet!husc6!bloom-beacon!tut.cis.ohio-state.edu!lvc From: lvc@tut.cis.ohio-state.edu (Lawrence V. Cipriani) Newsgroups: comp.lang.c Subject: Re: More ANSI comment help wanted: #define void int vs. #define void char Message-ID: <15105@tut.cis.ohio-state.edu> Date: 6 Jun 88 02:53:01 GMT References: <8085@elsie.UUCP> Organization: The Ohio State University Dept of Computer and Information Science Lines: 25 In article <8085@elsie.UUCP> ado@elsie.UUCP (Arthur David Olson) writes: ... >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? void blob() { ... } would become: int blob() { ... } instead of: char blob() { ... } Old C libraries commonly don't list the function return type to indicate a void but it really means int. The #define would retain compatibility with the old libraries. Anyone got better examples? -- Larry Cipriani, AT&T Network Systems and Ohio State University Domain: lvc@tut.cis.ohio-state.edu Path: ...!cbosgd!osu-cis!tut.cis.ohio-state.edu!lvc (strange but true)