Koopa (COBOL) Parser Generator

Koopa is a parser generator designed for COBOL. The COBOL parser can handle source files in isolation (no preprocessing required) and doesn't mind the presence of CICS/SQL fragments. The grammar is easily extensible in a way which minimizes the impact on the overall code.

Check out the guide for details on the original design decisions.

Features

Island parser generator
COBOL lexer and parser
Accepts free, fixed and variable format COBOL
Covered by a COBOL 85 testsuite, and grammar unit testing
COBOL viewer with syntax highlighting, outline, quick navigation and XPath-based querying
XML dumps of parse trees
COBOL preprocessor:
- copybook expansion with support for REPLACING
- REPLACE statement

Licensing

Everything in Koopa is covered by a BSD license, unless noted differently in the actual file or folder.

The files in the testsuite/cobol85 folder are a COBOL85 test suite by the National Computing Centre, UK, found originally at www.itl.nist.gov. The version here differs only in that it splits up the different programs in separate files, where the original puts them all in one big file. The licensing is unclear, but the code is offered publicly at the above site.

Configuration options

Some runtime customisation of Koopa is possible by the user.

Command line

Following options can be set on the command line by passing them as -D<option>=<value> to the JVM.

koopa.maxCobolWordLength: defaults to 31. Use a value greater than zero to override this. Setting it to 0 makes it use the default value. Setting it to a negative value disables the length check all together. (Cfr. the koopa.cobol.CobolWords class.)
koopa.cobol.sources: a comma-separated list of file extensions use to identify COBOL source files. This defaults to "cbl,cob". (Cfr. the koopa.cobol.CobolFiles class.)
koopa.cobol.copybooks: a comma-separated list of file extensions use to identify COBOL copybook files. This defaults to "cpy,copy". (Cfr. the koopa.cobol.CobolFiles class.)
koopa.cobol.project_class: use a specific koopa.cobol.CobolProject subclass when searching for copybooks on the file system. This defaults to koopa.cobol.projects.StandardCobolProject.
koopa.optimize: set to false to switch off optimization of choices and permutations.

GUI

Most of the command line options can also be set directly from the Koopa GUI, through the "Parser settings" menu.

Custom columns

The user can add custom XPath queries to the standard parsing overview tab.

To enable this, users should update their koopa.properties file with a koopa.customColumns property containing a comma-separated list of string identifiers. For every identifier, there should be koopa.customColumn.<identifier>.title and koopa.customColumn.<identifier>.xpath properties.

For example:

koopa.customColumns=statements,functions

koopa.customColumn.statements.title=Statement Calls
koopa.customColumn.statements.xpath=count(//statement)

koopa.customColumn.functions.title=Function Calls
koopa.customColumn.functions.xpath=count(//function)

Complex XPath query results should be presented in serialized form.

Technical Info (for Developers)

Java 8

The minimum target runtime environment for Koopa is Java 8. To that end the build script forces everything to be compiled to Java 8 compatible bytecode. This, however, is not enough to ensure Java 8 compatibility as you may still be compiling against the library of a later Java version. For that reason you also need to specify where the Java 8 runtime library can be found, by setting the JAVA8_BOOTCLASSES environment variable to its location.

You may see following message when building the project with ANT:

Please make sure JAVA8_BOOTCLASSES is set to a valid Java 8 bootstrap classpath.
You may get builds which are not compatible with Java 8 otherwise.

This is a reminder from the build script that you have not specified where the Java 8 runtime library may be found.

Parser Generation

Koopa Grammar files end in .kg (for "Koopa grammar"). These are processed by the koopa.dsl.kg.KGG class. You can pass it one of the following:

A path to a specific .kg file, which it will then translate.
A path to a folder, which will then be searched for .kg files, all of which will get translated.

All of this is taken care of by the ANT build script. If you make modifications to the standard Cobol.kg or one of the tests all you need to do is rerun ANT and everything should be taken care of.

If you're using an IDE such as Eclipse you may need to refresh your workspace after building with ANT.

Tests

Koopa has unit tests covering the Koopa implementation. Look for package names named test, or check the different run-FOO-tests targets in the build script.

Note that many, if not most tests, are defined using custom formats. The grammar unit tests, for instance, are all in .stage files. I do this to reduce the amount of friction writing individual tests, so that new tests can be written more easily and in a shorter amount of time.

There is also support for regression testing based on the COBOL85 testsuite. This will attempt to parse all source files (once with and once without preprocessing), and compare the results with those of a previous run. Look for the run-cobol-regression-tests build target.

All unit tests can be triggered from ANT. Simply invoke ant run-tests on the command line.

Random tests

The grammar unit tests have the option of being randomized, assuming there are definitions referencing other definitions. To enable this set koopa.tests.random to true, and koopa.tests.random.limit to a positive integer value. Each definition which can be randomized will than be randomized a number of times, up to the given limit.

krisds / koopa