search

billyquith / ponder

C++ reflection library with Lua binding, and JSON and XML serialisation.
http://billyquith.github.io/ponder/
Other
647 stars 95 forks source link

After a UserObject is destroyed or destructed it should be empty #23

Closed Weeena closed 8 years ago

Weeena commented 8 years ago

After a UserObject is destroyed or destructed, e.g.

someClass.destroy(someObject);

the object sould be empty (i.e. equal to UserObject::nothing). This is now not the case, e.g. the member m_class still refers to the destroyed object's class.

billyquith commented 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.

billyquith commented 8 years ago

Ok, if you get latest a I think this is fixed.