Re: [OT] Re: fgets() and embedded null characters
From: Chris Croughton (chris_at_keristor.net)
Date: 03/19/05
- Next message: Joona I Palaste: "Re: Shared Memory Problem"
- Previous message: Chris Croughton: "Re: Wrong-but-not-incorrect code"
- In reply to: Eric Sosman: "[OT] Re: fgets() and embedded null characters"
- Next in thread: CBFalconer: "Re: fgets() and embedded null characters"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 19 Mar 2005 15:01:18 +0000
On Fri, 18 Mar 2005 17:42:47 -0500, Eric Sosman
<eric.sosman@sun.com> wrote:
> <off-topic>
>
> It's buffering, because it takes time for the "Please
> stop" request to get back to the sender and for the sender
> to act upon it, and during that time the characters keep
> on coming.
Plus if you are sending as well you have to interrupt that to insert the
request. Unless you use the RTS/CTS/DTR/DCD lines, but they depended
(with modems) on actually switching the carrier off (and hence not
sending anything).
> Another method was to have the sender stop of its own
> volition after sending the CR, until the terminal sent a
> "Go ahead" when it was once again ready. This eliminated
> the latency of the "Please stop" method, but at the cost
> of some extra electronics in the terminal -- non-negligible
> in the days of discrete-component circuit boards. It was
> also prone to assorted synchronization deadlocks, where
> each side was waiting for the other to utter something on
> a silent (often half-duplex) line ...
Electronics? I was talking about things like the Teletype(R) Model 33
ASR, which was totally mechanical. Inserting an X-OFF character
automatically would have been a real pain, there was no buffering at the
terminal at all.
> Ah, those were the days! Less rosy by far than fading
> memory paints them, but there's absolutely no denying that
> they were "days."
Yup, they were days. And weeks...
(But at least you could read output as it appeared. 10 or possibly
30cps is readable, these things which scroll off the screen before you
even see that they've started are a pain...)
> </off-topic>
Chris C
- Next message: Joona I Palaste: "Re: Shared Memory Problem"
- Previous message: Chris Croughton: "Re: Wrong-but-not-incorrect code"
- In reply to: Eric Sosman: "[OT] Re: fgets() and embedded null characters"
- Next in thread: CBFalconer: "Re: fgets() and embedded null characters"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|