Go to file
2000-05-15 16:30:41 -03:00
bugs first element in a list constructor is not adjusted to one value. 2000-05-12 15:12:04 -03:00
lapi.c details 2000-05-08 17:49:05 -03:00
lapi.h details 2000-05-08 17:49:05 -03:00
lauxlib.c new names for debug types 2000-03-30 14:19:48 -03:00
lauxlib.h details 1999-12-29 14:24:03 -02:00
lbuffer.c many details (most by lhf). 2000-03-03 11:58:26 -03:00
lbuiltin.c defines for _ERRORMESSAGE and _ALERT 2000-05-09 11:50:16 -03:00
lbuiltin.h global variables are stored in a Lua table 2000-05-08 16:32:53 -03:00
lcode.c global variables are stored in a Lua table 2000-05-08 16:32:53 -03:00
lcode.h comment 2000-04-12 15:47:03 -03:00
ldblib.c `getinfo' gets information about non-active functions, too. 2000-05-12 16:49:18 -03:00
ldebug.c cannot change value of private locals (used to implement `for') 2000-05-15 16:30:41 -03:00
ldebug.h Auxiliary functions from Debug Interface module 2000-01-14 15:15:44 -02:00
ldo.c defines for _ERRORMESSAGE and _ALERT 2000-05-09 11:50:16 -03:00
ldo.h code redistribution 2000-04-14 15:12:35 -03:00
lfunc.c no more special cases for closures with 0 upvalues (performance is the same, 2000-03-29 17:19:20 -03:00
lfunc.h some name changes 2000-03-10 15:37:44 -03:00
lgc.c details 2000-05-11 15:57:19 -03:00
lgc.h first implementation of multiple states (reentrant code). 1999-11-22 11:12:07 -02:00
linit.c `lua_setfallback' leaves things on the stack, so it is better to protect 1999-12-06 09:43:09 -02:00
liolib.c defines for _ERRORMESSAGE and _ALERT 2000-05-09 11:50:16 -03:00
llex.c global variables are stored in a Lua table 2000-05-08 16:32:53 -03:00
llex.h first implementation of FOR 2000-04-12 15:57:19 -03:00
llimits.h IntPoint does not need L 2000-04-26 10:43:25 -03:00
lmathlib.c some name changes 2000-03-10 15:37:44 -03:00
lmem.c more information about memory use 2000-03-16 17:35:07 -03:00
lmem.h more information about memory use 2000-03-16 17:35:07 -03:00
lobject.c "conceptual" bug 2000-04-26 10:43:10 -03:00
lobject.h string hash uses one single hash table 2000-05-10 13:33:20 -03:00
lopcodes.h [C++ Warning]: W8084 Suggest parentheses to clarify precedence. 2000-04-27 14:39:15 -03:00
lparser.c first element in a list constructor is not adjusted to one value. 2000-05-12 15:12:04 -03:00
lparser.h new optimization: jumps to jumps 2000-04-06 14:36:52 -03:00
lref.c no more special cases for closures with 0 upvalues (performance is the same, 2000-03-29 17:19:20 -03:00
lref.h small changes for "clean C" 2000-02-08 14:39:42 -02:00
lstate.c global variables are stored in a Lua table 2000-05-08 16:32:53 -03:00
lstate.h string hash uses one single hash table 2000-05-10 13:33:20 -03:00
lstring.c string hash uses one single hash table 2000-05-10 13:33:20 -03:00
lstring.h string hash uses one single hash table 2000-05-10 13:33:20 -03:00
lstrlib.c BUG: `strfind' gets wrong subject length when there is an offset 2000-05-02 15:32:22 -03:00
ltable.c details 2000-05-11 15:57:19 -03:00
ltable.h global variables are stored in a Lua table 2000-05-08 16:32:53 -03:00
ltests.c string hash uses one single hash table 2000-05-10 13:33:20 -03:00
ltm.c `luaT_validevent' is exported, because compatibility module for fallbacks 2000-03-30 13:41:51 -03:00
ltm.h `luaT_validevent' is exported, because compatibility module for fallbacks 2000-03-30 13:41:51 -03:00
lua.c new option `-c' to close lua. 2000-05-10 14:00:21 -03:00
lua.h missing define for `lua_dobuffer' single-state 2000-05-10 13:35:18 -03:00
luadebug.h new names for debug types 2000-03-30 14:19:48 -03:00
lualib.h first implementation of multiple states (reentrant code). 1999-11-22 11:12:07 -02:00
lundump.c global variables are stored in a Lua table 2000-05-08 16:32:53 -03:00
lundump.h final version (by lhf) 2000-04-25 13:44:31 -03:00
lvm.c global variables are stored in a Lua table 2000-05-08 16:32:53 -03:00
lvm.h global variables are stored in a Lua table 2000-05-08 16:32:53 -03:00
lzio.c many details (most by lhf). 2000-03-03 11:58:26 -03:00
lzio.h "const" !!! 1999-08-16 17:52:00 -03:00
makefile more uniform names 2000-04-24 18:05:11 -03:00
manual.tex `getinfo' gets information about non-active functions, too. 2000-05-12 16:49:18 -03:00