Mail Thread Index

[Date Index] [Thread Index]

• Re: Iterating pairs of keys from a table, Tim Hill
  • Re: Iterating pairs of keys from a table, Chris Berardi
  • <Possible follow-ups>
  • Re: Iterating pairs of keys from a table, Dirk Laurie
    • Re: Iterating pairs of keys from a table, Tim Hill
      • Re: Iterating pairs of keys from a table, Dirk Laurie
• Lua and composition, Soni L.
  • Re: Lua and composition, 云风 Cloud Wu
  • Re: Lua and composition, Charles Heywood
    • Re: Lua and composition, Soni L.
  • Re: Lua and composition, Dirk Laurie
    • Re: Lua and composition, Soni L.
      • Re: Lua and composition, Dirk Laurie
      • Re: Lua and composition, Soni L.
      • Re: Lua and composition, Dirk Laurie
    • Re: Lua and composition, Tim Hill
      • Re: Lua and composition, Dirk Laurie
      • Re: Lua and composition, Francisco Olarte
  • Re: Lua and composition, Petri Häkkinen
    • Re: Lua and composition, Dirk Laurie
      • Re: Lua and composition, Petri Häkkinen
      • Re: Lua and composition, Sean Conner
      • Re: Lua and composition, Petri Häkkinen
      • Re: Lua and composition, Soni L.
      • Re: Lua and composition, Petri Häkkinen
      • Re: Lua and composition, Martin
      • Re: Lua and composition, Michael Nelson
• Re: heap allocation time?, Daurnimator
  • Re: heap allocation time?, Tim Hill
• Re: Does Lua need a JIT?, Ahmed Charles
  • <Possible follow-ups>
  • Re: Does Lua need a JIT?, Luke Gorrie
    • Re: Does Lua need a JIT?, Dibyendu Majumdar
      • Re: Does Lua need a JIT?, Luke Gorrie
    • Re: Does Lua need a JIT?, Dirk Laurie
• Send Unit8, Hamed Taheri
  • Re: Send Unit8, Eric Man
• Re: Interesting article on hash table performance, Ahmed Charles
  • Re: Interesting article on hash table performance, Francisco Olarte
  • <Possible follow-ups>
  • Re: Interesting article on hash table performance, Russell Haley
• Women of the Lua community, Etiene Dalcol
  • Re: Women of the Lua community, Rain Gloom
  • Re: Women of the Lua community, Peter van Dijk
• Re: LUA_INIT can replace require, 彭 书呆
  • Re: LUA_INIT can replace require, Tony Papadimitriou
    • Re: LUA_INIT can replace require, 彭 书呆
      • Re: LUA_INIT can replace require, Soni L.
      • Re: LUA_INIT can replace require, Charles Heywood
      • Re: LUA_INIT can replace require, Soni L.
      • Re: LUA_INIT can replace require, nobody
      • Re: LUA_INIT can replace require, 彭 书呆
• Possible Hex Literal Parsing Bug, Michael Rosenberg
  • Re: Possible Hex Literal Parsing Bug, Las
    • Re: Possible Hex Literal Parsing Bug, Martin
      • Re: Possible Hex Literal Parsing Bug, Coda Highland
      • Re: Possible Hex Literal Parsing Bug, Dirk Laurie
      • Re: Possible Hex Literal Parsing Bug, Coda Highland
      • Re: Possible Hex Literal Parsing Bug, Tim Hill
      • Re: Possible Hex Literal Parsing Bug, Martin
      • Re: Possible Hex Literal Parsing Bug, Adrian Perez de Castro
      • Re: Possible Hex Literal Parsing Bug, Michael Rosenberg
      • Re: Possible Hex Literal Parsing Bug, Dirk Laurie
      • Re: Possible Hex Literal Parsing Bug, Michael Rosenberg
      • Re: Possible Hex Literal Parsing Bug, Coda Highland
      • Re: Possible Hex Literal Parsing Bug, Luiz Henrique de Figueiredo
• [ANN] Lua code formatter (lcf) updated, Martin
• [ANN] Lua in Moscow 2017 conference is this Sunday! Schedule and Saturday pre-party, Alexander Gladysh
• large allocation with 'io.read' function, op7ic \x00
  • Re: large allocation with 'io.read' function, Dirk Laurie
    • Re: large allocation with 'io.read' function, op7ic \x00
      • Re: large allocation with 'io.read' function, Ahmed Charles
      • Re: large allocation with 'io.read' function, Lorenzo Donati
      • Re: large allocation with 'io.read' function, Enrico Colombini
      • Re: large allocation with 'io.read' function, William Ahern
    • Re: large allocation with 'io.read' function, Roberto Ierusalimschy
