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

Scopes being Properties of Objects

Certain language constructs require that a set of bindings, i.e. a scope is associated as a property of an object. We demonstrate this facility by introducing modules to our language:

ScopeProp.con[21]==

Declaration:    'module' DefIdent ModBlock ';'.
ModBlock:       Compound.
Operand:        ModUseIdent '::' QualIdent.
ModUseIdent:    Ident.
QualIdent:      Ident.

This macro is attached to a product file.

Any object a declared in the ModBlock of a module m, but not in deeper nested Blocks, can be accessed by m::a wherever m is bound to that module. We say the identifier occurrence of a is qualified by m.

A library module (see Scopes Being Properties of Objects of Specification Module Library: Name Analysis) provides computational roles for scopes being associated with object keys:

ScopeProp.specs[22]==

$/Name/ScopeProp.gnrc:inst

This macro is attached to a product file.

The scope of the module body, with its local definitions, is associated as a property with the key representing the module. The role ExportRange of the library module characterizes such an association. ModBlock.ScopeKey is used to specify the key with which the scope property is associated.

ScopePropDef.lido[23]==

SYMBOL ModBlock INHERITS ExportRange END;

RULE: Declaration ::= 'module' DefIdent ModBlock ';' COMPUTE
  ModBlock.ScopeKey = DefIdent.Key;
END;

This macro is attached to a product file.

In binding a qualified identifier occurrence, QualIdent, the role QualIdUse is used to access the scope property associated with the ModUseIdent.Key and bind the identifier. The module computation provides a specification of QualIdent.Scope.

We assume that ModUseIdent indeed has an associated scope . An error message is issued if that assumption is violated, e.g. in the case of a variable identifier.

In addition, the roles used for applied identifier occurrences are associated.

ScopePropUse.lido[24]==

RULE: Expression ::= ModUseIdent '::' QualIdent COMPUTE
  QualIdent.ScopeKey = ModUseIdent.Key;

  IF (AND (NE (QualIdent.ScopeKey, NoKey),
           EQ (QualIdent.Scope, NoEnv)),
  message (FATAL, CatStrInd ("module or class identifier required: ",
                             ModUseIdent.Sym), 0, COORDREF));
END;

SYMBOL ModUseIdent INHERITS IdUseEnv, ChkIdUse, IdentOcc END;

SYMBOL QualIdent INHERITS QualIdUse, ChkQualIdUse, IdentOcc END;

This macro is attached to a product file.