Eli   Documents 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
 o Typical Eli Usage Errors

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
 o Typical Eli Usage Errors

Reference Manuals

 o User Interface
 o Eli products and parameters
 o LIDO Reference Manual
 o Typical Eli Usage Errors

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

Mail Home

New Features of Eli Version 4.4

Previous Chapter Next Chapter Table of Contents


New functionality for unparser generation

Textual representations of tree-structured data objects can now be produced in five standard forms: a generic functional notation (as with Eli 4.3.x), an XML description of the data object, C++ code that will re-build the data object, Java code that will re-build the data object, and code describing the graph to the daVinci graph visualization tool (assumes daVinci 2.1, found at http://www.informatik.uni-bremen.de/daVinci/). It is also possible for the user to specify their own notation for describing tree-structured data objects (see Languages describing tree structure of Abstract Syntax Tree Unparsing).

Default output for terminal symbols has now been provided. The default assumes that the internal representation for the terminal symbol is a string table index. Token processors establish the internal representations for terminal symbols; mkidn and mkstr result in string table indices, whereas mkint does not. If you want to unparse a tree whose terminal symbols are not represented by string table indices, you need to override the default output (see Overriding PTG patterns of Abstract Syntax Tree Unparsing).


Previous Chapter Next Chapter Table of Contents