Path: utzoo!attcan!uunet!seismo!sundc!pitstop!sun!oliveb!bunker!garys From: garys@bunker.UUCP (Gary M. Samuelson) Newsgroups: comp.lang.c Subject: Re: #define void int vs. #define void char Message-ID: <3743@bunker.UUCP> Date: 30 Jun 88 17:59:06 GMT References: <8085@elsie.UUCP> <11823@mimsy.UUCP> Reply-To: garys@bunker.UUCP (Gary M. Samuelson) Organization: Bunker Ramo, an Olivetti Company, Shelton, Ct Lines: 20 In article <11823@mimsy.UUCP> chris@mimsy.UUCP (Chris Torek) writes: ==[but ado was told that] while "#define void char" might be better when ==it comes to pointers, there were other cases where "#define void int" ==was better. = ... Had the standard included the line = typedef void *pointer_t; /* or (char *) */ =in, one could implement pointer_t on old compilers virtually =painlessly. =Of course, `void *' does somewhat carry the notion that the pointer =does not point to anything in particular, or at least not to anything =concrete. I've got it ! For the generic pointer type, how about: (noalias *) Guaranteed not to point to anything in particular! :-) :-) :-? Gary Samuelson