• Possible "inconsistent" reference to gettable_event in reference manual, Lorenzo Donati
  • Re: Possible "inconsistent" reference to gettable_event in reference manual, Lorenzo Donati
    • Re: Possible "inconsistent" reference to gettable_event in reference manual, Lorenzo Donati
      • Re: Possible "inconsistent" reference to gettable_event in reference manual, Roberto Ierusalimschy
      • Re: Possible "inconsistent" reference to gettable_event in reference manual, Lorenzo Donati
• [ANN] Luacheck 0.19.0, Peter Melnichenko
  • Re: [ANN] Luacheck 0.19.0, Peter Aronoff
    • Re: [ANN] Luacheck 0.19.0, Francisco Olarte
    • Re: [ANN] Luacheck 0.19.0, Xavier Wang
    • Re: [ANN] Luacheck 0.19.0, Dirk Laurie
      • Re: [ANN] Luacheck 0.19.0, Peter Aronoff
    • Re: [ANN] Luacheck 0.19.0, Peter Melnichenko
      • Re: [ANN] Luacheck 0.19.0, Peter Aronoff
      • Re: [ANN] Luacheck 0.19.0, Peter Melnichenko
      • Re: [ANN] Luacheck 0.19.0, Dirk Laurie
      • Re: [ANN] Luacheck 0.19.0, Martin
      • Re: [ANN] Luacheck 0.19.0, Sean Conner
      • Re: [ANN] Luacheck 0.19.0, Peter Aronoff
      • Re: [ANN] Luacheck 0.19.0, Martin
      • Re: [ANN] Luacheck 0.19.0, Peter Melnichenko
      • Re: [ANN] Luacheck 0.19.0, Peter Aronoff
      • Re: [ANN] Luacheck 0.19.0, Dirk Laurie
      • Re: [ANN] Luacheck 0.19.0, Liam Devine
      • Re: [ANN] Luacheck 0.19.0, Dirk Laurie
  • Re: [ANN] Luacheck 0.19.0, Pierre Chapuis
    • Re: [ANN] Luacheck 0.19.0, Marc Balmer
    • Re: [ANN] Luacheck 0.19.0, Hisham
    • Re: [ANN] Luacheck 0.19.0, Geoff Leyland
    • Re: [ANN] Luacheck 0.19.0, Thibault Charbonnier
      • Re: [ANN] Luacheck 0.19.0, Peter Melnichenko
• Lua 5.3 JIT, Alex Larsen
  • Re: Lua 5.3 JIT, Charles Heywood
    • Re: Lua 5.3 JIT, szbnwer@<a href="/cgi-bin/echo.cgi?gmail.com">...</a>
      • Re: Lua 5.3 JIT, Dirk Laurie
      • Re: Lua 5.3 JIT, Soni L.
      • Re: Lua 5.3 JIT, 云风 Cloud Wu
  • Re: Lua 5.3 JIT, Dibyendu Majumdar
    • Re: Lua 5.3 JIT, Leonardo
• Re: *SPAM* Re: [ANN] LuaGRAPH 2.0 - A binding to the graphviz library, Herbert Leuwer
  • Re: *SPAM* Re: [ANN] LuaGRAPH 2.0 - A binding to the graphviz library, Martin
• Lua in Moscow 2017: live video feed tomorrow (mostly in English), Alexander Gladysh
  • Re: Lua in Moscow 2017: live video feed tomorrow (mostly in English), Daurnimator
    • Re: Lua in Moscow 2017: live video feed tomorrow (mostly in English), Alexander Gladysh
      • Re: Lua in Moscow 2017: live video feed tomorrow (mostly in English), Aapo Talvensaari
      • Re: Lua in Moscow 2017: live video feed tomorrow (mostly in English), François Perrad
      • Re: Lua in Moscow 2017: live video feed tomorrow (mostly in English), Hisham
      • Re: Lua in Moscow 2017: live video feed tomorrow (mostly in English), Luiz Henrique de Figueiredo
      • Re: Lua in Moscow 2017: live video feed tomorrow (mostly in English), Michal Kottman
  • Re: Lua in Moscow 2017: live video feed tomorrow (mostly in English), Dibyendu Majumdar
    • Re: Lua in Moscow 2017: live video feed tomorrow (mostly in English), Ką Mykolas
      • Re: Lua in Moscow 2017: live video feed tomorrow (mostly in English), Dibyendu Majumdar
      • Re: Lua in Moscow 2017: live video feed tomorrow (mostly in English), Anton Soldatov
  • Re: Lua in Moscow 2017: live video feed tomorrow (mostly in English), Alexander Gladysh
    • Re: Lua in Moscow 2017: live video feed tomorrow (mostly in English), Nagaev Boris
