stfc/claw-compiler

CLAW FORTRAN Compiler

claw-compiler's Issues

Add optional build target for Jython dependence

Since we don't want Jython to become a mandatory dependence for CLAW, we need to extend the build system with an optional target.

Implement lightweight plugin framework for loading Jython-dependent code into CLAW

In #4 we added the ability to optionally build code that depends on Jython. We will now use that support to add-in a lightweight plugin framework to load-in such code to CLAW at run-time. (Since Java does not have a pre-processor to handle optional compile-time dependencies.)

Add command-line arg to supply script and re-factor ClawTranslatorDriver

This issue adds a command-line argument to allow the name of a Python script to be passed in to Claw. If this script is supplied then we wish to drive the code translation from that script and therefore
require a different translator driver. We will therefore introduce a base translator driver and have the current (ClawTranslatorDriver) and new (ClawPythonTranslatorDriver) inherit from it.

Related issues (if any)

Issue #1

PSyclone-compatible version of CLAW

In bringing this fork of CLAW up-to-date with the upstream, I've broken compatibility with PSyclone. This issue will apply a temporary fix so that the new CLAW-interface functionality in PSyclone can be reviewed.

Prototype claw-python interoperability.

Currently CLAW applies transformations based on the existence of !$claw directives and rules in an XML configuration file.
In this issue we will add support for a user to specify a (Python) script on the command line.