                	Bug Hit List
                        ============

A lot of work has been expended on SEQUEL version 7.0 to make sure that
it runs reliably.  There are still some minor hiccups with the system that
need to be ironed out.  The known problems are:-

Graphical Interface

(1)  When loading an framework in which a window is small because there
     are few tactics/rewrite rules in it; if another framework is loaded
     afterwards the window does not expand.
(2)  Very occasionally, the graphical interface reports a segmentation
     error that lands control in the break package.  Typing (restart),
     (type-) and (update-statistics) generally does the trick.  If not, 
     quit and start from a clean image.  We're puzzled about this one and 
     do not know whether it is a fault in ATHENA widgets or whatever.
     It generally happens when the graphical interface has been in use
     for 2 hours or so.
(3)  Sometimes on exiting the graphical interface the stats window goes
     blank. Typing (type-) and (update-statistics) will refresh it.
(4)  Sometimes the proof tool does not return yes until the mouse arrow 
     is moved around the proof tool window.
 
Main Program

(1) Functions declared in the mutual macro do not type-check if they
    include a {}-bracketed signature with a type variable within it.

(2) Constraint propagation in the top level sometimes works erratically. 

(3) The file err.lisp cannot be compiled without producing an non-equivalent
    function.  This is a fault in Lucid Common Lisp version 4.01. 

(4) When diverting a file or saving a framework sometimes a piece of junk
    is sent to the output stream.  This is probably a fault in Lucid Common 
    Lisp version 4.01.  The error seems to occur when the output file is
    being overwritten.  The cure is not to overwrite files but to create
    new ones. 

(5) When trying to save a framework where some of the code is compiled
    an error message may be generated.  This is not really a bug; 
    SEQUEL can only save interpreted code.  However this can happen if
    you load a compiled framework and then afterwards load an interpreted
    framework and then try to save it.  

(6) When trying to save a framework, functions that are suppressed may
    not be saved.  In such a case; do not use suppress. But invoke it
    after loading the saved framework.

							Mark Tarver