• Luarocks List.lua from Lua script, Russell Haley
  • Re: Luarocks List.lua from Lua script, Russell Haley
• Colon notation in object-oriented programming, Dirk Laurie
  • Re: Colon notation in object-oriented programming, Petri Häkkinen
    • Re: Colon notation in object-oriented programming, Petri Häkkinen
      • Re: Colon notation in object-oriented programming, Soni L.
      • Re: Colon notation in object-oriented programming, Petri Häkkinen
      • Re: Colon notation in object-oriented programming, Soni L.
      • Re: Colon notation in object-oriented programming, Petri Häkkinen
      • Re: Colon notation in object-oriented programming, Soni L.
      • Re: Colon notation in object-oriented programming, Francisco Olarte
      • Re: Colon notation in object-oriented programming, Petri Häkkinen
    • Re: Colon notation in object-oriented programming, Peter Aronoff
      • Re: Colon notation in object-oriented programming, Dirk Laurie
      • Re: Colon notation in object-oriented programming, Soni L.
      • Re: Colon notation in object-oriented programming, Dirk Laurie
      • Re: Colon notation in object-oriented programming, Soni L.
      • Re: Colon notation in object-oriented programming, Peter Aronoff
      • Re: Colon notation in object-oriented programming, Peter Aronoff
      • Re: Colon notation in object-oriented programming, Dirk Laurie
      • Re: Colon notation in object-oriented programming, Petri Häkkinen
      • Re: Colon notation in object-oriented programming, Francisco Olarte
      • Re: Colon notation in object-oriented programming, Peter Aronoff
  • Re: Colon notation in object-oriented programming, Viacheslav Usov
    • Re: Colon notation in object-oriented programming, Francisco Olarte
      • Re: Colon notation in object-oriented programming, Dirk Laurie
      • Re: Colon notation in object-oriented programming, Francisco Olarte
      • Re: Colon notation in object-oriented programming, Coda Highland
      • Re: Colon notation in object-oriented programming, Francisco Olarte
      • Re: Colon notation in object-oriented programming, Dirk Laurie
  • Re: Colon notation in object-oriented programming, Sean Conner
    • Re: Colon notation in object-oriented programming, Xavier Wang
      • Re: Colon notation in object-oriented programming, David Favro
      • Re: Colon notation in object-oriented programming, szbnwer@<a href="/cgi-bin/echo.cgi?gmail.com">...</a>
      • Error Reporting (was Re: Colon notation in object-oriented programming), Sean Conner
      • Re: Error Reporting (was Re: Colon notation in object-oriented programming), Charles Heywood
      • Re: Error Reporting (was Re: Colon notation in object-oriented programming), Charles Heywood
      • Re: Error Reporting (was Re: Colon notation in object-oriented programming), Daurnimator
• Can't Lua ever sleep?, Dirk Laurie
  • Re: Can't Lua ever sleep?, Charles Heywood
  • Re: Can't Lua ever sleep?, Sean Conner
  • Re: Can't Lua ever sleep?, szbnwer@<a href="/cgi-bin/echo.cgi?gmail.com">...</a>
  • Re: Can't Lua ever sleep?, Sean Conner
    • Re: Can't Lua ever sleep?, Dirk Laurie
      • Re: Can't Lua ever sleep?, Daurnimator
      • Re: Can't Lua ever sleep?, Dirk Laurie
      • Re: Can't Lua ever sleep?, Sean Conner
      • Re: Can't Lua ever sleep?, Enrico Colombini
      • Re: Can't Lua ever sleep?, Daurnimator
      • Re: Can't Lua ever sleep?, Dirk Laurie
  • Re: Can't Lua ever sleep?, Pavel Drotar
• Lua in Moscow 2017: Photos from the conference, Alexander Gladysh
• HELP, JM Venet Magic.fr
  • Fwd: HELP, JM Venet Magic.fr
    • Re: Fwd: HELP, 彭 书呆
  • RE: HELP, benjamin.steinwender
  • Re: HELP, Martin
• io.read seems not right on windws, why?, R.wen
  • Re: io.read seems not right on windws, why?, Oliver Kroth
  • Re: io.read seems not right on windws, why?, Jonathan Goble
  • <Possible follow-ups>
  • Re: io.read seems not right on windws, why?, =?gb18030?b?Ui53ZW4=?=
• interacting with gc, pierre
  • Re: interacting with gc, tomas
  • Re: interacting with gc, 彭 书呆
  • preventing a library from being modified, pierre
    • Re: preventing a library from being modified, Coda Highland
• Re: [ANN] LuaConf 2017, Call for Sponsors, Call for Presentations, Etiene Dalcol
  • Re: [ANN] LuaConf 2017, Call for Sponsors, Call for Presentations, Etiene Dalcol
