lua-l archive

[Date Index] [Thread Index]

• April 01, 2019
  • Cross-compiling Lua byte code for specific target hardware, Matthias
  • Re: Cross-compiling Lua byte code for specific target hardware, Luiz Henrique de Figueiredo
  • A tutorial on turning a C structure into a Lua table, Farzad Sadeghi
  • Re: Cross-compiling Lua byte code for specific target hardware, Bogdan Marinescu
  • Re: Cross-compiling Lua byte code for specific target hardware, Russell Haley
  • Re: OP_CLOSE reintroduction, Roberto Ierusalimschy
  • Fwd: the functionality of the language and documentation, z x
  • Unicode 0x110000 is the Lua logo, Dirk Laurie
  • Re: Unicode 0x110000 is the Lua logo, Enrico Colombini
  • A proposal for arrays, Dibyendu Majumdar
  • Re: A proposal for arrays, Luiz Henrique de Figueiredo
  • Re: OP_CLOSE reintroduction, Dibyendu Majumdar
  • Re: A tutorial on turning a C structure into a Lua table, Sean Conner
  • Re: A tutorial on turning a C structure into a Lua table, Sean Conner
  • Re: A tutorial on turning a C structure into a Lua table, Jonathan Goble
  • Re: Cross-compiling Lua byte code for specific target hardware, Egor Skriptunoff
  • new Lua Discord server, Dennis Fischer
  • Lua Discord server, skid man
  • Re: Lua Discord server, joy mondal
• April 02, 2019
  • Re: Unicode 0x110000 is the Lua logo, Ką Mykolas
  • Re: the functionality of the language and documentation, Ilya Shchukin
  • Energy Benchmarks, Italo Maia
  • Re: Lua Discord server, Rob Kendrick
  • Re: Energy Benchmarks, Dirk Laurie
  • Re: Energy Benchmarks, Frank Kastenholz
  • Re: the functionality of the language and documentation, Frank Kastenholz
  • Re: Energy Benchmarks, Scott Morgan
  • Re: Energy Benchmarks, Peter Hickman
  • luaO_chunkid - supply string size as parameter instead of calling strlen(), Ivan-Assen Ivanov
  • Re: Energy Benchmarks, Hugo Musso Gualandi
  • Re: Unicode 0x110000 is the Lua logo, Philippe Verdy
  • Re: Lua Discord server, Ką Mykolas
  • Elegant design for creating error messages in LPEG parser, joy mondal
  • Re: A tutorial on turning a C structure into a Lua table, Farzad Sadeghi
  • Re: Elegant design for creating error messages in LPEG parser, Sean Conner
  • Re: luaO_chunkid - supply string size as parameter instead of calling strlen(), Roberto Ierusalimschy
  • RE: luaO_chunkid - supply string size as parameter instead of calling strlen(), Patrick Dorion
  • Re: Elegant design for creating error messages in LPEG parser, Hugo Musso Gualandi
• April 03, 2019
  • Is this a wrong test?, 最萌 小汐
  • 答复: Is this a wrong test?, 最萌 小汐
  • Re: Is this a wrong test?, Dirk Laurie
  • Re: Is this a wrong test?, Roberto Ierusalimschy
  • LuaRocks build problem with luacom, Simon Orde
  • Re: Elegant design for creating error messages in LPEG parser, joy mondal
  • Re: Elegant design for creating error messages in LPEG parser, Sean Conner
  • Re: Elegant design for creating error messages in LPEG parser, joy mondal
  • lpeg.cut? (Re: Elegant design for creating error messages in LPEG parser), nobody
  • Fun math puzzle: cin(X), Albert Chan
  • Re: lpeg.cut? (Re: Elegant design for creating error messages in LPEG parser), joy mondal
