Path: utzoo!censor!geac!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!samsung!uunet!brunix!ruby.vcu.edu!hleaves From: hleaves@ruby.vcu.edu (EAVES,HUGH) Newsgroups: comp.os.msdos.programmer Subject: Re: Desired: "limitless" heap manager reviews/recommendations Keywords: C virtual memory manager heap EMM expanded Message-ID: <61159@brunix.UUCP> Date: 10 Jan 91 16:06:43 GMT References: Sender: news@brunix.UUCP Reply-To: hleaves@ruby.vcu.edu Followup-To: comp.os.msdos.programmer Organization: Medical College of Virginia, Hired Hackers Lines: 29 News-Software: VAX/VMS VNEWS 1.3-4 In article , kerce@nu.cs.fsu.edu (Kingsley F. Kerce) writes... >Does anyone have opinion on a C heap manager that uses ex[pan/ten]ded >memory and/or fixed disk space? I would hope that such a package >would be as easy to use as the malloc() family. Additionally, it >would be nice if the manager worked with Turbo C 2.0. Finally, if >it's free, that's perfect. > >Thanks much, >-- >Kingsley Kerce kerce@nu.cs.fsu.edu It would be nice, but you're not going to find anything like that for a real mode compiler. Real mode pointers are all 16 or 20 bits, which already limits you to a maximum of 1 meg of memory. Even if you could use a larger pointer size, there is no virtual memory management in real mode. I guess you could rewrite your compiler to trap memory references to paged memory, and then, if necessary, reload it from disk. If you're really running applications that need a large amount of memory, you should consider switching to a protected mode compiler. Hugh ******************************************************************************* ** Hugh L. Eaves ** Internet: hleaves@ruby.vcu.edu ** ** Medical College of Virginia ** Bitnet: hleaves@vcuruby ** ** Department of Human Genetics ** Voice: (804) 371-8754 ** ***************** All non-incendiary communication welcome! *******************