• PLEASE! unsubscribe me - normal does not work!, Meino . Cramer
  • Re: PLEASE! unsubscribe me - normal does not work!, Luiz Henrique de Figueiredo
• Call for students! LuaRocks in Google Summer of Code 2017, Hisham
• "Private" C modules loaded by Rosie module, Jamie Jennings
  • Re: "Private" C modules loaded by Rosie module, Thijs Schreijer
  • <Possible follow-ups>
  • Re: "Private" C modules loaded by Rosie module, Jamie Jennings
• attempt to index global 'e_con' (a number value) error, Timothy Olawuyi
  • Re: attempt to index global 'e_con' (a number value) error, Luiz Henrique de Figueiredo
• Replacements of String Characters in LUA by using the Character Indexes, Naushad Mujawar
  • Re: Replacements of String Characters in LUA by using the Character Indexes, Dirk Laurie
  • Re: Replacements of String Characters in LUA by using the Character Indexes, Vadim A. Misbakh-Soloviov
• Fully Lua YAML library?, D. Matt Placek
  • Re: Fully Lua YAML library?, Pierre Chapuis
  • Re: Fully Lua YAML library?, Tony Papadimitriou
    • Re: Fully Lua YAML library?, D. Matt Placek
      • Re: Fully Lua YAML library?, Coda Highland
      • Re: Fully Lua YAML library?, D. Matt Placek
      • Re: Fully Lua YAML library?, Thijs Schreijer
      • Re: Fully Lua YAML library?, Sean Conner
    • Re: Fully Lua YAML library?, Daurnimator
      • Re: Fully Lua YAML library?, Soni L.
      • Re: Fully Lua YAML library?, Pierre Chapuis
      • Re: Fully Lua YAML library?, D. Matt Placek
      • Re: Fully Lua YAML library?, Dirk Laurie
• Restricted parsing for static config files / more granular `load()` options for 5.4, Rain Gloom
  • Re: Restricted parsing for static config files / more granular `load()` options for 5.4, Luiz Henrique de Figueiredo
  • Re: Restricted parsing for static config files / more granular `load()` options for 5.4, Soni L.
  • Re: Restricted parsing for static config files / more granular `load()` options for 5.4, Martin
    • Re: Restricted parsing for static config files / more granular `load()` options for 5.4, Rain Gloom
      • Re: Restricted parsing for static config files / more granular `load()` options for 5.4, Coda Highland
  • Re: Restricted parsing for static config files / more granular `load()` options for 5.4, nobody
  • <Possible follow-ups>
  • Re: Restricted parsing for static config files / more granular `load()` options for 5.4, Jamie Jennings
• Lack of bytecode optimization in Lua, Egor Skriptunoff
  • Re: Lack of bytecode optimization in Lua, Coda Highland
  • Re: Lack of bytecode optimization in Lua, Martin
    • Re: Lack of bytecode optimization in Lua, Egor Skriptunoff
  • Re: Lack of bytecode optimization in Lua, Thomas Jericke
    • Re: Lack of bytecode optimization in Lua, Egor Skriptunoff
  • Re: Lack of bytecode optimization in Lua, Dibyendu Majumdar
• When is multiple assignment good style?, Dirk Laurie
  • Re: When is multiple assignment good style?, Daurnimator
  • Re: When is multiple assignment good style?, Alexey Melnichuk
  • Re: When is multiple assignment good style?, Sean Conner
    • Re: When is multiple assignment good style?, Paul E. Merrell, J.D.
    • Re: When is multiple assignment good style?, Tim Hill
      • Re: When is multiple assignment good style?, Coda Highland
      • Re: When is multiple assignment good style?, Dirk Laurie
      • Re: When is multiple assignment good style?, Hisham
      • Re: When is multiple assignment good style?, Nagaev Boris
      • Re: When is multiple assignment good style?, Francisco Olarte
      • Re: When is multiple assignment good style?, Chris Jones
      • Re: When is multiple assignment good style?, steve donovan
      • Re: When is multiple assignment good style?, Francisco Olarte
      • Re: When is multiple assignment good style?, steve donovan
      • Re: When is multiple assignment good style?, Francisco Olarte
      • Re: When is multiple assignment good style?, Eike Decker
      • Re: When is multiple assignment good style?, Nagaev Boris
      • Re: When is multiple assignment good style?, Soni L.
      • Re: When is multiple assignment good style?, Chris Jones
      • Re: When is multiple assignment good style?, Javier Guerra Giraldez
      • Re: When is multiple assignment good style?, Chris Jones
      • Re: When is multiple assignment good style?, Viacheslav Usov
      • Re: When is multiple assignment good style?, Chris Jones
      • Re: When is multiple assignment good style?, Viacheslav Usov
      • Re: When is multiple assignment good style?, Hisham
      • Re: When is multiple assignment good style?, Sean Conner
      • Re: When is multiple assignment good style?, Martin
      • Re: When is multiple assignment good style?, Viacheslav Usov
      • Re: When is multiple assignment good style?, Sean Conner
  • Re: When is multiple assignment good style?, Viacheslav Usov
