[gpsd-dev] Fw: Documentation issues...

[Gary E. Miller]

Yo All!

Ezmer DeKleaner <address@hidden> is having trouble posting
to the list.  So I'm just forwarding this for him.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97701
        address@hidden  Tel:+1(541)382-8588


---------- Forwarded message ----------
From: Ezmer DeKleaner <address@hidden>
Date: Wed, Jul 17, 2013 at 5:39 PM
Subject: Documentation issues...
To: 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?


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



   - 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.

Thanks, this is what I have been trying to post.

and I also do not get any messages from the 'mailman' regarding new posts.

Ezzy

---------- Forwarded message ----------
From: Ezmer DeKleaner <address@hidden>
Date: Wed, Jul 17, 2013 at 5:39 PM
Subject: Documentation issues...
To: 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?

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

• 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.

signature.asc
Description: PGP signature