Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!unixhub!ditka!comeau
From: comeau@ditka.Chicago.COM (Greg Comeau)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: free() in SAS C
Message-ID: <38575@ditka.Chicago.COM>
Date: 10 May 91 14:00:25 GMT
References: <1991May02.143148.22732@edb.tih.no> <chopps.0579@ro-chp.UUCP> <1991May07.164814.2538@medar.com>
Sender: comeau@ditka.Chicago.COM (Greg Comeau)
Reply-To: comeau@csanta.attmail.com (Greg Comeau)
Organization: Comeau Computing
Lines: 26

In article <1991May07.164814.2538@medar.com> jseymour@medar.com (James Seymour) writes:
>Can anyone else comment further on this?  Did I miss something?  Is there
>*really* an ANSI-imposed 64k malloc limit?  This hardly seems reasonable
>to me.  Heck, if I wanted 64k limits, I coulda bought a MeSsy-DOS box
>(shudder).

There is *NO* such ANSI limit.  What ANSI tells us is:

void *malloc(size_t size)

"The ``malloc'' function allocates space for an object whose size is
specified by ``size'' and whose value is indeterminate."

That says it all.  If you want more ammo, investigating size_t:
"``size_t'' is the unsigned integral type of the result of the 
``sizeof'' operator". (BTW, size_t is also "the type of integer
required to hold the maximum size of an array").

The bottom line?  It's implementation dependent.

- Greg
-- 
	 Comeau Computing, 91-34 120th Street, Richmond Hill, NY, 11418
                          Producers of Comeau C++ 2.1
          Here:attmail.com!csanta!comeau / BIX:comeau / CIS:72331,3421
                     Voice:718-945-0009 / Fax:718-441-2310