41

Given a data structure (e.g. a hash of hashes), what's the clean/recommended way to make a deep copy for immediate use? Assume reasonable cases, where the data's not particularly large, no complicated cycles exist, and readability/maintainability/etc. are more important than speed at all costs.

I know that I can use Storable, Clone, Clone::More, Clone::Fast, Data::Dumper, etc. What's the current best practice?

JasonMArcher
  • 14,195
  • 22
  • 56
  • 52
Anirvan
  • 6,214
  • 5
  • 39
  • 53
  • Is [tag:deep-copy] really irrelevant, @JasonMArcher? The summary talks about C and C++, but shallow and deep copy are language-agnostic concepts. By a clone, shallow copy is usually meant (Java, C#, …), this question is asking for a deep copy. – Palec Jul 08 '15 at 09:34
  • Our tags don't need to git into minutiae. These are all kinds of cloning operations. Currently we have [clone], [cloning], [copy], [deepclone], [deep-clone], [deep]+[clone], [deep]+[copy] and [deep-copy]. – JasonMArcher Jul 08 '15 at 15:47

5 Answers5

19

Clone is much faster than Storable::dclone, but the latter supports more data types.

Clone::Fast and Clone::More are pretty much equivalent if memory serves me right, but less feature complete than even Clone, and Scalar::Util::Clone supports even less but IIRC is the fastest of them all for some structures.

With respect to readability these should all work the same, they are virtually interchangeable.

If you have no specific performance needs I would just use Storable's dclone.

I wouldn't use Data::Dumper for this simply because it's so cumbersome and roundabout. It's probably going to be very slow too.

For what it's worth, if you ever want customizable cloning then Data::Visitor provides hooking capabilities and fairly feature complete deep cloning is the default behavior.

Tejus Prasad
  • 6,322
  • 7
  • 47
  • 75
16

My impression is that Storable::dclone() is somewhat canonical.

chaos
  • 122,029
  • 33
  • 303
  • 309
7

Clone is probably what you want for that. At least, that's what all the code I've seen uses.

Dan
  • 61,568
  • 9
  • 61
  • 78
0

Try to use fclone from Panda::Lib which seems the fastest one (written in XS)

Ivan Baidakou
  • 713
  • 9
  • 14
-1

Quick and dirty hack if you're already dealing with JSONs and using the JSON module in your code: convert the structure to a JSON and then convert the JSON back to a structure:

use JSON;

my %hash = (
    obj => {},
    arr => []
);

my $hash_ref_to_hash_copy = from_json(to_json(\%hash));

The only negative possibly being having to deal with a hash reference instead of a pure hash, but still, this has come in handy a few times for me.

kos
  • 510
  • 3
  • 18
  • 1
    The major limiting factor for JSON serialization is that it can't handle blessed references (or the class has to handle serialization in some way). If blessed references aren't part of the data, this might be fine. – brian d foy Dec 01 '21 at 23:43