Re: Supporting byte-addressability on word-addressed hardware

David Keppel <pardo@cs.washington.edu> wrote:
>>[Pointer representations for GNU CC]
[...]
> int *p = malloc (sizeof(int));
> free (p);
>
>The correct solution is to cast `p' to a `char *' before passing it to
>`free'. However, you might be unwilling to do this (or force your
>users to do this) and failing to use the casts can lead to mysterious
>failures. Your call.


Note that this code is perfectly correct if free is correctly declared
previously. I don't have a copy of K&R II at hand, so I can't check
which include-file free is supposed to declared in, but a quick check
on two machines indicates that it's probably stdlib.h.


In short, this isn't such a big problem problem as you are making
it. Especially since a lot of compilers can warn you about undeclared
functions!


Gcc warns you about this if you uses -Wall, and it was gcc he was
porting...


--

Return to the comp.compilers page.
Search the comp.compilers archives again.