void *
ARPA at brl-smoke
ARPA at brl-smoke
Mon Apr 28 20:13:00 AEST 1986
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 */
More information about the Comp.lang.c
mailing list