Re: Lint like report on old sources - how to let report 'point' to the new src lines?

On 25 Apr., 13:48, Ed Morton <mor...@xxxxxxxxxxxxxx> wrote:
On 4/25/2008 6:08 AM, Florian Kaufmann wrote:





The actual problem statement is a bit more complex. We have a report
file (excel ***) that contains the monthly report plus for each
issue a comment, whether it should be fixed or if we accept the flaw.
Additionally we have the daily report from the lint like tool -
however this report has no information which issues are to be solved
and which issues are accepted.

Now there are two use cases:

1) Say I want to solve issues in the code. I get the daily report. But
I'd liked to strip the issues from the daily report that are labeled
as accepted in the monthly report, so i only see the issues that I
actually have to solve.

2) At the start of the next month, somebody has to go through to big
work of getting the latest daily report and create from it the new
monthly report that also contains the information which issues are
accepted. He does it by looking up the accepted issues in the old
monthly report and label the corresponding issues in the new report as
accepted.

You see, it's all very inefficient, way too much manual work.

Export both reports to tab-separated text and post a small sample of each here
along with a field-by-field description of what you want to do and the expected
output given those 2 files.

I think the inherent problem is the "label the corresponding issues"
issue in conjunction with changing source code between the reports;
there is no apparent correlation, parts of the code may have been
deleted in the meantime, or changed, or new code added. So using
some diff tool to identify the changes and use the line numbers to
calculate/associate the correlation between old and new versions of
the files seems a necessity to do; but it's no easy job as the OP
already suspected. (Thus better to change the report/bug/fix process
in the first place.)

Janis


        Ed.
.

Quantcast