Prolint


findstate-tt reports on FIND when unique index is used

Have following code:

DEFINE TEMP-TABLE ttAccount NO-UNDO
FIELD Id AS CHARACTER
INDEX i1 IS UNIQUE PRIMARY Id.

FIND ttAccount WHERE ttAccount.Id = "xyz" NO-ERROR.

The findstate-tt rule reports this and suggests a "FIRST/LAST" or "IF AMBIGUOUS" but the index is UNIQUE.

Is this expected behaviour?


tablename rule reports unqualified fields in FIELDS()

Code such as
FOR EACH Customer FIELDS(Id Name) NO-LOCK:

reports that the "Id" "Name" should be qualified with table name.

Is this intentional behaviour or should I log an issue?


Prolint results screen - Open sourcefile in Editor

On the 'Prolint results screen' there is a button labelled 'Open sourcefile in Editor'.

I run Prolint from PRO*Tools and use the 'Lint Active AB' button.

When I click the 'Open sourcefile in Editor' button nothing happens. Is something supposed to happen?


new rule help

Hi, all.

We just recently acquired proparse and prolint. I am looking into writing some new rules. I have not finished reading all the doc available at joanju.com, or fully absorbed the syntax tree. But I was hoping you folks could help me short-circuit the process a little. I am wondering if any of you
a) have written these rules
b) have suggested starting points to help me locate how to find them in the tree
c) be able to tell me "No can do"

on several rules I am looking at implementing.
1) No nested includes


Can you dynamically change the propath with proLint?

Just like you can do with Progress. I work on lots of projects and this ability would be great.


Engine Overheating - How can I turn this off?

This is a time-consuming process to have to enter the 3 char code every couple of minutes. Can this be turned off or bypassed?

Can prolint be run as a batch process?


Syndicate content