Prolint is a tool for automated source code review of Progress 4GL code. It reads one or more sourcefiles and examines it for bad programming practice
When you are interested Prolint, you are encouraged to subscribe to this group where you find the on-line tools to collaborate and discuss Prolint. There is a discussion forum, you can submit issues (for bugs and enhancement requests), you can modify the on-line documentation. So subscribe, and then don't forget to go to your subscription details to enable the e-mail notification!
An outputhandler must be located in directory prolint/outputhandlers, and has to be listed in
Columns in file prolint/outputhandlers/choices.d:
|"GUI"||this outputhandler will only run in a GUI session|
|"TTY"||this outputhandler will only run in a ChUI session|
|"*"||this outputhandler will run in any window-mode|
|""||this outputhandler will only run in batch-mode|
Each outputhandler is loaded persistently by prolint.p, but prolint will never delete the procedure. The outputhandler has to delete itself when ready,
usually from within the event-procedure for event "Prolint_FinalizeResults".
The outputhandler subscribes to, and responds to (some) of the following published events:
PROCEDURE Prolint_InitializeResults : DEFINE INPUT PARAMETER pClearOutput AS LOGICAL NO-UNDO. END PROCEDURE.
Event Prolint_InitializeResults is published when prolint.p starts.
All tests are performed by "rules", these are programs in directory prolint/rules.
This is where the actual knowledge about Progress source code review is implemented.
Unless you are running Progress version 8 or TTY mode, you will need to extract adecomm.pl.
This is because the codepreview window contains an editor, which uses the same syntax-coloring editor as the Progress Appbuilder, and adecomm.pl contains the includefiles that makes this possible.
Open a command shell and change directory to your DLC directory. In the following example I will assume this is directory "c:\Program Files\Progress" :