• Writing scripts that are compatible with Lua 5.1, 5.2, and 5.3?, Paul Merrell
  • Re: Writing scripts that are compatible with Lua 5.1, 5.2, and 5.3?, tomas
    • Re: Writing scripts that are compatible with Lua 5.1, 5.2, and 5.3?, Paul Merrell
      • Re: Writing scripts that are compatible with Lua 5.1, 5.2, and 5.3?, François Perrad
• Lua bug list, Dibyendu Majumdar
  • Re: Lua bug list, Luiz Henrique de Figueiredo
    • Re: Lua bug list, Dibyendu Majumdar
• Re: Android support, seibelj
  • Re: Android support, James Seibel
    • Re: Android support, Roberto Ierusalimschy
      • Re: Android support, James Seibel
• Quiteing clang static analyzer, Jerry Jacobs
  • Re: Quiteing clang static analyzer, Igor Ehrlich
    • Re: Quiteing clang static analyzer, Jerry Jacobs
      • Re: Quiteing clang static analyzer, Igor Ehrlich
      • Re: Quiteing clang static analyzer, Igor Ehrlich
      • Re: Quiteing clang static analyzer, Nagaev Boris
      • Re: Quiteing clang static analyzer, Jerry Jacobs
      • Re: Quiteing clang static analyzer, Igor Ehrlich
      • Re: Quiteing clang static analyzer, Igor Ehrlich
• Turn off LUA_USE_DLOPEN on iOS, 云风 Cloud Wu
  • Re: Turn off LUA_USE_DLOPEN on iOS, Nagaev Boris
    • Re: Turn off LUA_USE_DLOPEN on iOS, 云风 Cloud Wu
      • Re: Turn off LUA_USE_DLOPEN on iOS, Nagaev Boris
      • Re: Turn off LUA_USE_DLOPEN on iOS, 云风 Cloud Wu
      • Re: Turn off LUA_USE_DLOPEN on iOS, Chris Jones
      • Re: Turn off LUA_USE_DLOPEN on iOS, Hisham
• luaL_Buffer use question, gz
  • Re: luaL_Buffer use question, Roberto Ierusalimschy
    • Re: luaL_Buffer use question, gz
  • Re: luaL_Buffer use question, Duncan Cross
• Fwd: Undeliverable: "Private" C modules loaded by Rosie module, Thijs Schreijer
• [ANN] LLVM 4.0 support in Ravi, Dibyendu Majumdar
• lua_newstate crashes on "setnilvalue(L, registry(L)); ", lua_State L initialized with garbage?, Iaroslav Ianishyn
  • Re: lua_newstate crashes on "setnilvalue(L, registry(L)); ", lua_State L initialized with garbage?, Roberto Ierusalimschy
    • RE: lua_newstate crashes on "setnilvalue(L, registry(L)); ", lua_State L initialized with garbage?, Iaroslav Ianishyn
      • Re: lua_newstate crashes on "setnilvalue(L, registry(L)); ", lua_State L initialized with garbage?, Roberto Ierusalimschy
    • Re: lua_newstate crashes on "setnilvalue(L, registry(L)); ", lua_State L initialized with garbage?, Joshua Jensen
• [ANN] lsocket 1.4.1, gz
  • Re: [ANN] lsocket 1.4.1, gz
• Re: Re Atari BASIC versis Python versus Lua in 1982..., Laurent FAILLIE
  • Re: Re Atari BASIC versis Python versus Lua in 1982..., Sean Conner
    • Re: Re Atari BASIC versis Python versus Lua in 1982..., Hisham
      • Migrating function to newer Lua (Re Atari BASIC versis Python versus Lua in 1982...), Laurent FAILLIE
    • Re: Re Atari BASIC versis Python versus Lua in 1982..., Martin
      • Re: Re Atari BASIC versis Python versus Lua in 1982..., Coda Highland
  • <Possible follow-ups>
  • Re: Re: Re Atari BASIC versis Python versus Lua in 1982..., Frank Kastenholz
  • Re: Re Atari BASIC versis Python versus Lua in 1982..., Andrew Starks
    • Re: Re Atari BASIC versis Python versus Lua in 1982..., Enrico Colombini
  • Re: Re Atari BASIC versis Python versus Lua in 1982..., steve donovan
