To: domanows@niktow.canisius.edu (Matthew Domanowski)
Subject: Re: Dynamic array allocation problem in Borland C++
Newsgroups: comp.lang.c++,comp.std.c++
Organization: JBA Software Products, Studley, England.

In article <6208@niktow.canisius.edu> you wrote
:
  [stuff deleted]

: large arrays.  I have 8 megs of extended memory.  How can I calloc
: memory space in extended memory and avoid using the standard 640 K?
: If anyone has any suggestions, please e-mail me at domanows@canisius.edu
:    Thanks in advance...

There's an excellent discussion of memory allocation in text file TI738.ASC
in bchelp10.zip - I can't remember which ftp site I got it from - try archie
to find it.

This reply is also being mailed to the original poster.

--
       __    :   Mark Phillips           :   email = gbjbamrp@jba.co.uk
     JBA \   :   JBA Software Products   :   Tel   = 0527 854525
      \__/   :   Studley, Warwickshire   :   Fax   = 0527 857146
--
       __    :   Mark Phillips           :   email = gbjbamrp@jba.co.uk
     JBA \   :   JBA Software Products   :   Tel   = 0527 854525
      \__/   :   Studley, Warwickshire   :   Fax   = 0527 857146

I am currently working on a program to store graphics in .RAW format
in an array of records in Turbo C++.  Turbo C++ would only allow an
array of size 100.  To get around this problem I calloc'ed the arrays
at run time (not in linked list).  Now I am crashing my computer with
large arrays.  I have 8 megs of extended memory.  How can I calloc
memory space in extended memory and avoid using the standard 640 K?
If anyone has any suggestions, please e-mail me at domanows@canisius.edu
   Thanks in advance...
 Matt Domanowski
 domanows@canisius.edu