|There's more than one way to do things|
Clone - clone Vs Storable - dcloneby UnderMine (Friar)
|on Mar 24, 2003 at 13:24 UTC||Need Help??|
UnderMine has asked for the
wisdom of the Perl Monks concerning the following question:
I would like some advice as to whether anyone has experience of Clone's clone Vs Storable's dclone.
A module that I have recently been using Hash::Merge uses clone in order to do a level at a time comparison of the keys used in hashs. But this has shown up a few Bugs in the underlying module Clone (including causing a Seg-fault).
I have posted a fix for Hash::Merge that by-passes the Seg fault issue in clone but does not address the Uni-code support issue.
My question is should Hash::Merge be using clone or dclone. dclone does deep cloning but is part of core perl but is slower than clone in the context of Hash::Merge which only requires single depth transversal cloning.
All thoughts welcome