Algorithm-Diff-Apply
view release on metacpan or search on metacpan
lib/Algorithm/Diff/Apply.pod view on Meta::CPAN
The tag names are whatever you labelled the diff sequences you passed
to C<apply_diffs()>. By definition, a conflict block contains a subset
of at least two separate diffs.
Each of the C<$hunk_X_X> scalars in the arguments above is a hash
reference with the following structure:
{
"start" => N,
"changes" => [[OP1, DATA1], ..., [OPn, DATAn]],
}
Where "start" is a line number in the I<target> array, indicating
where this hunk is intended to be applied, and "changes" contains the
changes to apply.
Optimiser callbacks should return a I<permuted copy> of what they were
passed. Empty diffs will be discarded automatically. If only one diff
remains after processing, the conflict will have been optimised away
completely.
( run in 0.844 second using v1.01-cache-2.11-cpan-140bd7fdf52 )