Closed Weeena closed 8 years ago
Do you have a code sample to demonstrate this? The object has been destroyed, it is not useable.
EDIT: nevermind. I see what you mean. destroy() takes a const UserObject&. Hmm.
Ok, if you get latest a I think this is fixed.
After a UserObject is destroyed or destructed, e.g.
the object sould be empty (i.e. equal to
UserObject::nothing
). This is now not the case, e.g. the memberm_class
still refers to the destroyed object's class.