lua-l archive

Search lua-l

This index contains 143,604 documents and 1,774,497 keywords. Last update on 2023-03-08 .

101. Re: Request for 5.4: adding [] as table creation syntax for Lua 6.0 (score: 48)

Author: Thomas Jericke <tjericke@...>

Date: Thu, 14 Jul 2016 07:35:39 +0200

On 07/13/2016 01:41 PM, Egor Skriptunoff wrote: On Wed, Jul 13, 2016 at 9:32 AM, Thomas Jericke <tjericke@indel.ch> wrote: On 07/12/2016 10:58 PM, Rena wrote: If there were going to be new syntax, I

102. Re: Why no for table-iterator like e. g. "hashpairs"? (score: 45)

Author: Philippe Verdy <verdyp@...>

Date: Tue, 5 Nov 2019 16:41:43 +0100

one little issue that isn't always evident:  the array part of Lua tables is an implementation detail, a performance trick that is supposed to be invisible to Lua code. in principle, a table is a se

103. Re: tables holding nil: another way to look at the question itself (score: 45)

Author: Jerome Vuarand <jerome.vuarand@...>

Date: Tue, 28 Jul 2009 17:44:36 +0200

2009/7/28 Cosmin Apreutesei <cosmin.apreutesei@gazolin.ro>: Vararg lists are special kind of objects that you cannot instantiate or reference. They are not tables. You don't have to use or allow the

104. "require" stack bug? (score: 45)

Author: Rob Shaw <rob@...>

Date: Tue, 2 May 2006 11:51:09 +0200

Hi, I have some code to access a C array from lua, and got it to work following the example code around pg. 246 of the lua book (1st edition). If I register the metamethods from the lua side, everyth

105. Re: Request for 5.4: adding [] as table creation syntax for Lua 6.0 (score: 43)

Author: Egor Skriptunoff <egor.skriptunoff@...>

Date: Wed, 13 Jul 2016 14:41:28 +0300

On Wed, Jul 13, 2016 at 9:32 AM, Thomas Jericke <tjericke@indel.ch> wrote: On 07/12/2016 10:58 PM, Rena wrote: If there were going to be new syntax, I feel it'd go well with the discussion of arrays:

106. Re: Request for 5.4: adding [] as table creation syntax for Lua 6.0 (score: 43)

Author: Thomas Jericke <tjericke@...>

Date: Wed, 13 Jul 2016 08:32:23 +0200

actually looks like a If there were going to be new syntax, I feel it'd go well with the discussion of arrays: t = {x, y, z} --same as current meaning a = [x, y, z] --means: a = array(x, y, z) Where

107. Re: ipairs in Lua 5.3.0-alpha (score: 43)

Author: Andrew Starks <andrew.starks@...>

Date: Sat, 16 Aug 2014 09:23:01 -0500

Maybe I should explain what I meant with "hack": it helps only if nil is an exception. In all other cases it doesn't speed things up. I couldn't resist to do a further benchmark for demonstration (e

108. Re: ipairs in Lua 5.3.0-alpha (score: 43)

Author: Andrew Starks <andrew.starks@...>

Date: Sat, 16 Aug 2014 08:37:25 -0500

Maybe I should explain what I meant with "hack": it helps only if nil is an exception. In all other cases it doesn't speed things up. I couldn't resist to do a further benchmark for demonstration (e

109. Re: ipairs in Lua 5.3.0-alpha (score: 43)

Author: Jan Behrens <jbe-lua-l@...>

Date: Sat, 16 Aug 2014 13:31:48 +0200

Maybe I should explain what I meant with "hack": it helps only if nil is an exception. In all other cases it doesn't speed things up. I couldn't resist to do a further benchmark for demonstration (ev

110. Re: Proposal: Make creating large arrays faster and "allow" nils in arrays (score: 41)

Author: Philippe Verdy <verdyp@...>

Date: Sat, 25 Jul 2020 08:29:47 +0200

And where does it contradict what I said ? I just said that ipairs() does not enumerate only the array part, because of course integer keys in the sequence can also be in the hashed part (given the f