[Date Index]
[Thread Index]
- Re: To-be-closed variables and coroutines, Viacheslav Usov
- Lua 5.4.0 patch 2 causes C stackoverflow, Vinicius Jarina
- [ANN] Update to sig_catch power patch, Reuben Thomas
- Usage of -Os in 5.4 causing issues, Daniel Kolesa
- Re: Lua 5.4.0 manual, rexonf
- [ANN] Penlight 1.8.0 released, Thijs Schreijer
- Re: Dogfood released; an alternative for creating 'self running' Lua programs, Marc Balmer
- [ANN] lrexlib 2.9.1 released, rrt
- SipHash for Lua 5.1.5 patch, lua
- SipHash for Lua 5.4.0 patch, Sam Trenholme
- Are there some potential problems if I use a self-defined memory acquirement function instead of realloc(3) in the l_alloc function?, 孙世龙 sunshilong
- Re: Are there some potential problems if I use a self-defined memory acquirement function instead of realloc(3) in the l_alloc function?, Stefan
- Re: Are there some potential problems if I use a self-defined memory acquirement function instead of realloc(3) in the l_alloc function?, Viacheslav Usov
- Re: Are there some potential problems if I use a self-defined memory acquirement function instead of realloc(3) in the l_alloc function?, Roberto Ierusalimschy
- Re: Are there some potential problems if I use a self-defined memory acquirement function instead of realloc(3) in the l_alloc function?, Stefan
- Re: Are there some potential problems if I use a self-defined memory acquirement function instead of realloc(3) in the l_alloc function?, Roberto Ierusalimschy
- Re: Are there some potential problems if I use a self-defined memory acquirement function instead of realloc(3) in the l_alloc function?, Philippe Verdy
- Re: Are there some potential problems if I use a self-defined memory acquirement function instead of realloc(3) in the l_alloc function?, Andrew Gierth
- Re: Are there some potential problems if I use a self-defined memory acquirement function instead of realloc(3) in the l_alloc function?, 孙世龙 sunshilong
- Re: Are there some potential problems if I use a self-defined memory acquirement function instead of realloc(3) in the l_alloc function?, Sean Conner
- Re: Are there some potential problems if I use a self-defined memory acquirement function instead of realloc(3) in the l_alloc function?, 孙世龙 sunshilong
- Re: Are there some potential problems if I use a self-defined memory acquirement function instead of realloc(3) in the l_alloc function?, Sean Conner
- Re: Are there some potential problems if I use a self-defined memory acquirement function instead of realloc(3) in the l_alloc function?, Andrew Gierth
- Re: Are there some potential problems if I use a self-defined memory acquirement function instead of realloc(3) in the l_alloc function?, 孙世龙 sunshilong
- Re: Are there some potential problems if I use a self-defined memory acquirement function instead of realloc(3) in the l_alloc function?, Andrew Gierth
- Re: Are there some potential problems if I use a self-defined memory acquirement function instead of realloc(3) in the l_alloc function?, 孙世龙 sunshilong
- Re: Are there some potential problems if I use a self-defined memory acquirement function instead of realloc(3) in the l_alloc function?, Gerhard Sittig
- Re: Are there some potential problems if I use a self-defined memory acquirement function instead of realloc(3) in the l_alloc function?, Philippe Verdy
- Re: Are there some potential problems if I use a self-defined memory acquirement function instead of realloc(3) in the l_alloc function?, 孙世龙 sunshilong
- Re: Are there some potential problems if I use a self-defined memory acquirement function instead of realloc(3) in the l_alloc function?, Philippe Verdy
- Re: Are there some potential problems if I use a self-defined memory acquirement function instead of realloc(3) in the l_alloc function?, Andrew Gierth
- Re: Are there some potential problems if I use a self-defined memory acquirement function instead of realloc(3) in the l_alloc function?, 孙世龙 sunshilong
- Re: Are there some potential problems if I use a self-defined memory acquirement function instead of realloc(3) in the l_alloc function?, 孙世龙 sunshilong
- Use a self-defined memory acquirement function instead of realloc(3) in the l_alloc function, 孙世龙 sunshilong
- Lua & lock manager, Thierry Fournier
- SipHash benchmarks: I will use HalfSipHash31, Sam Trenholme
- [ANN] lualogging release 1.4.0, Thijs Schreijer
- godawful sh/Lua polyglot, Norman Ramsey
- What problems may occur if the restriction(i.e. l_alloc should not fail when shrinking the block) is broken?, 孙世龙 sunshilong
- Since the input argument named osize has not been used in the l_alloc() function, why still pass LUA_TTHREAD to this function in lua_newstate()?, 孙世龙 sunshilong
- Parallelizing a busted test suite, Hugo Musso Gualandi
- loadStringN can write to freed memory, will fail assert in tests, Payo Nel
- Serializable VM, Egor Skriptunoff
- No way to get uservalue count from API; intended?, Sergey Zakharchenko
- C stack overflow in Lua 5.4 in ackermann benchmark, Eduardo Bart
- Crash in tostringbuff when -D_FORTIFY_SOURCE=2 is not defined in Lua 5.4, Eduardo Bart
- Re: Crash in tostringbuff when -D_FORTIFY_SOURCE=2 is not defined in Lua 5.4, Eduardo Bart
- Re: Crash in tostringbuff when -D_FORTIFY_SOURCE=2 is not defined in Lua 5.4, Luiz Henrique de Figueiredo
- Re: Crash in tostringbuff when -D_FORTIFY_SOURCE=2 is not defined in Lua 5.4, Eduardo Bart
- Re: Crash in tostringbuff when -D_FORTIFY_SOURCE=2 is not defined in Lua 5.4, Eduardo Bart
- Re: Crash in tostringbuff when -D_FORTIFY_SOURCE=2 is not defined in Lua 5.4, Eduardo Bart
- Re: Crash in tostringbuff when -D_FORTIFY_SOURCE=2 is not defined in Lua 5.4, Roberto Ierusalimschy
- Re: Crash in tostringbuff when -D_FORTIFY_SOURCE=2 is not defined in Lua 5.4, Philippe Verdy
- Re: Crash in tostringbuff when -D_FORTIFY_SOURCE=2 is not defined in Lua 5.4, Andrew Gierth
- Re: Crash in tostringbuff when -D_FORTIFY_SOURCE=2 is not defined in Lua 5.4, Philippe Verdy
- Re: Crash in tostringbuff when -D_FORTIFY_SOURCE=2 is not defined in Lua 5.4, Philippe Verdy
- Re: Crash in tostringbuff when -D_FORTIFY_SOURCE=2 is not defined in Lua 5.4, Philippe Verdy
- Re: Crash in tostringbuff when -D_FORTIFY_SOURCE=2 is not defined in Lua 5.4, Philippe Verdy
- Re: Crash in tostringbuff when -D_FORTIFY_SOURCE=2 is not defined in Lua 5.4, Sam Trenholme
- Re: Crash in tostringbuff when -D_FORTIFY_SOURCE=2 is not defined in Lua 5.4, Philippe Verdy
- Re: Crash in tostringbuff when -D_FORTIFY_SOURCE=2 is not defined in Lua 5.4, Ranier Vilela
- Re: Crash in tostringbuff when -D_FORTIFY_SOURCE=2 is not defined in Lua 5.4, Philippe Verdy
- Re: Crash in tostringbuff when -D_FORTIFY_SOURCE=2 is not defined in Lua 5.4, Philippe Verdy
- Re: Crash in tostringbuff when -D_FORTIFY_SOURCE=2 is not defined in Lua 5.4, Andrew Gierth
- Programming In Lua, Russell Haley
- Metatable check helper API proposal, Sergey Zakharchenko
- Lua 5.4 local attribute syntax whitespace sensitivity, Sergey Zakharchenko
- Lua application programming (Big message), Joao Von
- [bug?] No readline support in Lua 5.4 REPL, Martin
- Squeezing more performance from the Lua interpreter, Eduardo Bart
- [ANN] Luacheck 0.24.0, Hisham
- [ANN] luacov/cluacov support for Lua 5.4, Hisham
- Strange way to determine whether it is Lua or C function, Egor Skriptunoff
- Question about luaH_newkey, 重归混沌
- luaclose_mylib function (inverse of "luaopen_mylib" C function), bel
- Job: Lua programmer for satellite/IoT project, Bogdan Marinescu
- Do strings move around?, Francisco Olarte
- Dogfood v1.0.2 has been released; an alternative for building self contained Lua executables, Jasper Klein
- Minor correctness issue with l_str2d's use of ltolower, Ahmed Charles
- Memory corruption in in luaV_execute (lua/Test_lua/lua/lvm.c:1784), secwx weizhenvul
Mail converted by MHonArc 2.6.19
