Re: calloc and set var to NULL

Le 06/07/2014 18:56, Chris Cappuccio a écrit : > > This is technically correct. So are you, but only because NULL and > zero happen to be the same value. They don't necessarily have to > be, it is implementation-defined. (Of course there would be > fireworks everywhere if they weren't, since lots

Re: calloc and set var to NULL

On Sun, Jul 06, 2014 at 09:56:05AM -0700, Chris Cappuccio wrote: > Denis Fondras [open...@ledeuns.net] wrote: > > Hello all, > > > > If I understand correctly calloc(), allocated space is already > > initialized to zero. So setting var to NULL is not needed. > > > > Is it alright or should it be

Re: calloc and set var to NULL

Le 06/07/2014 18:50, Otto Moerbeek a écrit : > Please use cvs diff, whcih includes more context. Now we have no idea > which parse.y you are patching. > Sorry for this oversight and thank you for the mention of cvs diff. Index: parse.y

Re: calloc and set var to NULL

Denis Fondras [open...@ledeuns.net] wrote: > Hello all, > > If I understand correctly calloc(), allocated space is already > initialized to zero. So setting var to NULL is not needed. > > Is it alright or should it be kept "just in case" ? > > Regards, > Denis > > --- parse.y.origSun Ju

Re: calloc and set var to NULL

On Sun, Jul 06, 2014 at 05:54:59PM +0200, Denis Fondras wrote: > Hello all, > > If I understand correctly calloc(), allocated space is already > initialized to zero. So setting var to NULL is not needed. > > Is it alright or should it be kept "just in case" ? > > Regards, > Denis > > --- parse

calloc and set var to NULL

Hello all, If I understand correctly calloc(), allocated space is already initialized to zero. So setting var to NULL is not needed. Is it alright or should it be kept "just in case" ? Regards, Denis --- parse.y.origSun Jul 6 17:51:59 2014 +++ parse.y Sun Jul 6 17:52:15 2014 @@ -3