Yeah but there is the little but massive problems that objects can hold references to other objects! And by memcopying them instead of assigning them, you totally break the GC (or in other terms: you would create weak references and therefor let the cloned object hold potential NULL references if the original object goes out of scope)
So everything you clone must be cloned by using this function hierarchically on all object references -> would need to be implemented in the bbObject class itself
Noel did that a few versions ago.
The GC dies with similar messages you get when you try to do callbacks to external libraries that are out of blitz for longer than the minimal timeslice of GC check.
Most likely because the clone can block the periodical GC checks
So everything you clone must be cloned by using this function hierarchically on all object references -> would need to be implemented in the bbObject class itself
Noel did that a few versions ago.
The GC dies with similar messages you get when you try to do callbacks to external libraries that are out of blitz for longer than the minimal timeslice of GC check.
Most likely because the clone can block the periodical GC checks