Heh, wow. I guess simplicity is bliss sometimes. I took the liberty of using your benchmarking program, and added my function to compare to faq. The function i had come up with and was using was 
sub maptest {
    my ($low, $high) = @_;
    my $i=0;

    return 0 if @$low != @$high;
    map{return 0 if $_ ne $low->[$i++]}@$high;
    return 1;
}
__END__

with 
my @first = ((1..200), qw(a b c d e f)) ;
my @second= ((1..200), qw(b a c d e f)) ;

Benchmark: timing 20000 iterations of faq, map...
       faq:  8 wallclock secs ( 8.44 usr +  0.00 sys =  8.44 CPU)
       map: 10 wallclock secs ( 9.64 usr +  0.00 sys =  9.64 CPU)

[download]
Needless to say they were nearly identical for a difference at the start of the array.
Thanks for all the help!

In reply to Re: Re: (Efficiently) comparing arrays by cyberconte
in thread comparing arrays by cyberconte

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.