Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!dciem!nrcaer!cognos!brianc
From: brianc@cognos.uucp (Brian Campbell)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Microsoft C 4.0 large models
Message-ID: <1245@cognos.UUCP>
Date: Wed, 12-Aug-87 13:11:49 EDT
Article-I.D.: cognos.1245
Posted: Wed Aug 12 13:11:49 1987
Date-Received: Sat, 15-Aug-87 06:42:38 EDT
References: <1112@lznv.ATT.COM> <399@aucs.UUCP> <3225@cucca.columbia.edu> <880@bdmrrr.bdm.com>
Reply-To: brianc@cognos.UUCP (Brian Campbell)
Organization: Cognos Incorporated, Ottawa, Canada
Lines: 18

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.  One result you won't
! get is the compiler message "Oh gosh, you really shouldn't use malloc in
! a large model".  Not to start an argument with anyone, but it is for
! reasons such as these that I love 68000-family architectures.  Good luck.

     I beg  to differ. The malloc/free  routines in the large  model the
*SAME*  as  the  _fmalloc/_free  routines.   The  only  problems  I  can
understand complaints about are not being able to allocate more than 64k
cleanly, and problems in using mixed models.
     P.S.  I prefer the 68000 family too.
-- 
Brian Campbell          uucp: decvax!utzoo!dciem!nrcaer!cognos!brianc
Cognos Incorporated     mail: 3755 Riverside Drive, Ottawa, Ontario, K1G 3N3
(613) 738-1440          fido: sysop@163/8