Algorithm-Merge

 view release on metacpan or  search on metacpan

Merge.pm  view on Meta::CPAN

This is called if all three sequences have different elements at the 
current position.  The three arguments are the current positions within 
each sequence.

=back 4

=head1 BUGS

Most assuredly there are bugs.  If a pattern similar to the above 
example does not work, send it to <jsmith@cpan.org> or report it on 
<http://rt.cpan.org/>, the CPAN bug tracker.

L<Algorithm::Diff|Algorithm::Diff>'s implementation of 
C<traverse_sequences> may not be symmetric with respect to the input 
sequences if the second and third sequence are of different lengths.  
Because of this, C<traverse_sequences3> will calculate the diffs of 
the second and third sequences as passed and swapped.  If the differences 
are not the same, it will issue an `Algorithm::Diff::diff is not symmetric 
for second and third sequences...' warning.  It will try to handle 
this, but there may be some cases where it can't.

README  view on Meta::CPAN

        elements.

    CONFLICT
        This is called if all three sequences have different elements at the
        current position. The three arguments are the current positions
        within each sequence.

BUGS
    Most assuredly there are bugs. If a pattern similar to the above example
    does not work, send it to <jsmith@cpan.org> or report it on
    <http://rt.cpan.org/>, the CPAN bug tracker.

    Algorithm::Diff's implementation of "traverse_sequences" may not be
    symmetric with respect to the input sequences if the second and third
    sequence are of different lengths. Because of this,
    "traverse_sequences3" will calculate the diffs of the second and third
    sequences as passed and swapped. If the differences are not the same, it
    will issue an `Algorithm::Diff::diff is not symmetric for second and
    third sequences...' warning. It will try to handle this, but there may
    be some cases where it can't.



( run in 1.676 second using v1.01-cache-2.11-cpan-df04353d9ac )