One of the big things we just released in 3.0 is the new Xdiff. We call it "cross diff" because it can locate code that has been moved, and we used to draw it on paper with "crossing lines".
Ok, what is all of this about and why is it so good? Let's go.
Let's start with a piece of code like the following:
Then we move a piece of code a little bit down:
And we slightly modify the moved code as you can see here:
Let's see what Plastic Xdiff can do:
It is able to identify the code as "moved" even when it has been modified. And you can click on the "subdiff" to actually run an independent diff on the moved fragment as you can see below.
Cool, isn't it?
We can do this with any programming language since the algorithm is not based on parsing but in plain text move detection.
Check the following screencast to see it in action.
Don't forget to check the next step too: Xmerge!
news ( 120 ) mono ( 30 ) merging ( 23 ) integrations ( 22 ) distributed ( 20 ) best practices ( 18 ) branching ( 14 ) semanticmerge ( 14 ) git ( 12 ) scm ( 11 ) c# ( 9 ) fun ( 9 ) testing ( 9 ) performance ( 8 ) solaris ( 7 ) branch explorer ( 6 ) configuration ( 6 ) visual studio ( 6 ) differences ( 5 ) migration ( 5 ) Agile ( 4 ) Scrum ( 4 ) backend ( 4 ) delphi ( 2 ) unity ( 2 ) eclipse ( 1 )