The debugger has now been commented, top to bottom.
It was an interesting job, and well worth doing. Not only did I learn a lot, but something that others will be able to use has come out of it. In addition, I learned a lot about how to check a vastly re-commented, re-whitespaced source against the original. For those interested:
perltidy -syn -dsm -naws -dnl -sob -dac -ce -bar
perl -p -e 'next if /^[\+\-]\s*$/'You can now visually inspect the output, looking for dropped stitches. This works particularly well for catching pod blocks with missing =cuts, as the old code will show up as deleted from the output code.
It might be worthwhile to consider some code-comparison enhancements to perltidy; even with the command line given above, lines with their internal spacing changed will still show up as different.
WOW! (Score:2)
Thanks!
We all owe you some beers this summer. What's your favorite?
Re:WOW! (Score:1)
Whitespace changes (Score:2)
-bor-wwhen you run diff to avoid seeing whitespace changes?Re:Whitespace changes (Score:1)
I think the real problem is that it's not easy to parse perl and do a real semantic diff.