General Information

	Eli: Translator Construction Made Easy
	Global Index
	Frequently Asked Questions
	Typical Eli Usage Errors

Tutorials

	Quick Reference Card
	Guide For new Eli Users
	Release Notes of Eli
	Tutorial on Name Analysis
	Tutorial on Scope Graphs
	Tutorial on Type Analysis
	Typical Eli Usage Errors

Reference Manuals

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

Libraries

	Eli library routines
	Specification Module Library

Translation Tasks

	Lexical analysis specification
	Syntactic Analysis Manual
	Computation in Trees

Tools

	LIGA Control Language
	Debugging Information for LIDO
	Graphical ORder TOol

FunnelWeb User's Manual

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

Generating Unparsing Code

Monitoring a Processor's Execution

Administration

System Administration Guide

Tutorial on Name Analysis

Kernel Grammar

The kernel grammar of the example language specifies the structure for Program, Block consisting of Declarations and Statements, and trivial Expressions. Different forms of Declarations, Statements, and Expressions are added to the grammar as the name analysis task is further refined.

Core.con[1]==

Program:        Source.

Source:         Block.
Block:          Compound.
Compound:       'begin' Declaration* Statement* 'end'.


Statement:      Expression ';'.
Expression:     Operand.
Operand:        IntNumber.

This macro is attached to a product file.

Expressions and Operands are represented by Expression contexts in the tree grammar.

Core.sym[2]==

Expression ::= Operand.

This macro is attached to a product file.

The notation of identifiers and numbers is chosen as in Pascal.

Core.gla[3]==

Ident:          PASCAL_IDENTIFIER
IntNumber:      PASCAL_INTEGER
                PASCAL_COMMENT

This macro is attached to a product file.

In the course of refining the name analysis task we will introduce several different contexts for identifier occurrences. Each occurrence has to have the attribute Sym representing the identifier encoding. Hence we specify a computational role IdentOcc that provides that attribute, and will be inherited by any identifier occurrence.

Core.lido[4]==

TERM Ident: int;
ATTR Sym: int;
CLASS SYMBOL IdentOcc COMPUTE SYNT.Sym = TERM; END;

This macro is attached to a product file.