Within BackupPC::Storage::Text, there is some code like
if ( exists($newConf->{$var}) ) {
my $d = Data::Dumper->new([$newConf->{$var}], [*va
+lue]);
$d->Indent(1);
$d->Terse(1);
$d->Sortkeys(1);
my $value = $d->Dump;
$value =~ s/(.*)\n/$1;\n/s;
$contents .= "\$Conf{$var} = " . $value;
$done->{$var} = 1;
}
This works fine for older versions of Data::Dumper, but fails for newer ones.
Replacing the line referring Data::Dumper with
my $d = Data::Dumper->new([$newConf->{$var}], \[*value]);
solves the issue, but I'm not sure I understand why exactly.
In particular, I would like to understand if it's BackupPC doing something that it shouldn't when using [*value], or if it is Data::Dumper that broke the rules by doing things differently now.
(Later edit) Looks like the correct question is like
should [*value] be a list or an arrayref?
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|