[procedure: prolint/outputhandlers/logwin.w]
The Prolint Result window shows a browse widget containing all warnings from the most recent Prolint run.
When Prolint is working, the statusbar shows:
When Prolint is ready, the statusbar shows:
Window features:
(this feature works only if you have ED for Windows and Progress version 9).
You will probably want to edit the sourcefiles where Prolint found warnings.
This is very easy when the warnings are listed in the "Build"-window of ED for Windows instead of the Prolint Results window.
There is a relatively easy way to export the warnings from the Results window to ED's Build window, if you have
installed proed4w :
The advantage of this method, over just running Prolint from within ED for Windows, is that this
will use the filter and sorting from the Result window.
How it works:
ED starts proed4w.exe with the "-c prolint-logwin" parameter.
proed4w.exe makes a TCP/IP connection with proed4w.p and passes it the "-c prolint-logwin" parameter.
proed4w.p publishes a "Prolint_SendLogWin_Ed4Win" event.
The Results window receives the event and passes all selected warnings on to outputhandlers/ed4win.p
Outputhandler ed4win.p publishes lines to proed4w.p
Proed4w.p sends lines through TCP/IP back to proed4w.exe
proed4w.exe writes those same lines to stdout, where ED will read them.
More setup details: see page Integrating Prolint and ED for Windows
[Procedure: prolint/prolintdb/lintstats.p invoked by prolint/outputhandlers/logwin.w]
The Session Statistical Comparison window is divided into three sections. On the top is the session browse where you locate the 2 sessions you want to compare against each other. There are filters at the top for user id (compared with a 'begins' operator), start date (greater than or equal operator), and session name (matches operator, the program adds two * wildcards for you). When they are set, choose filter and the matching sessions appear in the browse below. Note that a blank date means exclude the date field from the filter.
When you locate a session in which you are interested, you will make it either the 'Base' or the 'Curr'[ent] session. Typically the 'Base' is the older Baseline session that you want to use to show improvement. The newer session is the one you would typically want to select as Curr[ent].
As you select a Base or a Current session, the basic session information appears in the lower right section of the window so you can be sure which sessions you are comparing against each other. When you have both a Base and a Current, you would select Analyze. This populates the comparison browse in the lower left. This browse displays one row per compilation unit and rule, showing how many alerts were found in each session for that rule and compilation unit. To help you determine impact, the rule severity is shown, as well as the difference between the two sessions.
Assuming you are using the old version as the Base and the newer version of the program as the Current, a positive number in the "diff" column indicates that you have added new problems to that compilation unit. A negative number indicates that some have been cleaned up.
The lower (session comparison) browse can be filtered by Compilation Unit ("Prog" using a Matches operator with the wildcards added for you), and rule using a Begins operator. You fill in the values you wish to use as a filter, then select the lower filter button. (The upper filter button applies to the session browse at the top).
Once you have completed your analysis, click Cancel to close the window and return to the results window.