in reply to Re^7: Executing functions from another process
in thread Executing functions from another process

The problem happens on the last line which errors out with Modification of a read-only value. Why is this the case?

Because the combination of the dump + eval equates to:

my @newD = ("one", "two", \"two");

[download]

Which means that $newD[ 2 ] is assigned a reference to the string literal "two"; and when you indirect through that reference, you are trying to modify that string literal.

With the other two elements of the array, new variables are created which are initialised to read-write copies of the string literals.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

Replies are listed 'Best First'.
Re^9: Executing functions from another process
by gri6507 (Deacon) on Jan 24, 2014 at 15:46 UTC
    So it sounds like dump+eval does not create a true copy of the data structure. What alternate methods are there to create a true clone of a structure so that even the referenced values could be writable?
[reply]
      So it sounds like dump+eval does not create a true copy of the data structure.

      None that I am aware of will retain knowledge that one scalar in the structure is a reference to another scalar in that same structure.

      Ie. If you have this structure (which is different to what you showed, but may be what you intended):

      $a = 'one'; 
$b = 'two'; 
@d = ( $a, $b, \$b );;

      [download]

      Then neither Storable:

      use Storable qw[ freeze thaw ];;

$x = freeze \@d;;
$y = thaw $x;;

pp $y;;
["one", "two", \"two"]

${ $y->[2] } = 'three';;

pp $y;;
["one", "two", \"three"]

      [download]

      Nor Clone successfully capture that scalar reference relationship:

      use Clone qw[ clone ];;

$x = clone \@d;;

pp $x;;
["one", "two", \"two"]

${ $x->[2] } = 'three';;

pp $x;;
["one", "two", \"three"]

      [download]

      You could say that was a bug -- and I'd probably agree with you -- but it is a long standing one that it would appear that no one has till now seen as a problem. Which is another way of saying it is unlikely to be fixed -- or even accepted as a bug -- any time soon.

      With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority".
      In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]
[d/l]
[select]

        I think that Sereal might retain aliases properly. The spec at least has a type for a proper alias, and I think I remember hearing in a talk about Sereal that it does retain that. Also, Data::Dump::Stream, by demerphq might also properly retain aliases.

[reply]

In Section Seekers of Perl Wisdom