Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!bellcore!decvax!ittatc!dcdwest!sdcsvax!sdcrdcf!hplabs!hpda!hpisoa2!hpitg!brl-smoke!ARPA@brl-smoke
From: ARPA@brl-smoke
Newsgroups: net.lang.c
Subject: Re: void *
Message-ID: <326@brl-smoke>
Date: Mon, 28-Apr-86 06:13:00 EDT
Article-I.D.: brl-smok.326
Posted: Mon Apr 28 06:13:00 1986
Date-Received: Tue, 13-May-86 00:27:07 EDT
References: <728@bentley>
Lines: 19

If your C compiler doesn't understand "void" (which has been in
the language for years; X3J11 did not invent it, just (void *)),
or lacks bit fields, enums, struct assignment, __LINE__, decent
library routines, etc., then I would think you would want to get
it fixed.  Even the compiler on my Apple //e understands most of
these (as well as (void *))!  Didn't you pay for vendor support?

I have a header file I #include in my applications, that is set
up on different systems to compensate for such things and to
provide a uniform set of extensions such as boolean data type.
Here are some relevant excerpts for a relatively puny system:

typedef char	*pointer;		/* generic pointer (void *) */
#define	const		/* nothing */	/* (undefine for ANSI C) */
#define	signed		/* nothing */	/* (undefine for ANSI C) */
#define	volatile	/* nothing */	/* (undefine for ANSI C) */
#define	strchr	index			/* 7th Edition UNIX, 4.2BSD */
#define	strrchr	rindex			/* 7th Edition UNIX, 4.2BSD */
#define	void	int			/* K&R Appendix A followers */