Sat Jul 18 10:21:41 CEST 2009


the error seems to be in "interpret-stream" which leaves the stream
instance on the top of the stack.

"stream>input" seems to be the culprit

no, it works: something doesn't clean up.. but what is it?  probably
some exception that's not reported..

i find myself trapped now in the non-debuggable part of the code:
the exception mechanism is not transparent.  also, the fact that this
read code is bootstrapped doesn't help..

maybe time to clean it up a bit?  having both nonlocal exits and
primitives that call other primitives and inspect the error return
value causes problems..

most of the code seems to work though, except for this weird bug..