[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gpsd-users] Documentation Questions
From: |
Eric S. Raymond |
Subject: |
Re: [gpsd-users] Documentation Questions |
Date: |
Tue, 23 Jul 2013 10:46:28 -0400 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
Ezmer DeKleaner <address@hidden>:
>
> Looking at the documentation on
> http://catb.org/gpsd/client-howto.html#_python_examples
>
> there appears to be an inconsistency.
>
> On (Table 1. Entry points in client bindings) it shows for gps_read() that
> it is NONBLOCKING.
>
> gps_read()
> gpsmm.read()
> gps.read()
> Nonblocking read for data from the daemon
>
>
>
> Above it has a paragraph with the following statement:
>
> Blocking read for data from the daemon. Named something like "read()" (this
> was "poll()" in older versions).
>
> My experience is that this appears to be a BLOCKING read. Can I get some
> confirmation?
That is correct. The contradicting description is left over from an earlier
version of the API. Same story with gps_waiting(). I have fixed both.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>