Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!decvax!ittatc!dcdwest!sdcsvax!sdcrdcf!hplabs!hpda!hpisoa2!hpitg!gilbbs!mc68020@gilbbs
From: mc68020@gilbbs
Newsgroups: net.lang.c
Subject: Re: void *
Message-ID: <194@gilbbs>
Date: Sat, 26-Apr-86 10:34:00 EDT
Article-I.D.: gilbbs.194
Posted: Sat Apr 26 10:34:00 1986
Date-Received: Tue, 13-May-86 01:13:14 EDT
References: <728@bentley>
Lines: 20

In article <200@brl-smoke.ARPA>, gwyn@BRL.ARPA (VLD/VMB) writes:
> You're mixing two features of malloc().  Malloc() should return (void *),
> which is a generic pointer type to/from which all other pointer types
> may be cast without loss of information.  (This is the only use of
> (void *), and it is the only universal pointer type; other pointer
> casts can be non-portable.)  Malloc() ALSO guarantees that the pointer
> it returns is suitably aligned for safe casting to ANY pointer type.
> This is a property of malloc(), not of (void *).

   Well, that's just great!  The C compiler on my system doesn't understand
such niceties as void.  So what do we do?  (do *NOT* tell me to get another
compiler, there *IS* no other compiler available for this system!)

-- 
Disclaimer:  I hereby disclaim any and all responsibility for disclaimers.

tom keller
{ihnp4, dual}!ptsfa!gilbbs!mc68020

(* we may not be big, but we're small! *)