Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!apple!usc!cs.utexas.edu!helios!tamuts!n138ct
From: n138ct@tamuts.tamu.edu (Brent Burton)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Novice question about malloc() in Think C
Summary: you betcha!  #include <stdlib.h> got me!
Message-ID: <12651@helios.TAMU.EDU>
Date: 26 Feb 91 06:28:45 GMT
References: <1991Feb25.103404.3662@Neon.Stanford.EDU> <12591@helios.TAMU.EDU> <STEVE.91Feb25153736@huxley.huxley.bitstream.com>
Sender: usenet@helios.TAMU.EDU
Followup-To: comp.sys.mac.programmer
Distribution: usa
Organization: Texas A&M University
Lines: 29

In article <STEVE.91Feb25153736@huxley.huxley.bitstream.com> <steve@bitstream.com> (Stephen Z. Stein) writes:
>In article <12591@helios.TAMU.EDU> n138ct@tamuts.tamu.edu (Brent Burton) writes:
>>   I have had this problem too.
>Because you make the same mistake, I think.
>
>I am virtually certain he was having this error because he forgot to
>
>#include <stdlib.h>

>like it says to in the friendly manual.

>Lesson 1: Read the friendly manual.
>Lesson 2: Pay the syntax!

Steve, (and others)

this will get you everytime.  I went and 'fixed' the code I modified -- 
removed the #defines and included <stdlib.h> and it worked.

This is NOT a simple case of RTFM. I have -- it was "simple" oversight.
Had I been thinking a little more, maybe I could've avoided it... :)

Anyway, thanks to all who replied with a friendly reminder about <stdlib.h>.


             +----------------------+--------------------------+
             | Brent P. Burton      | n138ct@tamuts.tamu.edu   |
             | Texas A&M University | Computer Science/Physics |
             +----------------------+--------------------------+