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

Eli System Administration Guide

Previous Chapter Next Chapter Table of Contents


Problem Reporting

Should you have a problem with Eli please e-mail a description to:

eli-project-users@lists.sourceforge.net

When reporting problems, please include the Eli version number (printed when Eli starts up, or available in the distribution in `Eli/pkg/version/version.dg') and the output from running the shell command uname -a on your system. Also, please give complete output illustrating the problem. If necessary, please include relevant specification files.

In some cases it will also be helpful to identify the version of the software in question. Most distributed files have RCS tags embedded in them. Most executables are generated from sources that have an initialized variable containing version information:

char rcsid[] = "$Id: misc.c,v 1.2 88/11/30 12:57:39 bob Exp $";

It is easy to identify the source versions from which binaries have been generated by running the RCS ident utility on them. For example, running ident on `pkg/gla/gla_fe' would yield something like the following:

gla_fe:
     $Id: driver.c,v 1.15 1996/03/22 19:28:48 kadhim Exp $
     $Id: dfltclp.c,v 1.8 1994/12/08 03:09:52 tony Exp $
     $Id: source.c,v 2.5 1995/01/16 02:19:21 waite Exp $
 ...
Sites that do not have ident can extract this information by one of the following commands:
Source
grep '\$Id:' `file-name'
Executable
strings `file-name' | grep '\$Id:'


Previous Chapter Next Chapter Table of Contents