I am using Borland's latest C++ on DOS, and when I try to "new" storage it sometimes returns 0, even though I haven't used that much storage from the heap yet.
The case is that I "new" about 32kbytes in 8 calls to new, and then make a call to
new for another 40k. Suspiciously it looks like I either exceeded 64k and new
will only give me 64k of storage, or I need to use "far" pointers.
The code I wrote runs fine on the Sparc, and is supposed to be platform independant,
so I don't want to muck up the code with far, so I'm hoping there is some way to
tell the compiler to generate far pointers all the time. Here's an example: