Very late error reports under Windows

[Jocelyn Paine <popx at pop3 dot ifs dot org dot uk>]

Using Kawa under Windows NT 4, there seems to be a problem in reporting
errors from the top-level. Here's an example, which I ran
just by doing java kawa.repl -w . I use an undefined symbol
++, and the error message relating to it doesn't appear even after the
next correct expression is evaluated in prompt 4. In fact, it
seems to require to be forced out by a second error:

  #|kawa:1|# (+ 1 2)  
  3

  #|kawa:2|# (++ 1 2)
  #|kawa:3|# ; No error message about misuse of ++ appears.
  #|kawa:4|# (+ 1 2)
  3

  #|kawa:5|# ; Stil no message.
  #|kawa:6|# (// 1 2)
  gnu.mapping.UnboundSymbol: Unbound symbol ++
  	at gnu.mapping.Environment.getChecked(Environment.java:223)
	at kawa.standard.ScmEnv.getChecked(ScmEnv.java:37)
	at gnu.expr.ReferenceExp.eval(ReferenceExp.java:84)
	at gnu.expr.ApplyExp.eval(Compiled Code)
	at gnu.expr.ModuleExp.evalModule(ModuleExp.java:38)
	at kawa.Shell.run(Compiled Code)
	at kawa.Shell.run(Shell.java:35)
	at kawa.repl.apply0(repl.java:27)
	at gnu.mapping.Future.run(Future.java:59)

  gnu.mapping.UnboundSymbol: Unbound symbol //

  #|kawa:7|# ; Now we've got the message that should have appeared 4 prompts ago.
             ; And part of the following one, but not its trace.

Jocelyn Paine
http://www.ifs.org.uk/~popx/
+44 (0)7768 534 091