• April 04, 2019
  • Re: Elegant design for creating error messages in LPEG parser, Sean Conner
  • Re: Elegant design for creating error messages in LPEG parser, joy mondal
  • Re: Elegant design for creating error messages in LPEG parser, Sean Conner
  • Re: lpeg.cut? (Re: Elegant design for creating error messages in LPEG parser), Sean Conner
  • Re: Energy Benchmarks, Egor Skriptunoff
  • Re: lpeg.cut? (Re: Elegant design for creating error messages in LPEG parser), Philipp Janda
  • Re: Energy Benchmarks, joy mondal
  • Re: Energy Benchmarks, Enrico Colombini
  • Re: Fun math puzzle: cin(X), Dirk Laurie
  • Re: Energy Benchmarks, Frank Kastenholz
  • Re: Energy Benchmarks, Scott Morgan
  • Re: Fun math puzzle: cin(X), Albert Chan
  • Re: LuaRocks build problem with luacom, Thijs Schreijer
  • Re: Elegant design for creating error messages in LPEG parser, Soni "They/Them" L.
  • Re: Fun math puzzle: cin(X), Egor Skriptunoff
  • lua-test failure help on Vxworks 7?, Kuhl, Brian
  • Re: Fun math puzzle: cin(X), Albert Chan
  • Re: Fun math puzzle: cin(X), Tim Hill
• April 05, 2019
  • Re: Fun math puzzle: cin(X), Philippe Verdy
  • Re: Fun math puzzle: cin(X), Albert Chan
  • Re: Fun math puzzle: cin(X), Rodrigo Azevedo
  • Re: Fun math puzzle: cin(X), Albert Chan
  • New feature for lua, Sergey Kovalev
  • Re: New feature for lua, Egor Skriptunoff
  • Re: New feature for lua, steve donovan
  • Re: New feature for lua, Roberto Ierusalimschy
  • Re: lua-l Digest, Vol 105, Issue 12, Sergey Kovalev
  • Re: New feature for lua, Sean Conner
  • Re: lua-l Digest, Vol 105, Issue 12, Sean Conner
• April 06, 2019
  • Re: Fun math puzzle: cin(X), Dirk Laurie
  • Re: Energy Benchmarks, Italo Maia
  • Re: Fun math puzzle: cin(X), Albert Chan
  • Re: Fun math puzzle: cin(X), Albert Chan
  • Installing lcomplex on Lua 5.3, Aditya Mahajan
  • Re: Installing lcomplex on Lua 5.3, Luiz Henrique de Figueiredo
  • Installing lcomplex on Lua 5.3, Aditya Mahajan
  • Re: Installing lcomplex on Lua 5.3, Aditya Mahajan
• April 07, 2019
  • A question of style for C module writers, Marc Balmer
  • Re: A question of style for C module writers, Charles Heywood
  • Re: A question of style for C module writers, Sean Conner
  • Re: A question of style for C module writers, Philipp Janda
  • Modifying strings returned by luaL_checkstring()?, Marc Balmer
  • When will userdate be freed/gced?, Marc Balmer
  • Making a modifiable copy of a string in C, Marc Balmer
  • Re: Making a modifiable copy of a string in C, Viacheslav Usov
  • Re: Modifying strings returned by luaL_checkstring()?, Andrew Gierth
  • Re: Making a modifiable copy of a string in C, Marc Balmer
  • Re: When will userdate be freed/gced?, Andrew Gierth
  • Re: Making a modifiable copy of a string in C, Andrew Gierth
  • Re: When will userdate be freed/gced?, Marc Balmer
  • Re: Making a modifiable copy of a string in C, Andrew Gierth
  • Re: When will userdate be freed/gced?, Andrew Gierth
  • Re: Making a modifiable copy of a string in C, Marc Balmer
  • Re: Making a modifiable copy of a string in C, Viacheslav Usov
  • RE: LuaRocks build problem with luacom, Simon Orde
  • Re: lua-l Digest, Vol 105, Issue 13, Sergey Kovalev
  • Re: lua-l Digest, Vol 105, Issue 13, Jonathan Goble
  • Re: lua-l Digest, Vol 105, Issue 13, Dirk Laurie
  • C module compatibility, Antonin Décimo
  • Re: C module compatibility, Andrew Gierth
  • lpeg: bug or intentional? `… * (Cmt(0,f1) + Cmt(0,f2)) * …` doesn't call f2, nobody
  • Re: Energy Benchmarks, joy mondal
