home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.isis
- Path: sparky!uunet!caen!batcomputer!cornell!ken
- From: ken@cs.cornell.edu (Ken Birman)
- Subject: Re: NIX Problems with the definition of NULLARG in i
- Message-ID: <1992Nov8.184128.11599@cs.cornell.edu>
- Organization: Cornell Univ. CS Dept, Ithaca NY 14853
- References: <1992Nov7.231718.1707@msuinfo.cl.msu.edu> <1992Nov7.234834.7701@msuinfo.cl.msu.edu>
- Date: Sun, 8 Nov 1992 18:41:28 GMT
- Lines: 26
-
- In article <1992Nov7.234834.7701@msuinfo.cl.msu.edu> adc@tardis.msu.edu writes:
- >Sorry, another application I was using had its own idea on what VOID
- >should be.
-
- Glad you tracked it down. The reason we #define VOID as void on some
- systems and char on others is that one whole "line" of C compilers
- barfs on "void *" as an argument type to a procedure. If these see
- void abc(xyz)
- void *xyz;
- {
- void *zyx;
- zyx = xyz;
- }
- they tend to dump core, or claim that xyz is an undefined variable, or
- just generate wrong code.
-
- So, we learned back in 1987 that it was better to use VOID instead of
- void all through our source, and #define VOID to be char on compilers
- that don't correctly implement the C language...
-
- Sorry that you ran into this problem. Probably, we should rename this
- type "ISIS_VOID" to avoid future encounters with the same thing.
- --
- Kenneth P. Birman E-mail: ken@cs.cornell.edu
- 4105 Upson Hall, Dept. of Computer Science TEL: 607 255-9199 (office)
- Cornell University Ithaca, NY 14853 (USA) FAX: 607 255-4428
-