Dan Kegel <[email protected]> writes: > However, once in a while, a programmer will call delete when he > should have called delete[], and a bunch of destructors won't > get called. To detect this programming error, let's split > the vector new and delete functions off from their scalar twins, > and add values for the heap function flags so we can inform > valgrind what kind of blocks are being wrangled. > > This means picking two flag bits that Microsoft doesn't use; > there seem to be enough to go around.
If you mean inventing new flags to HeapAlloc and friends, then no, you can't do that. -- Alexandre Julliard [email protected]
