|
|
Benefits (ROI)
Your Return On Investment from Proparse will be fast, and it will
potentially be enormous.
Why Proparse?
Why not just use grep/sed/awk/perl or even 4GL? What do we need a parser for?
Proparse API Quick Introduction
A quick, gentle introduction to programming with Proparse's API via the 4gl.
This is a good place to start if you want to read or write Prolint rules.
Programming Prolint by Example: "noeffect"
Programming a new rule into Prolint is easier than you might think.
Parsers (.doc file download)
John's introductory article titled "Parsers" which was published in
Progressions number 49 (spring 2002).
Tree Parsers
If you are faced with a large scale project which is going to require
the creation of some heavy-hitting parsing tools,
then tree parsers will be of interest to you.
Exchange 2003
Judy's Boston Exchange 2003 presentation
"Prolint: Find Your Bugs Before They Find You"
Exchange 2004
Judy's Las Vegas Exchange 2004 presentation
"Refactoring: Transforming Your Application"
ProRefactor (PDF download)
has two distinct topics. The first topic is refactoring
and how it relates to the 4gl. The second topic is our product,
ProRefactor.
Class Methods (PDF download)
is about using 4gl persistent
procedures as "objects", and proposals for best practices for
using functions and procedures (and naming conventions for those)
as class methods.
Eclipse, Refactoring, and More
is the text from the presentation that John gave at the PUG NL in November 2004.
It also describes Proparse and ProRefactor, and it talks about refactoring
4GL code.
|
|