• April 08, 2019
  • Re: lpeg: bug or intentional? `… * (Cmt(0,f1) + Cmt(0,f2)) * …` doesn't call f2, Sean Conner
  • Re: Making a modifiable copy of a string in C, Sean Conner
  • Re: Elegant design for creating error messages in LPEG parser, joy mondal
  • Re: Elegant design for creating error messages in LPEG parser, Dirk Laurie
  • Re: Elegant design for creating error messages in LPEG parser, Sean Conner
  • Re: Elegant design for creating error messages in LPEG parser, Sean Conner
  • Re: Energy Benchmarks, Italo Maia
  • Re: Energy Benchmarks, steve donovan
  • Re: Installing lcomplex on Lua 5.3, Luiz Henrique de Figueiredo
  • Re: Installing lcomplex on Lua 5.3, Thijs Schreijer
  • Re: Installing lcomplex on Lua 5.3, Thijs Schreijer
  • Re: Installing lcomplex on Lua 5.3, Eduardo Barthel
  • Numbers are buggy?, Soni "They/Them" L.
  • Re: Making a modifiable copy of a string in C, Gé Weijers
  • Re: Numbers are buggy?, Soni "They/Them" L.
  • Re: lua-test failure help on Vxworks 7?, Roberto Ierusalimschy
  • Re: Numbers are buggy?, Luiz Henrique de Figueiredo
  • Re: Modifying strings returned by luaL_checkstring()?, Gé Weijers
  • Re: Numbers are buggy?, Soni "They/Them" L.
  • Shuttle -- Lua launcher, Chris Smith
  • Re: Numbers are buggy?, Roberto Ierusalimschy
  • Re: lpeg.cut? (Re: Elegant design for creating error messages in LPEG parser), Sérgio Medeiros
  • Re: C module compatibility, Tomás Guisasola
  • RE: lua-test failure help on Vxworks 7?, Kuhl, Brian
  • Re: lpeg: bug or intentional? `… * (Cmt(0,f1) + Cmt(0,f2)) * …` doesn't call f2, nobody
  • Re: Elegant design for creating error messages in LPEG parser, joy mondal
  • Re: Quickly processing "Lua" files, Egor Skriptunoff
  • Re: Fun math puzzle: cin(X), Albert Chan
  • Re: C module compatibility, Antonin Décimo
  • Re: C module compatibility, Andrew Gierth
• April 09, 2019
  • Re: C module compatibility, Luiz Henrique de Figueiredo
  • Re: Fun math puzzle: cin(X), Dirk Laurie
  • Re: Installing lcomplex on Lua 5.3, Hisham
  • Re: Installing lcomplex on Lua 5.3, Eduardo Barthel
  • update: I wrote my own pure-Lua Lua parser thingy (sort of), Soni "They/Them" L.
  • Re: Fun math puzzle: cin(X), Egor Skriptunoff
• April 10, 2019
  • Re: Fun math puzzle: cin(X), Albert Chan
  • Lua state lifetime, Fotis Panagiotopoulos
  • load and upvalues, Dennis Fischer
  • Re: Lua state lifetime, Ką Mykolas
  • Re: Lua state lifetime, Fotis Panagiotopoulos
  • Re: Lua state lifetime, Luiz Henrique de Figueiredo
  • Re: Lua state lifetime, Fotis Panagiotopoulos
  • Throwing an error within a __gc metamethod, Fotis Panagiotopoulos
  • Re: load and upvalues, Dirk Laurie
  • Re: Throwing an error within a __gc metamethod, Roberto Ierusalimschy
  • Re: Lua state lifetime, Roberto Ierusalimschy
  • Re: Lua state lifetime, Fotis Panagiotopoulos
• April 11, 2019
  • Unexplained object deletion when using lpeg.Cc with lpeg.Cmt, joy mondal
  • luac.c missing in the github repo, Andrei Alexeyev
  • Re: luac.c missing in the github repo, Jonathan Goble
  • Re: Unexplained object deletion when using lpeg.Cc with lpeg.Cmt, Sean Conner
  • Re: Unexplained object deletion when using lpeg.Cc with lpeg.Cmt, joy mondal
  • Re: Unexplained object deletion when using lpeg.Cc with lpeg.Cmt, joy mondal
  • Re: Unexplained object deletion when using lpeg.Cc with lpeg.Cmt, Dirk Laurie
  • Re: luac.c missing in the github repo, Charles Heywood
  • Garbage collection causes stack overflow, Fotis Panagiotopoulos
  • Re: Garbage collection causes stack overflow, Roberto Ierusalimschy
  • Re: Garbage collection causes stack overflow, Fotis Panagiotopoulos
  • Re: Garbage collection causes stack overflow, Roberto Ierusalimschy
  • Re: lua-test failure help on Vxworks 7?, Roberto Ierusalimschy
  • Re: Unexplained object deletion when using lpeg.Cc with lpeg.Cmt, joy mondal
  • Re: Garbage collection causes stack overflow, Fotis Panagiotopoulos
  • Re: Garbage collection causes stack overflow, Roberto Ierusalimschy
