Re: Blocking read() from a USB->Serial adapter.

On 2006-11-25, Charles Sullivan <cwsulliv@xxxxxxxxxxxx> wrote:

If that's the case, then that answers my questions. I thought
blocking meant blocking until the specified number of
characters is read, or until the read is interrupted.

Or until the driver decides to return for whatever reason it
chooses. On success, you're guaranteed a minimum of one byte.

--
Grant Edwards
grante@xxxxxxxx
.

Relevant Pages

  • Re: Capturing Keystrokes that are not permitted within a TextArea
    ... Fair point but this application is secure anyway, the only reason we're ... blocking these characters is because it makes the end result a bit tricker, ...
    (comp.lang.javascript)
  • Re: Blocking read() from a USB->Serial adapter.
    ... returning fewer characters than specified if the characters ... But I had the impression that a blocking read is supposed to block ... available (e.g. if some disk has to position its head first, ... both return all data the driver has available for you at ...
    (comp.os.linux.development.apps)
  • Re: Blocking read() from a USB->Serial adapter.
    ... blocking meant blocking until the specified number of ... characters is read, or until the read is interrupted. ... Or until the driver decides to return for whatever reason it ... On success, you're guaranteed a minimum of one byte. ...
    (comp.os.linux.development.apps)
  • Re: Blocking read() from a USB->Serial adapter.
    ... blocking meant blocking until the specified number of ... Or until the driver decides to return for whatever reason it ... On success, you're guaranteed a minimum of one byte. ...
    (comp.os.linux.development.apps)
  • Re: Blocking read() from a USB->Serial adapter.
    ... Grant Edwards wrote: ... blocking meant blocking until the specified number of ... characters is read, or until the read is interrupted. ... Or until the driver decides to return for whatever reason it ...
    (comp.os.linux.development.apps)