In a message dated 05-1695, Peter Fitzsimmons said to Nick Knight:

 NK> break our systems.  With an RTL-in-a-DLL, memory
 NK> allocation/handling is performed through a single
 NK> source heap,

>Personally,  this is rarely an issue for me,  since I consider it a design
>flaw to have something allocated/opened in one place to be freed/closed in
>another.

I don't share your concerns, personally, but I do understand them.  OTOH,
after thinking about it, most of our objects are created and destroyed by
the same process.  Perhaps it's the *sharing* of memory pointers between
programs.  Passing a pointer to a "new" object to another process
and back. Using malloc/new, I'm sure OS/2's memory protection scheme would
complain without taking extra steps to insure the heap is shareable memory.
 If this is even possible (to give out tiny pieces of a shared memory area)
...

I'm just speculating, too lazy to walk down the hall and get a more
detailed explaination :).

Nick

.. One man's Windows are another man's walls. -- MR/2 2.24 #0

--- InterPCB 1.50