> Yes it is. Previously it would only check that (call the
> underlying function)
> when it had already done some reading, now it calls the
> underlying function as
> part of the actual check, and that is potentially done quite
> a lot of times
> before it really has something to deliver.

OK, now I understand.

Would the preferred solution be to call data_pending() immediately after the
read and save the result in a state variable, instead of calling it
repeatedly?
Received on 2007-07-04