Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!nrl-cmf!ukma!gatech!purdue!decwrl!sun!pitstop!sundc!seismo!uunet!tektronix!tekcrl!tekchips!danw
From: danw@tekchips.LABS.TEK.COM (Daniel E. Wilson)
Newsgroups: comp.sys.atari.st
Subject: Re: nullfilling
Message-ID: <3701@tekcrl.LABS.TEK.COM>
Date: 14 Mar 89 21:56:15 GMT
References: <8903010551.AA25974@ucbvax.Berkeley.EDU>
Sender: ftp@tekcrl.LABS.TEK.COM
Lines: 14

In article <8903010551.AA25974@ucbvax.Berkeley.EDU>, U46050@UICVM.BITNET (JOHN ZAFIRIS) writes:
> (people will think before writting code that
> assumes what it shouldn't (blank mem) (yes, I know, K&R says this and
> K&R says that... hooey!  I don't like C anyway).  Best of all, this is

  K&R say nothing about clearing memory.  Only static variables are cleared
and this is done by the compiler.  What K&R say about memory allocated by
malloc is that the contents are garbage and that it must be initialize by
the programmer.

  Anyone programming in C that assumes that malloced memory is zero is
making a very big mistake.

Dan Wilson