Re: [clisp-list] stream trouble

[Russell S. <se...@ar...>]

>>>>> "Sam" == Sam Steingold <sd...@gn...> writes:

Sam> try this: 

Sam>    (let ((true-input (two-way-stream-input-stream
Sam>                       (symbol-value (synonym-stream-symbol
Sam>                       *standard-input*))))) 
Sam>       (setf (stream-element-type true-input) '(unsigned-byte 8))
Sam>       (read-byte-sequence buffer true-input))

I ran the following at the Linux command line (clisp-2.27):

  $ clisp -q -norc -x '(let ((true-input (two-way-stream-input-stream (symbol-value (synonym-stream-symbol *standard-input*))))) (describe true-input)) (exit)'

  *** - SYNONYM-STREAM-SYMBOL: argument #<INPUT STRING-INPUT-STREAM> should be a stream of type SYNONYM-STREAM

Starting CLISP normally and playing around, I find:

  [1]> (describe *standard-input*)

  #<IO SYNONYM-STREAM *TERMINAL-IO*> is an input/output-stream.

  [2]> (two-way-stream-input-stream *terminal-io*)

  *** - TWO-WAY-STREAM-INPUT-STREAM: argument #<IO TERMINAL-STREAM> should be a stream of type TWO-WAY-STREAM
  1. Break [3]> 

If *terminal-io* isn't of type TWO-WAY-STREAM, what is an input/output-stream?


-- 
Russell Senior         ``The two chiefs turned to each other.        
se...@ar...      Bellison uncorked a flood of horrible       
                         profanity, which, translated meant, `This is
                         extremely unusual.' ''