Fixed by lua-types branch.
** Changed in: tarantool
Status: New => Fix Committed
** Changed in: tarantool
Milestone: None => 1.5.1
** Changed in: tarantool
Assignee: (unassigned) => Roman Tsisyk (rtsisyk)
--
You received this bug notification because you are a member of Tarantool
Development Team, which is subscribed to tarantool.
https://bugs.launchpad.net/bugs/1180825
Title:
box/lua.test produces different output on x86 and x86_64
Status in Tarantool - an efficient in-memory data store:
Fix Committed
Bug description:
lua function f1() return 'testing', 1, false, -1, 1.123, 1e123, nil end
---
...
lua f1()
---
- testing
- 1
- false
- -1
- 1.123
- 1e+123
- nil
...
call f1()
Found 7 tuples:
['testing']
[1]
['false']
[4294967295]
[1]
[0]
['nil']
lua f1=nil
On Thu, May 16, 2013 at 4:57 PM, Mike Pall <[email protected]> wrote:
>
> To preserve ABI compatibility with Lua, lua_Integer has a
> different width on those platforms. [Which IMHO was a bad design
> decision to begin with, but I can't fix that.]
>
>> a = 1e+123
>
> Conversions for values outside of the range of lua_Integer will
> give undefined results. These may be platform-specific, too.
>
> --Mike
Please do not use floats like 1e+123 in tests.
To manage notifications about this bug go to:
https://bugs.launchpad.net/tarantool/+bug/1180825/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~tarantool-developers
Post to : [email protected]
Unsubscribe : https://launchpad.net/~tarantool-developers
More help : https://help.launchpad.net/ListHelp
