gpsd-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gpsd-dev] ✘CEP(50) 0.285 metersMime-Version: 1.0


From: Hal Murray
Subject: Re: [gpsd-dev] ✘CEP(50) 0.285 metersMime-Version: 1.0
Date: Fri, 22 Jul 2016 14:29:53 -0700

address@hidden said:
> And I can't see how to force Python to use a 64-bit long.  Got a clue for
> me?

Python defaults to double.

https://docs.python.org/2/library/stdtypes.html

There are four distinct numeric types: plain integers, long integers, 
floating point numbers, and complex numbers. In addition, Booleans are a 
subtype of plain integers. Plain integers (also just called integers) are 
implemented using long in C, which gives them at least 32 bits of precision 
(sys.maxint is always set to the maximum plain integer value for the current 
platform, the minimum value is -sys.maxint - 1). Long integers have unlimited 
precision. Floating point numbers are usually implemented using double in C; 
information about the precision and internal representation of floating point 
numbers for the machine on which your program is running is available in 
sys.float_info. Complex numbers have a real and imaginary part, which are 
each a floating point number. To extract these parts from a complex number z, 
use z.real and z.imag. (The standard library includes additional numeric 
types, fractions that hold rationals, and decimal that hold floating-point 
numbers with user-definable precision.)


address@hidden said:
> We aim to have gpsd run on 32 bit and 64 bit systems.  RasPi's, Odroid's and
> BBB's currently are 32 bit only. 

Can't you use int64_t and friends.


-- 
These are my opinions.  I hate spam.






reply via email to

[Prev in Thread] Current Thread [Next in Thread]