KC> That's what I'm talking about. There's no rules that say new() canno
KC> termination function if it fails to allocate the memory. One of the
KC> purposes of overloading new() is to provide virtual mem, which would
KC> disk access for goodness sake!
Ok.
The  original poster asked about a way to prevent an object from being
created based on reasons not related to memory management. Overloading
oeprator new() is the wrong solution for this.
Thomas
---
 þ MM 1.0 #0113 þ A judge is a lawyer who once knew a governor.
---------------