lua-l archive

Search lua-l

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

161. Re: newbee question... (score: 22)

Author: Rob Kendrick (Lua) <lua@...>

Date: Thu, 19 Oct 2000 11:13:45 +0100

Thats something I found had to get used to, but I did :) Cheers, -- Rob Kendrick, http://www.digital-scurf.org/ Work is the scythe of time.

162. Re: newbee question... (score: 22)

Author: Jonathan Adamczewski <jadamcze@...>

Date: Thu, 19 Oct 2000 10:09:49 +0000 (GMT)

Out of curiousity... nil 1 3 Why does table indexing begin at 1 and not zero? I guess this is just a convention, but I've become accustomed to zero based arrays :) Thanks Jonathan.

163. Re: LUA oddities.. (score: 19)

Author: Patrick Masotta <masottaus@...>

Date: Mon, 18 Jun 2012 04:32:15 -0700 (PDT)

Do you think C has to adatp to LUA? don't you think the other way arround should be a smarter approach? Do you really think today?s LUA target are the mining engineers that do not want to learn a 0 b

164. Cons, tuple and __slots__ -- a simple mechanism to implement them in Lua (score: 19)

Author: Xavier Wang <weasley.wx@...>

Date: Fri, 16 Sep 2011 10:21:58 +0800

hi list :) I'm very sad that nobody reply my last post[1], even Roberto didn't. patch-ev is a very simple and powerful improve for Lua. It fills the space between simple type such as number and strin

165. Re: Luajit and curstom data structures (score: 19)

Author: Mike Pall <mikelu-1104@...>

Date: Sat, 9 Apr 2011 00:39:45 +0200

The problem in your case are the Lua semantics for __newindex: they require checking that the table _doesn't_ contain the key before calling the __newindex metamethod. So it's really doing this: for

166. Re: LuaJIT 64 bit integers (was: the purpose of lightuserdata) (score: 19)

Author: Josh Haberman <jhaberman@...>

Date: Thu, 13 Jan 2011 17:05:47 +0000 (UTC)

Yes, I shudder to think of explaining that to users. I was initially very excited to hear your announcement of 64-bit integer support since it's been a stumbling block for adoption of Lua inside Goog

167. Re: LuaJIT 64 bit integers (was: the purpose of lightuserdata) (score: 19)

Author: Mike Pall <mikelu-1101@...>

Date: Thu, 13 Jan 2011 12:27:01 +0100

Then you'll be even more surprised that t[1LL] != t[1LL], because neither cdata not cdata literals are interned. 64 bit integers are (REALLY!) unsuitable as table keys. One wouldn't come up with code

168. Re: Holes (score: 19)

Author: steve donovan <steve.j.donovan@...>

Date: Tue, 14 Dec 2010 12:03:44 +0200

I think this elegance argument carries a lot of weight with the Lua authors, which is why it's probably a non-starter. In any case, we're expecting a single very flexible data type to work how we mea

169. Re: sunday afternoon whishlist (score: 19)

Author: Tony Finch <dot@...>

Date: Sun, 9 May 2010 18:01:27 +0100

Perl's handling of nonexistent indices is more complicated than that. If you write $x->{y}->{z} (Perl for x.y.z) then $x-{y} is autovivified into a reference to a hash. This also applies to array ref

170. Re: lists with nil play nice for Lua 5.2 (score: 19)

Author: Asko Kauppi <askok@...>

Date: Thu, 9 Aug 2007 19:03:05 +0300

Well, this turns out to be yet another reason for redefinable __len. That way, one could have tables whose # operator counts from zero. -asko Greg Falcon kirjoitti 9.8.2007 kello 18:29: Errrr, which