Implementing a Type Field copy with Reflection?

BlitzMax Forums/BlitzMax Programming/Implementing a Type Field copy with Reflection?


Copy of memory does not change the reference count -> zack and bang if the original object ever goes out of scope


Why should anything go bang? What does reference count have to do with anything? Why would you want to affect the reference count when creating a completely new object? Wouldn't that just stop the old object from ever being deleted? Why should an object going out of scope have any effect on the content of data you copied from it and is now residing in a completely different object?