implementing objects will still be able to keep a regular public clone() method that may do their own selective deep cloning. This allows explicit demarcation between the normal 'user' facing clone() and the two step cloning process used by Cloner. Specifically, this will let Spatial continue to have a clone() method that operates as it does today... with its new guts essentially calling a properly configured Cloner.cleanup_build_scripts
parent
68425480cb
commit
10947e8b50
Loading…
Reference in new issue