Xref: utzoo comp.sys.ibm.pc:34283 comp.lang.c:21532
Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!uwvax!puff!rt1.cs.wisc.edu!schaut
From: schaut@rt1.cs.wisc.edu (Richard Schaut)
Newsgroups: comp.sys.ibm.pc,comp.lang.c
Subject: Re: Microsoft C - Heap space question
Keywords: heap microsoft-c
Message-ID: <2930@puff.cs.wisc.edu>
Date: 7 Sep 89 02:43:18 GMT
References: <3631@cbnewsh.ATT.COM> <4143@csd4.csd.uwm.edu>
Sender: news@puff.cs.wisc.edu
Reply-To: schaut@rt1.cs.wisc.edu (Richard Schaut)
Distribution: usa
Organization: U of Wisconsin CS Dept
Lines: 14

In article <4143@csd4.csd.uwm.edu> chad@csd4.csd.uwm.edu (D. Chadwick Gibbons) writes:
|[yuck!]
|	MicroSoft, and most other DOS compilers for that matter, provide a
|function to allocate heap space using far pointers.  This way, if the heap
|requirements exceed 64K, it will grab another chunk of system memory.  The
|function is declared--I believe--as "char far *farmalloc(size_t);"  
				      ^^^^
If MS C is ANSI compatible, then the function would be declared as
"void far *farmalloc(size size_t);" thereby removing the need to cast
the return value to a pointer to a specific kind of object.
--
Rick

"Any questions?  Any answers?  Anyone like a mint?" -- source unknown