Whitepapers, discussions, and code related to tools for programming in ABL, analyzing existing code, and improving and transforming ABL code.
I am working on a manual of code standards for my division, and would appreciate input about this. I've incorporated (or adapted) many of the entries from the prolint lists of bugs, style improvement, performance enhancements, etc. Of course this will be a combination of helpful advice, common sense, ways to make the code more readable and re-usable, and ways to prevent problems down the line.
I will appreciate any suggestions or ideas that are sent in.
ProUnit is a framework to create automated unit tests for Progress 4GL platform. It's based on other XUnit frameworks, like JUnit, NUnit and others.
The Widget Walker (also known as Widget Viewer and AttriVitoque) is a tool developed by Vito Imburgia at EMEA ETSC.
It helps a developer to preview what they can implement in 4GL (walking from one widget to another, changing an attribute, applying a method or an event) It's really effective when it is set in the proTools.
This tool allows you to enter a query on a table, and reports detailed index selection information for you, including an index tree (of one or more indexes) that the compiler would construct for this query, plus an analysis of indexes for each node of the index tree to help explain why each index was chosen.
The source code for this tool (written in Progress 4GL/ABL V9.1) is included in the download. It is quite heavily commented to help explain all the compiler's index selection behaviour (including how/why multiple indexes are sometimes selected). The UI is very simple so it can be used i
This is a group for keeping track of all ABL development support tools on the Hive
PCT (Progress Compilation Tools) is a set of ANT tasks, designed to compile Progress® procedures and dump/load databases.
PCT is distributed under the Apache License.
This project was born due to the lack of automated Progress® code compiler. PCT is a command-line based tool, so it can be run in batch mode, to generate nightly builds for example. However, as PCT is a set of ANT tasks, your compilation tasks can be run using a graphical frontend to ANT.
These pages are for exploring ideas and designing a new AST and/or "Intermediate Representation" tree for further semantic analysis of 4GL/ABL source code.
The output of Proparse and ProRefactor will be used to generate an IR tree which is more appropriate for control flow, data flow, and other kinds of analysis.
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.