Xref:	news-dnh.mv.net comp.os.msdos.djgpp:2541
Path:	news-dnh.mv.net!mv!news.sprintlink.net!europa.chnt.gtegsc.com!news.kreonet.re.kr!news.dacom.co.kr!news.uoregon.edu!usenet.eel.ufl.edu!netline-fddi.jpl.nasa.gov!goonsquad.spies.com!uuwest!alcyone!max
From:	max AT alcyone DOT darkside DOT com (Erik Max Francis)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Q: Moving from V1.12.3 to V2.0
Date:	Tue, 10 Oct 95 11:06:38 PDT
References:	<45c2jl$ijk AT sisko DOT dnaco DOT net>
Organization:	&tSftDotIotE
Lines:	14
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway:	from newsgroup comp.os.msdos.djgpp

eheft AT sisko DOT dnaco DOT net (eheft) writes:

> Found one problem ... v2.0 doesn't initilize all your malloced
> space to zero thus causing the FPE error when used?

This is in perfect compliance with the ANSI C standard.  Dynamically 
allocated memory is not guaranteed to be zeroed -- in fact, on the vast 
majority of compilers this is most emphatically not the case!


Erik Max Francis, &tSftDotIotE // uuwest!alcyone!max, max AT alcyone DOT darkside DOT com
San Jose, CA, USA // 37 20 07 N  121 53 38 W // GIGO, Omega, Psi // the 4th R!
H.3`S,3,P,3$S,#$Q,C`Q,3,P,3$S,#$Q,3`Q,3,P,C$Q,#(Q.#`-"C`- // 1love // folasade
_Omnia quia sunt, lumina sunt._ // mc2? oo?  Nah. // http://www.spies.com/max/

- Raw text -