Eli   Documents
Eli: Translator Construction Made Easy

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 Scope Graphs
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

Specifying the mapping between concrete and abstract syntax

Eli deduces the correspondence between the concrete and abstract syntaxes based on the user specifications in .con, .lido and .map files.

 

Typical Error Situation

Often caused by typing mistakes:

.map: MAPSYM a_or_b : a b.

.con: x : a b.

.lido: RULE: x ::= a_or_b ',' a_or_b END;

This .lido rule does not match a concrete grammar rule. It is added to the parsing grammar.

==> a_or_b is considered to be a terminal.

==> ERROR: No GLA specification for a_or_b

Back to Typical Eli Errors