Paul Davis wrote:
Don't make this mistake: poll *have* to return immediately in *all*
cases where to wait is useless (i.e. when no non-user driven event may
happen).
This is the rule you need to remember.
where does this rule come from? i was under the impression that
poll(2) should
Today Abramo Bagnara wrote:
Paul Davis wrote:
Don't make this mistake: poll *have* to return immediately in *all*
cases where to wait is useless (i.e. when no non-user driven event may
happen).
This is the rule you need to remember.
where does this rule come from? i was under the
Don't make this mistake: poll *have* to return immediately in *all*
cases where to wait is useless (i.e. when no non-user driven event may
happen).
This is the rule you need to remember.
where does this rule come from? i was under the impression that
poll(2) should timeout in those cases, not
On Sun, 2 Dec 2001, Tim Goetze wrote:
On Dec 1 Abramo Bagnara wrote:
Tim Goetze wrote:
Abramo Bagnara wrote:
Don't make this mistake: poll *have* to return immediately in *all*
cases where to wait is useless (i.e. when no non-user driven event may
happen).
This is the rule
Tim Goetze wrote:
and another related problem: when i poll any stream before it is started,
poll() returns immediately, too. while one may in an esoteric mood argue
that this makes sense in the playback case since the stream *is* ready for
data, this behaviour is nonsense with a capture
Abramo Bagnara wrote:
Don't make this mistake: poll *have* to return immediately in *all*
cases where to wait is useless (i.e. when no non-user driven event may
happen).
This is the rule you need to remember.
ok. here's a rule simple enough for me to remember :) but should poll in
this case,
Tim Goetze wrote:
Abramo Bagnara wrote:
Don't make this mistake: poll *have* to return immediately in *all*
cases where to wait is useless (i.e. when no non-user driven event may
happen).
This is the rule you need to remember.
ok. here's a rule simple enough for me to remember :)
On Dec 1 Abramo Bagnara wrote:
Tim Goetze wrote:
Abramo Bagnara wrote:
Don't make this mistake: poll *have* to return immediately in *all*
cases where to wait is useless (i.e. when no non-user driven event may
happen).
This is the rule you need to remember.
ok. here's a rule simple