1.  Our software does not support programs using read from keyboard. 
    The input will be taken from the xterm window that started stk.
    However it will also be considered as input into stk if it's 
    running it's own prompt there.  
    To fix this need to redirect input in the eval loop from some
    place, but what's difficult is to make the characters typed on the
    IIW go to that port.
	Possible alternatives:  redefine read.


2.  format #t outputs to the startdat out no matter what
    (current-output-port) returns, while display works porperly it
    seems.

3.  The output in IIW contains extra quotes. The problem originates from
    our way of redirecting the target program stdout through a file to
    the IIW. 
    File: portfix.stk

4.  Due to STk problems use of dynamic-wind makes the xscheme very unstable.
    Especially using it to swap ports around user code evaluation in IIW 
    caused often and random segfaults. On of the conditions that seem to 
    kill it is using a catch withing the second thunk of dynamic-wind
    when the catch returns true.  The port assignments in this case are 
    somehow lost and a general instability exists after the exception so that
    a normal statement can cause a segfault.

5.  Our procedures are very dependent on other names existing in
    global envaronment.  pp depends on reverse for example.

    To Fix:  need to do the  (let ((reverse reverse)) our code)  trick!

7.  Catch statements in user code are not supported because of a
    conflict with dynamic-wind in *xs-iiw*.

8.  Nested breakpoints are not supported further then two levels,
    meaning that if a break point is set on an expression and another
    one is set on an expression that is an element in the first.
    Problem in break:index.
    To fix:  rewrite code for break.stk to use two indexing functions --
	     one that can index the inserted break structures (for removing
	     them) and another that transparentely indexes inside the break
	     structures (for inserting new ones).

9.  Separating XScheme code in a diferent environment had a terrible effect on
    performance.  When pp.stk (pretty printer) was moved out of xs-environment
    it started to run 10 times faster.  When view-expr (expression viewer that
    calls pp) was also moved out the speed increased another 5 times (approx).

10. Text selection in expression viewer widgets is very strange.
    The selection tag must be the top priority.
    Fixed????

11. Setting breakpoints in functions which are called from watch expressions
    will cause infinite loop. The fix is to disable the breakpoints during
    evaluation of watch expressions, but that failed to work and broke the
    rest of the breakpoint mechanizm when attempted.  Currentely the fix is
    disabled (see use of *xs-watch-re-evaluation* variable in break.stk and
    throughout the program).