• Re: Seeking opinions about a use case of using Lua as a data description language, Sean Conner
  • Re: Seeking opinions about a use case of using Lua as a data description language, Hakki Dogusan
• Sandbox implementation, Anon ym
  • <Possible follow-ups>
  • Re: Sandbox implementation, Frank Kastenholz
    • Re: Sandbox implementation, David F
  • Re: Re: Sandbox implementation, Frank Kastenholz
• Sandbox implementation, attempt #2, David F
  • Re: Sandbox implementation, attempt #2, Soni L.
    • Sandbox implementation, attempt #2, David F
      • Re: Sandbox implementation, attempt #2, Soni L.
      • Sandbox implementation, attempt #2, David F
      • Re: Sandbox implementation, attempt #2, Kat Kioo
      • Sandbox implementation, attempt #2, David F
      • Re: Sandbox implementation, attempt #2, Kat Kioo
      • Re: Sandbox implementation, attempt #2, David F
      • Re: Sandbox implementation, attempt #2, Soni L.
      • Re: Sandbox implementation, attempt #2, David F
      • Re: Sandbox implementation, attempt #2, Sean Conner
• Conditional Function Definition, Marcello Chiuminatto
  • Re: Conditional Function Definition, Sean Conner
  • Re: Conditional Function Definition, Dirk Laurie
    • RE: Conditional Function Definition, Marcello Chiuminatto
      • Re: Conditional Function Definition, Parke
      • RE: Conditional Function Definition, Marcello Chiuminatto
  • <Possible follow-ups>
  • Conditional Function Definition, David F
• Feature request: per-value uservalue, Xavier Wang
  • Re: Feature request: per-value uservalue, Tim Hill
    • Re: Feature request: per-value uservalue, Xavier Wang
    • Re: Feature request: per-value uservalue, 云风 Cloud Wu
      • Re: Feature request: per-value uservalue, Tim Hill
      • Re: Feature request: per-value uservalue, Xavier Wang
      • Re: Feature request: per-value uservalue, Sean Conner
      • Re: Feature request: per-value uservalue, Xavier Wang
      • Re: Feature request: per-value uservalue, 彭 书呆
      • Re: Feature request: per-value uservalue, Tim Hill
      • Re: Feature request: per-value uservalue, 彭 书呆
      • Re: Feature request: per-value uservalue, Tim Hill
      • Re: Feature request: per-value uservalue, Coda Highland
      • Re: Feature request: per-value uservalue, Thomas Jericke
      • Re: Feature request: per-value uservalue, Coda Highland
      • Re: Feature request: per-value uservalue, Tim Hill
      • Re: Feature request: per-value uservalue, Coda Highland
      • Re: Feature request: per-value uservalue, Roberto Ierusalimschy
      • Re: Feature request: per-value uservalue, Andrew Starks
      • Re: Feature request: per-value uservalue, Tim Hill
      • Re: Feature request: per-value uservalue, 云风 Cloud Wu
      • Re: Feature request: per-value uservalue, Francisco Olarte
      • Re: Feature request: per-value uservalue, Viacheslav Usov
• A new way of blogging about Lua, Roland
• API/ABI changes review for liblua, Andrey Ponomarenko
• Lua Code Combine (LuaCC), Miha Cooper
  • Re: Lua Code Combine (LuaCC), Pierre Chapuis
    • Re: Lua Code Combine (LuaCC), Miha Cooper
      • Re: Lua Code Combine (LuaCC), Milind Gupta
    • Re: Lua Code Combine (LuaCC), Pierre Chapuis
      • Re: Lua Code Combine (LuaCC), Miha Cooper
• Pepperfish downtime last night, Rob Kendrick
• Re: lua.org down, Luiz Henrique de Figueiredo
• luasql, Timothy Olawuyi
• glue the bytecode with lua, Andreas Mueller
  • Re: glue the bytecode with lua, Tony Papadimitriou
  • Re: glue the bytecode with lua, Dirk Laurie
    • Re: glue the bytecode with lua, steve donovan
      • Re: glue the bytecode with lua, Samir Tine
  • Re: glue the bytecode with lua, Luiz Henrique de Figueiredo
