[gpsd-users] Documentation issues...

[Ezmer DeKleaner]

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?

Also, it has another function discrepancy (or I am just challenged in understanding all this.. probably more likely :( )

One part of documentation says nonblocking, other says blocking.

• Nonblocking check to see if data from the daemon is waiting. Named something like "waiting()" and taking a wait timeout as argument. Note that choosing a wait timeout of less than twice the cycle time of your device will be hazardous, as the receiver will probably not supply input often enough to prevent a spurious error indication. For the typical 1-second cycle time of GPSes this implies a minimum 2-second timeout.

gps_waiting()

gpsmm.waiting()

gps.waiting()

Blocking check with timeout to see in input is waiting.

Many thanks in advance, and sorry if I am just having problems with my reading comprehension.