[TUHS] Did realloc ever zero the new memory?

Dave Horsfall dave at horsfall.org
Sun Sep 13 20:32:14 AEST 2015

On Sun, 13 Sep 2015, markus schnalke wrote:

> > void *alloc(size_t bytes);
> > void *realloc(void *old, size_t want);
> > 
> > void *zalloc(size_t bytes);
> > void *zealloc(void *old, size_t want);
> Please note, that identifiers are usually remembered by sound not by 
> letter sequence. `zalloc' and `zealloc' are likely to be pronounced 
> similar and thus there is a good chance that this leads to confusion and 
> errors. Furthermore, `calloc' and `zalloc' are prone to be pronounced 
> equally or understood equally, especially by non-native speakers.

That, of course, depends upon how you pronounce "z".  In this part of the 
world, it's "zed".  No confusion with "see" here down-under...

Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."
 I'll support shark-culling when they have been observed walking on dry land.

More information about the TUHS mailing list