• April 12, 2019
  • Lua on GPU?, Jon Chesterfield
  • Re: Garbage collection causes stack overflow, Enrico Colombini
  • Re: Garbage collection causes stack overflow, Ką Mykolas
  • string.bytes, Dirk Laurie
  • Re: string.bytes, Javier Guerra Giraldez
  • Non-uniqueness of module names, Dirk Laurie
  • Re: Non-uniqueness of module names, Dibyendu Majumdar
  • Re: Non-uniqueness of module names, Roberto Ierusalimschy
  • Re: Non-uniqueness of module names, Abhijit Nandy
  • Re: Non-uniqueness of module names, Luiz Henrique de Figueiredo
  • Re: Non-uniqueness of module names, Dirk Laurie
  • -Wstring-plus-int warning when building Lua with clang, Michał Górny
  • Re: Non-uniqueness of module names, Sean Conner
  • Re: Non-uniqueness of module names, Sean Conner
  • Re: Non-uniqueness of module names, Dirk Laurie
  • Re: Non-uniqueness of module names, Sean Conner
  • Re: Non-uniqueness of module names, Gabriel Bertilson
• April 13, 2019
  • Re: string.bytes, Dennis Fischer
• April 14, 2019
  • Re: Installing lcomplex on Lua 5.3, Aditya Mahajan
  • custom interpreters and modules in zip files, Jim
  • reference counting, Jim
  • Re: Non-uniqueness of module names, Jim
  • Re: custom interpreters and modules in zip files, Sean Conner
  • Re: reference counting, Sean Conner
  • Re: Non-uniqueness of module names, Sean Conner
• April 15, 2019
  • Re: Non-uniqueness of module names, Dirk Laurie
  • Re: Non-uniqueness of module names, Roberto Ierusalimschy
  • luasqL -- iterator from manual does not work -- cursor still open, douglas mcallaster
  • Re: luasqL -- iterator from manual does not work -- cursor still open, Tomás Guisasola
  • Re: Non-uniqueness of module names, Gerhard Sittig
  • Re: Non-uniqueness of module names, Luiz Henrique de Figueiredo
  • Re: reference counting, Gé Weijers
  • Re: Garbage collection causes stack overflow, Fotis Panagiotopoulos
  • environment variables as modules, Soni "They/Them" L.
  • Re: Non-uniqueness of module names, Sean Conner
  • Re: environment variables as modules, Sean Conner
  • Re: Non-uniqueness of module names, Sean Conner
  • Re: Non-uniqueness of module names, Soni "They/Them" L.
• April 16, 2019
  • Re: reference counting, 云风 Cloud Wu
  • Re: Non-uniqueness of module names, Thijs Schreijer
  • Re: Non-uniqueness of module names, Dirk Laurie
  • Re: reference counting, Jim
  • Re: Non-uniqueness of module names, Dirk Laurie
  • Re: reference counting, Gé Weijers
  • Re: reference counting, 云风 Cloud Wu
  • Re: reference counting, Coda Highland
  • [ANN] LuaSec 0.8 release, Bruno Silvestre
  • Re: Non-uniqueness of module names, Roberto Ierusalimschy
• April 17, 2019
  • Re: Non-uniqueness of module names, Fabio Mascarenhas
  • Re: Non-uniqueness of module names, Fabio Mascarenhas
• April 18, 2019
  • Re: Non-uniqueness of module names, Dennis Fischer
  • X.509 PKIX certificate parser using lpeg.Cmt (was Re: Elegant design for creating error messages in LPEG parser), William Ahern
  • Re: reference counting, Jim
  • Re: Non-uniqueness of module names, Dirk Laurie
  • Re: Non-uniqueness of module names, Hisham
  • Re: Non-uniqueness of module names, Dirk Laurie
  • Re: Non-uniqueness of module names, Peter Aronoff
