Use of uninitialized value in concatenation (.) or string at ./compare
+.pl line 25.
[download]

#!/usr/bin/perl -w

use Array::Compare;
use strict;


my $file1  = "/var/tmp/db.bind1";
my $file2  = "/var/tmp/db.bind2";
my $out    = "/var/tmp/compare_out";

open(FILE1, "$file1")  || die "Can't open $file1 to read\nReason: $!\n
+";
my @file1 = <FILE1>;
close(FILE1);

open(FILE2, "$file2")  || die "Can't open $file2 to read\nReason: $!\n
+";
my @file2 = <FILE2>;
close(FILE2);

open(OUT, ">$out")     || die "Cant create $out\nReason: $!\n";

my $comp = Array::Compare->new(DefFull => 1);

print OUT "line $_ differs. File 1: $file1[ $_ ] != File 2: $file2[ $_
+ ]\n"

    for $comp->full_compare(\@file1,\@file2);

#$comp->compare(\@file1, \@file2);

#print OUT $comp->full_compare(\@file1,\@file2);

close(OUT);
exit;
[download]

That simply means that the value in one of the arrays is the null string ('') eg, a blank line.

You can either trun of that particular warning with

no warnings 'uninitialized';
[download]

See perllexwarn for details.

Or you could modify the print statement to provide better diagnostics.

print OUT "line $_ differs. File 1: ",
    $file1[ $_ ] || '[blank]',
    " != File 2: ",
    $file2[ $_ ] || '[blank]',
    "\n"
    for $comp->full_compare(\@file1,\@file2);
[download]

---

Examine what is said, not who speaks.

"Efficiency is intelligent laziness." -David Dunham
"When I'm working on a problem, I never think about beauty. I think only how to solve the problem. But when I have finished, if the solution is not beautiful, I know it is wrong." -Richard Buckminster Fuller
If I understand your problem, I can solve it! Of course, the same can be said for you.

Thanks for the help there that actually worked for me, but I think I am going to also give Merlyn's method a shot. Maybe the best solution is more simplistic, LOL. Thanks again, -Sunadmn