The OpenEdge Hive

for a GUI-window to modify the settings described here:

   run prolint/core/lintcfg.w("")                               

Directory prolint/settings shows an example of how custom profiles can be used.

Each profile represents a subdirectory in prolint/settings.

Such a subdirectory may contain configuration files describing the behavior of Prolint.

The name of the custom profile is passed to Prolint as an input parameter. For example:

  RUN prolint/core/prolint.p (sourcefile, ttemptablehandle, "relaxed", true).

tells prolint to look for configuration files in directory prolint/settings/relaxed.

The configuration files in this directory may tell prolint to skip all rules with severity<6, for example.

If the parameter is blank or points to a non-existing directory, prolint will
use directory prolint/settings instead because this contains the default settings.

Profiles can be attractive when prolint is called from other ADE-tools to specify the
context where prolint is called from.

For example, Roundtable might run prolint.p(.., .., "rtb check-in",..)
during its pre-validation on check-in.

The Application compiler might run prolint.p(.., .., "application compiler",..)
which might tell prolint to write results to a logfile instead of using the results window.

Note: directories are searched in PROPATH.

files in prolint/settings:

file exteditor.cfg

file exteditor.cfg specifies how a source file can be opened in an external editor, like for example Ed4Win or UltraEdit etc.


exteditor.cfg contains just two lines:

1. commandline
2. parameters

These two lines are passed to the operating system. Each of these lines may contain &1 and &2, which are substituted by
filename and linenumber respectively, using the Progress SUBSTITUTE function.

example (for UltraEdit-32) :

"C:\Program Files\UltraEdit\UEDIT32.EXE"
"&1/&2"

(in this example the double quotes are used for supporting long filenames.)

file dbaliases.d

If your program requires database aliases to exist before it will compile, then you must use this file to tell Prolint about your database aliases before that program can be parsed.
The file may contain several lines, each line contains two fields: aliasname and databasename. Example:

"demo" "sports2000"
"archive" "sports2001"

In this example, "demo" is an alias for database "sports2000" and "archive" is an alias for database "sports2001".

files you may find in a profile subdirectory:

See profiles