Eli   Documents

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

New Features of Eli Version 4.2

Previous Chapter Next Chapter Table of Contents


Caution Needed in Specifying a Compiler

The environment variable ELI_CC can be used to specify the C compiler that should be used to compile user-provided and Eli-generated code. Specification of a C compiler in this manner is considered to be "permanent", so Eli assumes that the value of ELI_CC will remain unchanged over the life of a cache. If you change the value of ELI_CC, you should restart Eli with the eli -r command to reset the cache. Otherwise, Eli will mix object code produced by the two compilers with unpredictable results.

You can also specify the C compiler to be used by means of the +cc parameter. That specification holds only for the request containing it. Eli will guarantee that all of the object code needed to satisfy that request was produced by the specified compiler. Successive requests specifying different compilers will be handled correctly.


Previous Chapter Next Chapter Table of Contents