scsh-users
[Top] [All Lists]

Re: Elusive pipe I/O bug in Scsh?

To: scsh@zurich.ai.mit.edu
Subject: Re: Elusive pipe I/O bug in Scsh?
From: sperber@informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor])
Date: Mon, 17 Feb 2003 13:07:45 +0100
>>>>> "janky" == Stefan Jankowski 
>>>>> <dave.null@spambucket.informatik.uni-freiburg.de> writes:

>>>>> "Michael" == Michael Sperber [Mr Preprocessor] 
>>>>> <sperber@informatik.uni-tuebingen.de> writes:

Michael> The trivial question is whether you're sure that your
Michael> helper program always flushes its output to point where a
Michael> complete S-expression results.

janky> Is this a problem? Wouldn't (read) block anyway until it has read a
janky> complete sexp?

It would, but I was wondering whether a confusion between blocking and
EOF could be the result of what you're seeing.

janky> My understanding is that (read) treats its input as a simple stream of
janky> octets without regard to linebreaks (other than treating them as
janky> whitespace) or blocking in OS-level reads; or am I missing something?

No, you're correct.

So, again, it would be helpful to see (at least some of) your code,
specifically concerning the way you process pipes are connected.

-- 
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla

<Prev in Thread] Current Thread [Next in Thread>