in reply to Re: Clone - clone Vs Storable - dclone
in thread Clone - clone Vs Storable - dclone
I think that at the heart here we have a core vs non-core issue.
UnderMine
Core modules should be upto date with the latest things that have happened
Core modules that cause seg faults tend to get fixed fast where as when a module such as Clone causes one it is not considered such an issue.
andperl -e 'use Clone qw(clone); $a = \$b; undef $a; $c = clone $a;'
Cause Seg faultsperl -e 'use Clone qw(clone); $a ={}; undef $a; $c = clone $a;'
but
andperl -e 'use Clone qw(clone); undef $a; $c = clone $a;'
does not cause this issue.perl -e 'use Clone qw(clone); $a =""; undef $a; $c = clone $a;'
Core supports Uni-code but it takes time for modules to catch up. It appears that Clone does not support Unicode structures correctly :-
as oposed toperl -MClone=clone -le '%a=(chr 256 =>1);$c=clone \%a; print ord fore +ach keys %$c' 196
Hope this clears up a few thingsperl -MStorable=dclone -le '%a=(chr 256 =>1);$c=dclone \%a; print ord + foreach keys %$c' 256
UnderMine
In Section
Seekers of Perl Wisdom