Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!mit-eddie!bloom-beacon!oberon!sdcrdcf!trwrb!cadovax!gryphon!greg
From: greg@gryphon.CTS.COM (Greg Laskin)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Microsoft C 4.0 large models
Message-ID: <1121@gryphon.CTS.COM>
Date: Tue, 4-Aug-87 19:45:05 EDT
Article-I.D.: gryphon.1121
Posted: Tue Aug  4 19:45:05 1987
Date-Received: Fri, 7-Aug-87 06:32:18 EDT
References: <1112@lznv.ATT.COM> <399@aucs.UUCP> <3225@cucca.columbia.edu> <880@bdmrrr.bdm.com>
Reply-To: greg@gryphon.CTS.COM (Greg Laskin)
Organization: Trailing Edge Technology, Redondo Beach, CA
Lines: 18
Summary: wrongness corrected

In article <880@bdmrrr.bdm.com> davis@bdmrrr.bdm.com (Arthur Davis x4675) writes:
>If you have moved your code to a large model, I hope you have changed
>your malloc calls to _fmalloc (and free to _ffree).  You can get some
>strange results using malloc in a far environment.  

malloc and free work just fine in large model.  _fmalloc and _ffree are
for hybid models.  For example, to allocate data referenced by a far
pointer in a SMALL model program, you have to use _fmalloc, but in a
LARGE model program, malloc works fine because you link the program to
the large model library.


-- 
Greg Laskin   
"When everybody's talking and nobody's listening, how can we decide?"
INTERNET:     greg@gryphon.CTS.COM
UUCP:         {hplabs!hp-sdd, sdcsvax, ihnp4}!crash!gryphon!greg
UUCP:         {philabs, scgvaxd}!cadovax!gryphon!greg