Tim Peters email@example.com writes:
Sure, but that's only an issue if you are allocating resources in one runtime lib and deallocating in another AFAIK. There's nothing beyond memory allocation going on here, and the type object in question has a custom deallocator which goes to the same runtime that allocated it.
See my later msg -- returning memory to a heap it wasn't obtained from is fatal enough.
I think that's exactly what I said.
The object memory itself is in question here, not memory allocated *by* the object.
I think that's also exactly what I thought.