• Selenophobia, Egor Skriptunoff
  • Re: Selenophobia, p. shkadzko
    • Re: Selenophobia, p. shkadzko
  • Re: Selenophobia, Frank Kastenholz
    • Re: Selenophobia, Tim Hill
    • Re: Selenophobia, Vadim A. Misbakh-Soloviov
      • Re: Selenophobia, Alex Larsen
      • Performance (was Re: Selenophobia), Frank Kastenholz
      • Re: Performance (was Re: Selenophobia), Dirk Laurie
      • Re: Performance (was Re: Selenophobia), Tim Hill
      • Re: Performance (was Re: Selenophobia), Dirk Laurie
      • Re: Performance (was Re: Selenophobia), Frank Kastenholz
      • Re: Performance (was Re: Selenophobia), Tim Hill
      • Re: Performance (was Re: Selenophobia), Luiz Henrique de Figueiredo
      • Re: Performance (was Re: Selenophobia), Marc Balmer
      • Re: Performance (was Re: Selenophobia), Tim Hill
      • Re: Performance (was Re: Selenophobia), Daurnimator
      • Re: Performance (was Re: Selenophobia), Daurnimator
    • Re: Selenophobia, Egor Skriptunoff
      • Re: Selenophobia, Frank Kastenholz
      • Re: Selenophobia, szbnwer@<a href="/cgi-bin/echo.cgi?gmail.com">...</a>
  • Re: Selenophobia, Sean Conner
    • Re: Selenophobia, Charles Heywood
    • Re: Selenophobia, Andrew Starks
    • Re: Selenophobia, Russell Haley
    • Re: Selenophobia, Enrico Colombini
      • Re: Selenophobia, Sean Conner
      • Re: Selenophobia, Enrico Colombini
  • Re: Selenophobia, Pierre Chapuis
    • Re: Selenophobia, steve donovan
      • Re: Selenophobia, Joseph Manning
      • Re: Selenophobia, Tim Hill
      • Re: Selenophobia, Ahmed Charles
      • Re: Selenophobia, Dirk Laurie
      • Re: Selenophobia, Enrico Colombini
      • Re: Selenophobia, Tim Hill
      • Re: Selenophobia, Ahmed Charles
      • Re: Selenophobia, Javier Guerra Giraldez
      • Re: Selenophobia, Ahmed Charles
      • Re: Selenophobia, Javier Guerra Giraldez
      • Re: Selenophobia, Joseph Manning
      • Re: Selenophobia, Ahmed Charles
      • Re: Selenophobia, Dirk Laurie
      • Message not available
      • Re: Selenophobia, Ką Mykolas
    • Re: Selenophobia, Andrew Starks
      • Re: Selenophobia, Paul K
      • Re: Selenophobia, Andrew Starks
      • Re: Selenophobia, steve donovan
    • Re: Selenophobia, Dirk Laurie
    • Re: Selenophobia, Sean Conner
  • Re: Selenophobia, Martin
    • Re: Selenophobia, p. shkadzko
      • Re: Selenophobia, Sean Conner
  • <Possible follow-ups>
  • Re: Selenophobia, pierre
    • Re: Selenophobia, Luiz Henrique de Figueiredo
    • Re: Selenophobia, Sean Conner
      • Multi-thread Semantics (Re: Selenophobia), William Ahern
      • Re: Multi-thread Semantics (Re: Selenophobia), Javier Guerra Giraldez
    • Re: Selenophobia, Fabien
      • Re: Selenophobia, steve donovan
• Breakthrough dream, Rodrigo Azevedo
  • Re: Breakthrough dream, Peter Aronoff
    • Re: Breakthrough dream, Rodrigo Azevedo
      • Re: Breakthrough dream, Peter Aronoff
      • Re: Breakthrough dream, Rodrigo Azevedo
      • Re: Breakthrough dream, Pierre Chapuis
      • Re: Breakthrough dream, Dirk Laurie
  • Re: Breakthrough dream, Marc Balmer
  • Re: Breakthrough dream, Dirk Laurie
    • Re: Breakthrough dream, Egor Skriptunoff
      • Re: Breakthrough dream, Florian Weimer
      • Re: Breakthrough dream, Martin
      • Re: Breakthrough dream, Frank Kastenholz
      • Re: Breakthrough dream or Selenophobia, Russell Haley
      • Re: Breakthrough dream or Selenophobia, Ulrich Schmidt
      • Re: Breakthrough dream or Selenophobia, Viacheslav Usov
      • Re: Breakthrough dream or Selenophobia, Dirk Laurie
      • Re: Breakthrough dream or Selenophobia, Peter Aronoff
      • Re: Breakthrough dream or Selenophobia, Luiz Henrique de Figueiredo
      • Re: Breakthrough dream or Selenophobia, Dirk Laurie
    • Re: Breakthrough dream, Tim Hill
  • Re: Breakthrough dream, Sean Conner
    • Re: Breakthrough dream, Luiz Henrique de Figueiredo
      • Re: Breakthrough dream, Vadim A. Misbakh-Soloviov
    • Re: Breakthrough dream, Pierre Chapuis
  • Re: Breakthrough dream, Pierre Chapuis
    • Re: Breakthrough dream, Enrico Colombini
      • Re: Breakthrough dream, Ross Berteig
    • Re: Breakthrough dream, Philipp Janda
  • Re: Breakthrough dream, Andrew Starks
    • Re: Breakthrough dream, Dirk Laurie
  • <Possible follow-ups>
  • Re: Breakthrough dream, Duane Leslie
    • Re: Breakthrough dream, Sean Conner
