Contemplating the void
26-Mar-86 00:05:07
Sb: #12549-Contemplating the void
Fm: Dave Haynie/C128 Land 76703,2047
To: Steve Allen 73277,620
This message turned up in search, but its forum couldn’t be identified from the original transcript, so it may not be linked into its thread.
As I recall the specification of the void type, it generally means, at least
in a function definition, like void foo(), etc. that NO VALUE is returned at
all, or at least nothing meaningful. I'm not sure about void *. But if manx
uses it as a generic type, it MAY not be portable. Also, my C book tells me
that any type may be cast to void, but that void may not be cast to anything.
I don't know if this also applies to void *, but it seems possible. Maybe
someone out there knows the official K&R position on this. I kind of like
thinking of an untyped area of memory as UBYTE * or something like that, in
that it really implies no special meaning to that area (unlike char, int,
float, etc.); this is just a personal pref. -Dave Haynie