[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bindings of *DEBUG-IO*
- To: firstname.lastname@example.org
- Subject: bindings of *DEBUG-IO*
- From: email@example.com
- Date: Thu, 1 Aug 1996 18:01:39 +0100 (BST)
I'm getting confused about the binding of *DEBUG-IO* when
using clisp non-interactively with the -x command line option.
It appears that *DEBUG-IO* becomes a two-way-stream, rather than
a synonym for *TERMINAL-IO*. However I can't find this documented
anywhere in either the manual page describing -x, or the
implementation notes, grepping the doc directory left me none the wiser.
This is probably the correct thing to do -- after all
if you're not interactive you don't want to prompt the user for
continues after CERROR.
So my question is what are the stream binding differences between
interactive and -x usage? Is my supposition correct and is *DEBUG-IO*
a null input stream when non-interactive?
thanks in advance.
Nathan Sidwell Holder of the Xmris home page
Chameleon Architecture Group at SGS-Thomson, formerly Inmos
http://www.pact.srf.ac.uk/~nathan/ Tel 0117 9707182
firstname.lastname@example.org or email@example.com or firstname.lastname@example.org