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!
Subversion (source control)
Tue, 2006-09-19 21:17 — jurjenThe source code for Prolint is managed in a Subversion repository, here at the OpenEdge Hive.
You can also find a Subversion repository at Sourceforge.net, but that one is outdated.
View the repository in your web browser:
http://websvn.oehive.org/listing.php?repname=prolint
or if you prefer to use a subversion client (like svn.exe or TortoiseSvn) then you can export the trunk from svn://oehive.org/prolint/trunk/prolint
Prolint Discussion Forum
Mon, 2006-09-18 23:26 — jurjenVisit the Prolint discussion forum
(but if you have an idea for a new rule, please use the Issue Tracker and use the combo-boxes to specify "component=rule" and "category=feature request")
When you are not subsrcribed to the Prolint group, you will not be able to post anything in the Forum.
Subscribing only takes a second or less, and you can unsibscribe whenever you want.
input blocking statement during database transaction
Mon, 2006-09-18 22:59 — jurjeninput blocking statement during database transaction
- Login to post comments
widget X created but never deleted
Mon, 2006-09-18 22:58 — jurjenwidget X created but never deleted
- Login to post comments
memory in memptr X is never released with set-size(X)=0
Mon, 2006-09-18 22:58 — jurjenmemory in memptr X is never released with set-size(X)=0
- Login to post comments
type mismatch in parameter X when calling user-defined function
Mon, 2006-09-18 22:57 — jurjentype mismatch in parameter X when calling user-defined function Y
- Login to post comments
insufficient index information specified in WHERE-clause
Mon, 2006-09-18 22:56 — jurjeninsufficient index information specified in WHERE-clause
- Login to post comments
abbreviation of database field names is not allowed
Mon, 2006-09-18 22:56 — jurjenabbreviation of database field names is not allowed
- Login to post comments
enforce the order of keywords
Mon, 2006-09-18 22:55 — jurjenenforce the order of keywords. For example "FOR EACH tablename NO-LOCK WHERE ": NO-LOCK should appear immediately after tablename, not after the WHERE-clause.
- Login to post comments
check for capitalizing of keywords
Mon, 2006-09-18 22:54 — jurjenHas to be customizable: some want only lowercase, others want only uppercase keywords.
- Login to post comments
no DEFINE statements between executable statements
Mon, 2006-09-18 22:53 — jurjenDEFINE VARIABLE statements should not be used after any executable statements. In other words, enforce that DEFINEs only appear in the definition section before any actual logic.
- Login to post comments
check for matching parameters in RUN statements
Mon, 2006-09-18 22:52 — jurjencheck for matching parameters in RUN statements. Will probably need two rules for this: one for internal procedures and a second, much more complicated rule for external procedures
- Login to post comments
enforce header comment
Mon, 2006-09-18 22:51 — jurjenenforce that each program (compilation unit) starts with a particular boilerplate comment
- Login to post comments
enforce that certain includefiles are used
Mon, 2006-09-18 22:50 — jurjenenforce that certain includefiles are used. This rule would have to be highly customizable. The idea is: a company rule asserts that a particular includefile is included in compilation unit. Which compilation units? Which includefile(s)?
- Login to post comments
check if each opened stream is closed
Mon, 2006-09-18 22:48 — jurjencheck if each opened stream is closed
- Login to post comments
