Thanks Michael for your msg about intelligent memory alloca, on
02 11-02-1994

What compiler are you using? There should be no reason why you
cannot malloc() massive amounts of memory under OS/2 (even if
there is not enough physical memory to back it up.)

It is more efficient to allocate very large buffers via
DosAllocMem() if you know you are going to use it all, such as in
your bitmap example. But for general purpose usage, you should
stick with malloc() (or new if your are in C++ world.) They are
not incredibly fast but are portable (and will be improved over
time if your compiler vendor is any good.) You can override new in
special cases where you have a class that is always a fixed size
and gets alloc'd/free'd extremely often.

If you do decide to suballocate your own heap, you can use the
OS/2 suballocation stuff which, once again, is not the fastest in
the world but is already there and debugged. If you do decide how
to do it, then you learn about how OS/2 handles sparse memory
objects and commits it as needed.

___
 X KWQ/2 1.2b X This tagline stolen by KWQ Mail/2.

--- Maximus/2 2.02