Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!harvard!caip!ll-xn!cit-vax!jon
From: jon@cit-vax.Caltech.Edu (Jonathan P. Leech)
Newsgroups: net.lang.c
Subject: Re: malloc()
Message-ID: <479@cit-vax.Caltech.Edu>
Date: Wed, 14-May-86 05:00:45 EDT
Article-I.D.: cit-vax.479
Posted: Wed May 14 05:00:45 1986
Date-Received: Fri, 16-May-86 01:49:46 EDT
References: <866@ttrdc.UUCP> <815@bentley.UUCP>
Reply-To: jon@cit-vax.UUCP (Jonathan P. Leech)
Organization: California Institute of Technology
Lines: 20

Summary:
Expires:
Sender:
Followup-To:
Distribution:

Organization : California Institute of Technology
Keywords:

In article <815@bentley.UUCP> kwh@bentley.UUCP (KW Heuer) writes:
>
>This is what I started to mention once before, and picked up a lot of "no,
>you don't understand how it works" messages (sigh).  I saw the need for a
>"ALIGN *" datatype, and was hoping "void *" would be it.  (Nope, just a
>useless synonym for "char *").  The idea would be that, just as it's always
>legal to cast any pointer into a "char *", it would be legal to cast *from*
>"ALIGN *" to any pointer.  Then lint would shut up about malloc()!
>

    I don't think 'void *' is useless. What do you  do	on  a  machine
where it's NOT 'always legal to cast any pointer into a "char *"'?   I
find 'void *' most wonderful and useful in C++.
-- 
    Jon Leech (jon@csvax.caltech.edu || ...seismo!cit-vax!jon)
    Caltech Computer Science Graphics Group
    __@/