File di log originale · 20130228-3533.txt
------------------------------------------------------------------------
r3533 | helixhorned | 2013-02-28 09:30:15 -0800 (Thu, 28 Feb 2013) | 1 line
Lunatic t.: {read,save}gamevar, fix break in nested while, fix rotatesprite16.
------------------------------------------------------------------------
r3532 | helixhorned | 2013-02-28 09:30:11 -0800 (Thu, 28 Feb 2013) | 3 lines
build.c: initialize g_doHardcodedMovement to 1.
Fixing movement when not loading a.m32.
------------------------------------------------------------------------
r3531 | helixhorned | 2013-02-28 09:30:08 -0800 (Thu, 28 Feb 2013) | 1 line
scriplib: attach const qualifiers to appropriate function input arguments.
------------------------------------------------------------------------
r3530 | helixhorned | 2013-02-28 09:30:04 -0800 (Thu, 28 Feb 2013) | 12 lines
Lunatic: fixups and debugging helpers.
- add LuaJIT's 'v' module printing trace info
- translator: fix game function name definitions
- revert math.fmod -> math.modf, they are different!
- disable JIT compilation for a function we're getting strange crashes with
- Make some of DukePlayer_t's members 'bool' on the Lua side. It's way
too easy to write something like "ps.jetpack_on" where "ps.jetpack_on~=0"
was meant. [Background: Kyle873 observed that Duke was always floating.]
- Error out if looping in our_module(). I find this behavior more logical
than returning true.
- fix a couple of missed FORBID variables
------------------------------------------------------------------------
build.c: initialize g_doHardcodedMovement to 1.
Fixing movement when not loading a.m32.
attach const qualifiers to appropriate function input arguments.
fixups and debugging helpers.
- add LuaJIT's 'v' module printing trace info - translator: fix game function name definitions - revert math.fmod -> math.modf, they are different! - disable JIT compilation for a function we're getting strange crashes with - Make some of DukePlayer_t's members 'bool' on the Lua side. It's way too easy to write something like "ps.jetpack_on" where "ps.jetpack_on~=0" was meant. [Background: Kyle873 observed that Duke was always floating.] - Error out if looping in our_module(). I find this behavior more logical than returning true. - fix a couple of missed FORBID variables