• Lua 5.0.2 scalability with very large scripts, Andreas Falkenhahn
  • Re: Lua 5.0.2 scalability with very large scripts, Martin
• Regex 'Absent Operator', Scott Morgan
  • Re: Regex 'Absent Operator', Ulrich Schmidt
  • Re: Regex 'Absent Operator', Pierre-Yves Gérardy
• Re: Re: Performance (was Re: Selenophobia), Frank Kastenholz
• Back and forth UTC dates, Javier Mr
  • Re: Back and forth UTC dates, Oliver Kroth
    • Re: Back and forth UTC dates, Francisco Olarte
      • Re: Back and forth UTC dates, Oliver Kroth
      • Re: Back and forth UTC dates, Vadim A. Misbakh-Soloviov
      • Re: Back and forth UTC dates, Francisco Olarte
  • Re: Back and forth UTC dates, Francisco Olarte
    • Re: Back and forth UTC dates, Dirk Laurie
      • Re: Back and forth UTC dates, Francisco Olarte
  • Re: Back and forth UTC dates, Francisco Olarte
    • Re: Back and forth UTC dates, Javier Mr
      • Re: Back and forth UTC dates, Luiz Henrique de Figueiredo
      • Re: Back and forth UTC dates, Francisco Olarte
      • Re: Back and forth UTC dates, Roberto Ierusalimschy
      • Re: Back and forth UTC dates, Viacheslav Usov
      • Re: Back and forth UTC dates, Roberto Ierusalimschy
      • Re: Back and forth UTC dates, Viacheslav Usov
      • Re: Back and forth UTC dates, Roberto Ierusalimschy
      • Re: Back and forth UTC dates, Gé Weijers
      • Re: Back and forth UTC dates, Daurnimator
      • Re: Back and forth UTC dates, Martin
      • Re: Back and forth UTC dates, Roberto Ierusalimschy
      • Re: Back and forth UTC dates, Francisco Olarte
• Repeated processing of large datasets, John Logsdon
  • <Possible follow-ups>
  • Repeated processing of large datasets, John Logsdon
  • Repeated processing of large datasets, John Logsdon
    • Re: Repeated processing of large datasets, Francisco Olarte
    • Re: Repeated processing of large datasets, Peter Pimley
    • Re: Repeated processing of large datasets, Geoff Leyland
      • Re: Repeated processing of large datasets, John Logsdon
      • Re: Repeated processing of large datasets, Geoff Leyland
      • Re: Repeated processing of large datasets, Parke
• forcing userdata to be gc'd?, John Dunn
  • Re: forcing userdata to be gc'd?, nobody
  • Re: forcing userdata to be gc'd?, Francisco Olarte
    • Re: forcing userdata to be gc'd?, William Ahern
      • Re: forcing userdata to be gc'd?, Gé Weijers
  • Re: forcing userdata to be gc'd?, Florian Weimer
    • Re: forcing userdata to be gc'd?, Francisco Olarte
• Safe user-facing pattern matching., Jorge
  • Re: Safe user-facing pattern matching., Rena
    • Re: Safe user-facing pattern matching., Jorge
      • Re: Safe user-facing pattern matching., Viacheslav Usov
      • Re: Safe user-facing pattern matching., tomas
      • Re: Safe user-facing pattern matching., Viacheslav Usov
      • Re: Safe user-facing pattern matching., Gé Weijers
      • Re: Safe user-facing pattern matching., Roberto Ierusalimschy
      • Re: Safe user-facing pattern matching., Rain Gloom
      • Re: Safe user-facing pattern matching., Coda Highland
      • Re: Safe user-facing pattern matching., Jorge
      • Re: Safe user-facing pattern matching., Coda Highland
      • Re: Safe user-facing pattern matching., Rena
• Off-topic: a new JIT compiler for C with LLVM backend, Dibyendu Majumdar
  • Re: Off-topic: a new JIT compiler for C with LLVM backend, Javier Guerra Giraldez
    • Re: Off-topic: a new JIT compiler for C with LLVM backend, Dibyendu Majumdar
• gmatch problem, John Logsdon
  • Re: gmatch problem, Roberto Ierusalimschy
  • Re: gmatch problem, Dirk Laurie
• [ANN] lua-psl 0.2, Daurnimator
• Reminder: student application period for Google Summer of Code ends April 3, Hisham

---

Mail converted by MHonArc 2.6.19