> return malloc(size ? size : 1);
>
> That's a constant pointer, and you can read 1 byte beyond it (the '\0')
The '\0'? You mean the pseudorandom byte that happens to be in the
heap at the beginning of the malloc block?
> Anything wrong with that as parrot's malloc wrapper?
That would keep both SUSv2 (me as a proxy :-) and Simon happy :-)
> [does purify report on an unitialised memory read that is never actually
> used? If so, is it worth writing something for that malloc(1), possibly
> only in #ifdef PANDER_TO_PURIFY so that we can increase signal to noise?]
>
> Nicholas Clark
--
$jhi++; # http://www.iki.fi/jhi/
# There is this special biologist word we use for 'stable'.
# It is 'dead'. -- Jack Cohen
