tags:

views:

1024

answers:

4

There doesn't seem to be a clear answer to this in the documentation.

I'm interested in incrementing a variable time that counts the seconds since the program started. If the maximum value can count far into the future, like 100 years, then I don't care about letting the variable increment forever. Otherwise I'm going to have to think of a good point to reset time back to 0.

A: 

I found this email on the lua users site

The Lua core does not make use of 64 bit datatypes, except implicitly through size_t or ptrdiff_t (which happen to be 64 bit on a 64 bit box).

sizeof( float ) == 4
sizeof( double) == 8

You can define lua_Number to be a double (default), float or any integer with at least 32 bits. There are side effects though and some extensions may cease to work due to the limited range of floats or ints. The core should be fine, though.

Ólafur Waage
+6  A: 

as compiled by default, the Number is a double, on most compilers that's an IEEE 64-bit floating point. that means 10bit exponent, so the maximum number is roughly 2^1024, or 5.6e300 years. that's a long time.

now, if you're incrementing it, you might be more interested in the integer range. the 52-bit mantissa means that the highest number that can be used with integer precision is 2^52, or 1.427e8, almost 150 million years. still a very long uptime for any process

Javier
Thanks, I can stand being hated by a few programmers 150 million years from now.
Kai
+1  A: 

What? Not a clear answer? Numbers

Nick D
That's clear indeed. I'll change my statement to "not easily Googled", since the word "maximum" doesn't appear anywhere on that page.
Kai
Ok :) -
Nick D
+5  A: 

Although tydok's reference to PiL 2.3 is both correct and apropos, and Javier's answer is in practice correct, I thought the discussion of numbers in Lua should be rounded out with a couple of other details.

The Lua interpreter is designed to be embedded in an application typically as a configuration and/or scripting language. When built for an application, it is common to configure some of its features to suit.

The exact numeric type to use for numbers is available for configuration. When compiling for a platform without hardware floating point where loading third-party modules is not important (especially in an embedded system or set-top box game console application) then it is reasonable to pick an integral type instead of the default double. Occasionally, switching to float is reasonable also.

However, there are applications where 64-bit integers are needed, or most numbers can be integers but occasional floating point arithmetic is required. For those cases, there is the LNUM patch to the Lua core.

LNUM changes the core so that numbers are stored as either integers or floating point, and allows several configurable selections for the precision of each.

So the bottom line answer to the question of the maximum value of a Lua number is that it depends on the configuration of the interpreter chosen at compile time, and whether you are worried about the maximum magnitude representable or the maximum integer. And even then, work has been done to make large integers play well with floating point representations.

RBerteig
LNUM is great, both for speed on non-FPU processors (some ARMs go there), and for those rare occasions you really need 64-bit integer math.
Javier