I just found out that WinDiff has a capability to store comments made to a diff to their own file that can be imported by someone else:
============
==============================
File:.\so-test.cpp : .\so-test2.cpp, Total comments:1
==============================
Comment #1, L22 of right file<21>
Reviewer comment:
Why not just initialize the variable to 1?
Source line:
np += 1; // useless line for code review test
----------------------------------------------
============
This is a model that BC might use to permit some simple sharing of code review comments. WinDiffs work, but they are pretty rudimentary (for example, there's no mechanism to delete or edit a comment).
Another area where WinDiff's implementation falls short is that it would be nice if the comment file could be opened directly and have the tool automatically open the corresponding diff based on the "File:" information int he header. To be useful for code review, BC and the header information in the code review comments files would need to be able to support version control systems and/or patch files natively.
Anyway, it's an idea that might be a starting point for code review support.
============
==============================
File:.\so-test.cpp : .\so-test2.cpp, Total comments:1
==============================
Comment #1, L22 of right file<21>
Reviewer comment:
Why not just initialize the variable to 1?
Source line:
np += 1; // useless line for code review test
----------------------------------------------
============
This is a model that BC might use to permit some simple sharing of code review comments. WinDiffs work, but they are pretty rudimentary (for example, there's no mechanism to delete or edit a comment).
Another area where WinDiff's implementation falls short is that it would be nice if the comment file could be opened directly and have the tool automatically open the corresponding diff based on the "File:" information int he header. To be useful for code review, BC and the header information in the code review comments files would need to be able to support version control systems and/or patch files natively.
Anyway, it's an idea that might be a starting point for code review support.
Comment