• April 19, 2019
  • Re: Non-uniqueness of module names, Dirk Laurie
  • Re: Non-uniqueness of module names, Mitchell
  • Light User Data value changed, Milind Gupta
  • Re: Light User Data value changed, Jonathan Goble
  • Re: Light User Data value changed, Albert Chan
  • Re: Light User Data value changed, Milind Gupta
• April 20, 2019
  • Re: Light User Data value changed, Tim Hill
  • (no subject), Haoran Wang
  • Re: Non-uniqueness of module names, Tim Hill
  • Re: Non-uniqueness of module names, Sean Conner
  • Re: Non-uniqueness of module names, Coda Highland
  • Re: Non-uniqueness of module names, Sean Conner
  • Re: Non-uniqueness of module names, Parke
• April 21, 2019
  • Re: Non-uniqueness of module names, Sean Conner
  • Re: Non-uniqueness of module names, Coda Highland
  • Re: Non-uniqueness of module names, Roberto Ierusalimschy
  • Re: Non-uniqueness of module names, Soni "They/Them" L.
  • Bug in Lua 5.3? (was Re: Non-uniqueness of module names), Sean Conner
  • Re: Bug in Lua 5.3? (was Re: Non-uniqueness of module names), Sean Conner
  • How to branch both ways?, nobody
  • Re: How to branch both ways?, Sean Conner
  • Re: Bug in Lua 5.3? (was Re: Non-uniqueness of module names), Coda Highland
  • Re: Bug in Lua 5.3? (was Re: Non-uniqueness of module names), Sean Conner
• April 22, 2019
  • Modulo with negative operands, Albert Chan
  • Re: Modulo with negative operands, Dirk Laurie
• April 24, 2019
  • [ANN] Quaternion rotation library, Dirk Laurie
  • Scoped variable *toclose syntax, Dibyendu Majumdar
• April 25, 2019
  • Re: Scoped variable *toclose syntax, Philippe Verdy
  • Re: Scoped variable *toclose syntax, Dirk Laurie
  • Re: Scoped variable *toclose syntax, Dibyendu Majumdar
  • Re: Scoped variable *toclose syntax, Roberto Ierusalimschy
  • Re: Scoped variable *toclose syntax, Dibyendu Majumdar
  • Re: Scoped variable *toclose syntax, Dibyendu Majumdar
  • Re: Scoped variable *toclose syntax, Dibyendu Majumdar
  • Re: Scoped variable *toclose syntax, Sean Conner
  • Re: Scoped variable *toclose syntax, Tim Hill
  • Re: Scoped variable *toclose syntax, Dibyendu Majumdar
  • Re: Scoped variable *toclose syntax, Dibyendu Majumdar
  • Re: Scoped variable *toclose syntax, Diego Nehab
  • Re: Scoped variable *toclose syntax, Dibyendu Majumdar
  • Re: Scoped variable *toclose syntax, Egor Skriptunoff
  • *toclose and custom stack traces, nobody
  • Re: Scoped variable *toclose syntax, Roberto Ierusalimschy
  • Re: Scoped variable *toclose syntax, Sean Conner
  • Re: Scoped variable *toclose syntax, Dibyendu Majumdar
  • Re: Scoped variable *toclose syntax, Philippe Verdy
  • Re: Scoped variable *toclose syntax, Philippe Verdy
• April 26, 2019
  • confused about root-trace link in LuaJIT, twey seo
  • About the annotation, kurapica
  • Re: About the annotation, kurapica
  • Re: Scoped variable *toclose syntax, Lorenzo Donati
• April 28, 2019
  • finite state machine in lua, Srinivas Murthy
  • Re: finite state machine in lua, Sean Conner
• April 29, 2019
  • Re: finite state machine in lua, Jorge
  • Re: finite state machine in lua, Soni "They/Them" L.
  • Re: finite state machine in lua, Srinivas Murthy
  • Re: finite state machine in lua, Jorge
• April 30, 2019
  • [ANN] LuaRocks 3.1.0, Hisham
  • lua-http https failures on Ubuntu 18, Russell Haley
  • Re: [ANN] LuaRocks 3.1.0, Russell Haley
  • Re: [ANN] LuaRocks 3.1.0, Andrew Gierth
  • Re: [ANN] LuaRocks 3.1.0, Russell Haley

---

Mail converted by MHonArc 2.6.19