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


 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


 o Eli library routines
 o Specification Module Library

Translation Tasks

 o Lexical analysis specification
 o Syntactic Analysis Manual
 o Computation in Trees


 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


 o System Administration Guide

Mail Home

New Features of Eli Version 4.1

Previous Chapter Next Chapter Table of Contents


The Noosa system (invoked using the :mon product has undergone some major changes since the last release of Eli. Numerous small changes have been made to the user interface but the general appearance is the same.

The default font is not specified by Noosa any more. You now get whatever your Tk setup gives you by default, but you can set it yourself using the Noosa*Font resource in your .Xdefaults. More support for resources will be provided in future releases.

The previous version displayed the complete abstract syntax tree drawn in a conventional fashion. The new version also includes a tree display that allows a partial view of the tree and takes up much less space. It is designed for browsing of the tree and nodes can be selectively opened and closed. You can select which of the kinds of tree display you want using the Abstract Tree item in the Windows menu.

Eli and Noosa now have support for attribution monitoring so the nodes in the tree displays provide access to the node attributes. You can elect to see the values of attributes; they are displayed in the transcript window when next computed. Optionally you can also make the program stop when the value of an attribute is computed (a form of breakpoint).

The Windows menu has a new entry called Files. This brings up a window from which it is possible to display and edit files while you are monitoring (e.g., to fix bugs in your specs or to alter the process input). The Open menu item in the Noosa menu is no longer provided since its functionality is subsumed by the new window type. You can have as many file windows as you like. They support emacs-style key bindings and support searching.

Sensitive areas in the transcript are now always underlined and you just have to click on them with B1 (a'la netscape) to "open" them. What "opening" means depends on the kind of value. In the current version the sensitive areas are coordinates (or coordinate ranges), abstract tree nodes (Nodes), and pattern-based text generator nodes (PTGNodes). Opening a coordinate (or range) highlights that coordinate (or range) in the input window. Opening an abstract tree node highlights the node in an abstract tree window (if there are any). Opening a PTGNode causes the text expansion of that node to be printed at the bottom of the transcript window. Future versions of Noosa will support opening other types of values such as environments and definition table keys.

In this version of Eli the :mondbx and :mongdb products are not operational due to the new Noosa implementation. This situation will be remedied as soon as possible with the fixes being made available via an Eli patch.

Previous Chapter Next Chapter Table of Contents