Path: utzoo!utgpu!attcan!uunet!husc6!uwvax!umn-d-ub!rutgers!ucsd!ucbvax!decwrl!sgi!wdl1!dinolt
From: dinolt@wdl1.UUCP (George W. Dinolt)
Newsgroups: comp.sys.atari.st
Subject: Re: malloc bugs (s.b. Malloc bugs)
Message-ID: <4120005@wdl1.UUCP>
Date: 16 Aug 88 00:48:12 GMT
References: <5919@batcomputer.tn.cornell.edu>
Lines: 18

/ wdl1:comp.sys.atari.st / braner@batcomputer.tn.cornell.edu (braner) /  1:12 pm  Aug 12, 1988 /
[]
M. Banner writes about Malloc:

   Use malloc() (lowercase m), the library function that came with your C
   compiler.  Assuming you got a decent compiler (Laser, Megamax, MWC, etc)
   (I don't know about Alcyon) that will keep you out of trouble.
   Make sure you use free() for what was malloc()ed, not Free().
   The only case where you need Malloc() (uppercase M, the GEMDOG function)
   is when you absolutely need to allocate more than 64K at once, since
   malloc() takes an unsigned int as its argument, and an int on the 68000
   is (or should be) 16 bits.  
...
In fact the MWC compiler has an lmalloc(lsize) which takes a long as an
argument, so in that compiler at least, there is no need to use Malloc.
Regards,
George Dinolt 
dinolt@ford-wdl1.arpa, ...!sun!wdl1!dinolt