Prolint


Prolint 70 is now available

Prolint 70 is now available! Note: It requires ProParse 3.1a released in April 2007.

This release is all about the Prolint database. It provides a session identifier with any lint session, like Progress Profiler’s Profiler ID, so that you can compare sessions over time. This allows you to see the improvement (or the opposite) over time as people work on the code.


Anthony showing Eclipse with ProRefactor Prolint

Anthony showing Eclipse with ProRefactor Prolint

Anthony Swindell enthusiastically showing the power of Eclipse with plugins like ProRefactor and Prolint.


Prolint/Eclipse

I've started work on a Prolint plug-in for Eclipse, but just written in Java, rather than ABL. Because it relies a lot on ProRefactor, I've just included my work so far in the ProRefactor SVN repository.

The Prolint/Eclipse page in the Prolint book is where you can find a bit more information and maybe a couple of pretty pictures. :)


Prolint/Eclipse Problems View

Prolint/Eclipse Problems View

Once Prolint problems have been found, problem markers are created in Eclipse. These markers can be sorted and filtered. Clicking on a marker in the Problems view opens an editor to the right line and highlights the problem code.


Prolint/Eclipse menu choices

Prolint/Eclipse menu choices

There are two simple menu items for Prolint: one to find problems, and the other to clear the problem markers. Any combination of files, folders, and projects can be selected for these.


Prolint/Eclipse

John has started some initial work on a Java/Eclipse variant of Prolint. This variant of Prolint has the advantage of easy access to ProRefactor's output - especially its symbol tables and scoping information.

Questions about getting the original Prolint into Eclipse, and other "project direction" type questions, are completely unanswered. It's all very open for you to dive in, write some code, and help determine how best to make Prolint an integral part of working with 4GL/ABL in Eclipse and OpenEdge Architect.


ProED4W

Integrate with the "ED for Windows" editor

Purpose of Proed4w:

If you are using "ED for Windows" (version 4) and are editing .p or .w files, you can use this tool as a communication bridge between ED for Windows and a Progress session.

You can do:
- create a "Compile" button in Ed for Windows
- compile 4GL code from within Ed
- Ed shows compile warnings and errors in its Build results window.

You can also:
Launch Prolint from within ED for Windows to have it check the current sourcefile.


Prolint

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

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, and best of all: there is an e-mail list. So subscribe, and then don't forget to go to your subscription details to enable the e-mail notification!


Syndicate content