Get Eli: Translator Construction Made Easy at SourceForge.net.
    Fast, secure and Free Open Source software downloads

General Information

 o Eli: Translator Construction Made Easy
 o Global Index
 o Frequently Asked Questions

Tutorials

 o Quick Reference Card
 o Guide For new Eli Users
 o Release Notes of Eli
 o Tutorial on Name Analysis
 o Tutorial on Type Analysis

Reference Manuals

 o User Interface
 o Eli products and parameters
 o LIDO Reference Manual

Libraries

 o Eli library routines
 o Specification Module Library

Translation Tasks

 o Lexical analysis specification
 o Syntactic Analysis Manual
 o Computation in Trees

Tools

 o LIGA Control Language
 o Debugging Information for LIDO
 o Graphical ORder TOol

 o FunnelWeb User's Manual

 o Pattern-based Text Generator
 o Property Definition Language
 o Operator Identification Language
 o Tree Grammar Specification Language
 o Command Line Processing
 o COLA Options Reference Manual

 o Generating Unparsing Code

 o Monitoring a Processor's Execution

Administration

 o System Administration Guide

Open PDF File

Eli System Administration Guide

Eli embodies an understanding of how to generate text processors from specifications of their behavior. This understanding has been developed over many years by a host of people, and is expressed in a large number of tools and workflow patterns. The generation process creates many intermediate artifacts, which must be passed among the tools. A change in a specification may make it necessary to rebuild some of these artifacts by executing particular tools.

Odin is a program capable of managing a collection of artifacts and tools to provide a product that is up-to-date with respect to all of the raw material on which it is based. The tools and associated workflow patterns are described to Odin by a derivation graph. Modularity in the derivation graph specification is achieved by gathering related tools and the workflow patterns connecting them into packages.

In order to use Odin to derive specific products from specific raw material, a cache must be available. A cache is represented in the computer by a single directory. It contains a derivation graph built from some set of packages, plus all of the artifacts created when deriving products defined by that derivation graph. Each user may establish an arbitrary number of caches, and each cache may be shared by an arbitrary number of users.