> > For safety, I propose that xmalloc zero out the memory it allocates. Any > > comments or rebuttals? > > > For safety, I would prefer it does not. I don't think we should > use non-portable solutions to cover up the faults of badly-written > software. I'd feel more comfortable using the software knowing that > some classes of errors would have been discovered. So you would rather have problems occur *randomly* depending on what the values *happen* to be at the moment? Personally, if something is not properly initialized I'd like a core dump every time so that it is found and fixed quickly. -- Cheers, Derek _____________________________________________________________________ Derek Scherger Echologic Software Corporation mailto:[EMAIL PROTECTED] http://www.echologic.com
- question (preference?) about xmalloc Noel L Yap
- Re: question (preference?) about xmalloc Larry Jones
- Re: question (preference?) about xmalloc Donald Sharp
- Re: question (preference?) about xmalloc Russ Allbery
- Re: question (preference?) about xmalloc Michael Gersten
- Re: question (preference?) about xmalloc Greg A. Woods
- Re: question (preference?) about xmalloc David Thornley
- Re: question (preference?) about xmalloc Derek Scherger
- Re: question (preference?) about xmalloc Jonathan M. Gilligan
- Re: question (preference?) about xmalloc David Thornley
- Re: question (preference?) about xmalloc Noel L Yap
- Re: question (preference?) about xmalloc Donald Sharp
- Re: question (preference?) about xmalloc Larry Jones
- Re: question (preference?) about xmalloc Noel L Yap
- Re: question (preference?) about xmalloc Donald Sharp
- Re: question (preference?) about xmalloc Larry Jones
- Re: question (preference?) about xma... Donald Sharp
- Re: question (preference?) abou... Larry Jones
