lua-users home
lua-l archive

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


On Sun, Mar 15, 2015 at 10:50 AM, Colin Hirsch <lua@colin-hirsch.net> wrote:
>> On 13 March 2015 at 16:21 Roberto Ierusalimschy <roberto@inf.puc-rio.br> wrote:
>>
>> > That does look interesting, although we’d have to check whether it
>> > is possible for us to switch to LuaJIT. The last time I looked at it
>> > that was not possible for lack of 64bit integer support (unfortunately
>> > Lua’s default numeric type “double” is not at all appropriate
>> > to our applications, and our Lua 5.1 is configured to use int64_t
>> > instead, something that Lua is well designed to handle). However it
>> > seems that in the meantime LuaJIT has gained support for some boxed
>> > 64bit integers, which might be good enough if well integrated…
>>
>> (Out of topic) Can you give a brief explanation about why you need
>> 64bit integer support? (I am writing something about the introduction
>> of integers in Lua 5.3, and it would be good to have some more concrete
>> examples of why people need 64bit integers.)
>
> On a related note, we are currently considering upgrading from Lua 5.1 to Lua 5.2, rather than 5.3, because we _only_ need 64bit
> integers, and 5.2 can be configured to use them exclusively, just like the 5.1 we are currently using.
>
> We will of course first look into whether the floating point part of 5.3 can be safely and easily ignored in our use cases; our
> concern is that the implicit conversion form integer to float might strike at inconvenient times...

Perhaps you may want to take a look at this [1] patch, which removes
floating-point numbers completely from 5.3.

[1] https://github.com/lneto/lua/tree/no-float
-- 
Lourival Vieira Neto