RE: question (preference?) about xmalloc

[Leeuw, Guus (G.)]

Donald,

> -----Original Message-----
> From: Donald Sharp [mailto:[EMAIL PROTECTED]]

> I think both are 'right' solutions.  Larry's solution ensures that the
> constructor function knows the right thing to do.  Forcing xmalloc
> to 0 out the newly malloc'ed block is also a good thing to do.  If 
> you do not 0 out a new block of memory, it's possible to accidently
> ( via a bug in the program ) write over memory that you didn't intend
> to thus causing a crash later on in the program.  If the memory 
> has been zero'ed out you'll get a null pointer dereference right there
> thus helping debug the problem faster.

Understand, though, that 0 do not always denote NULL pointers or NULL
floads...
If at all, then NULL (and not 0) is the way to go.

Guus