Guide for New Eli Users
The Eli system documentation
is divided into three basic groups:
- Strategies and examples for using Eli.
The purpose of this material is to present simple techniques that work.
Only points that we have found important for most users are covered.
- Detailed definitions of notation and behavior.
The purpose of this material is to answer any question that might arise.
There is a reference manual for each of the notations understood by Eli,
including the language in which requests for processor construction are made.
All of the products that can be requested, and all of the parameters that can
be used to modify those requests, are the subject of a separate reference
Finally, there is a reference manual for the on-line documentation browser.
- Strategies for installing, configuring and maintaining Eli.
The purpose of this material is to guide the person responsible for Eli at a
All of the documentation is available both on-line and in printed form.
Documents are stored on line as hypertext, and can be used
to support the debugging phase of a project.
Two levels of debugging
are necessary when using Eli:
The specifications you present to Eli may be inconsistent or
In that case, Eli will provide error reports in the same way as any
You must correct the specifications so that they are well-formed and
You have presented a correct specification to Eli, but this specification
describes the wrong problem instance.
Now you must determine how the problem instance you have described differs
from the one you are really interested in, and change the specification
On-line documentation for Eli can only provide support for level (1),
because level (2) does not involve symptoms that can be diagnosed by Eli.
Eli presents error reports to a user only on request.
The available requests are described in
Diagnosing Specification Inconsistencies of Products and Parameters Reference Manual.
One of these requests is
This request builds a new hypertext subtree containing the error reports,
embedded in the text to which they refer.
The files containing the errors are made accessible to the nodes describing
those errors, so that the user can correct them directly.
To correct a file, move the browser to the node describing the errors in
Execute the browser's edit command and make whatever changes are necessary.
Then exit the editor.
Error reports are also linked to the nodes of the on-line documentation
describing the constructs in which the errors were detected.
Thus the user is placed in an environment in which all of the information
needed to diagnose the errors, and the tools needed to correct them, are
immediately at hand.