Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!samsung!spool.mu.edu!uunet!pilchuck!dataio!fnx!nazgul!bright
From: bright@nazgul.UUCP (Walter Bright)
Newsgroups: comp.lang.c++
Subject: Re: Can Borland C++ malloc > 640K?
Message-ID: <316@nazgul.UUCP>
Date: 4 May 91 18:08:08 GMT
References: <sean.672670930@s.ms.uky.edu>
Reply-To: bright@nazgul.UUCP (Walter Bright)
Organization: Zortech, Seattle
Lines: 14

In article <sean.672670930@s.ms.uky.edu> sean@ms.uky.edu (Sean Casey) writes:
/I'm writing an application that needs to malloc about 1500K of memory
/for a large tree. Does anyone know any tricks to let the BC++ heap see
/extended memory?

For applications of this sort, you simply need a 32 bit compiler, that runs
with a 32 bit DOS Extender like Pharlap's. 32 bit compilers for MSDOS include:

Zortech C/C++
Watcom C
Metaware C

With a 32 bit compiler you needn't worry again about far pointers, huge
pointers, 64k segments or 640k barriers.