lua-users home
lua-l archive

Search lua-l

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

Query: [How to search]

Display: Description: Sort by:

Results:

References: [ lua (Too many documents hit. Ignored) ] [ array: 5396 ] [ indexing: 1373 ]

Total 296 documents matching your query.

41. Re: 1-based indexing in Lua (score: 220)
Author: Francisco Olarte <folarte@...>
Date: Fri, 30 Mar 2018 17:05:49 +0200
You are comparing lua tables, which are dictionaries with some fancy optimization for positive integer indexes, to python lists, which are not. If you use the closer type to a lua table in python, a
42. What is a Lua string? (Was: String indexing again) (score: 220)
Author: Dirk Laurie <dpl@...>
Date: Tue, 21 Dec 2010 10:20:15 +0200
Definition: A string is a Lua value consisting of a sequence of bytes but having no other structure, mainly used to represent other values in a human-readable way. In particular, a string is not a ta
43. Re: String indexing again (score: 220)
Author: Axel Kittenberger <axkibe@...>
Date: Mon, 20 Dec 2010 17:20:22 +0100
The issue with UTF8, which has become the defacto unicode standard pick, that chars have variable with. Something classic C did not see coming, and it causes all kind of confusions clashing with the
44. Re: String indexing again (score: 220)
Author: Axel Kittenberger <axkibe@...>
Date: Mon, 20 Dec 2010 16:33:18 +0100
IMHO the best argument given has been the reference to (future?) UTF8 portability. The n-th character from a string with UTF8 characters is a nontrivial operation with O(n) costs. It is not necessar
45. Re: String indexing again (score: 220)
Author: Tony Finch <dot@...>
Date: Sun, 19 Dec 2010 22:32:31 +0000
It says character but it means octet. A string is an array of octets. The mapping from sequences of octets to Unicode codepoints varies, and the relationship between codepoints and glyphs is complica
46. Re: Any thoughts on indexing ...? (score: 220)
Author: Mark Hamburg <mhamburg@...>
Date: Wed, 09 Apr 2008 09:51:31 -0700
Though if we're worrying about optimization, it would be nice to recognize that if given something like: for i, x in ipairs{ "a", "b", "c" } do -- end Then the constructed table can be lifted out as
47. Re: Any thoughts on indexing ...? (score: 220)
Author: Mike Pall <mikelu-0804@...>
Date: Wed, 9 Apr 2008 14:47:14 +0200
Well, yes. But large varargs are rare. Comparison here: http://lua-users.org/lists/lua-l/2006-04/msg00120.html I still think apairs() would be a useful addition to Lua (5.2?). It would be a concise r
48. Re: Empty? No. Array? No. Has? Yes. (score: 206)
Author: Rena <hyperhacker@...>
Date: Sat, 6 Jul 2013 08:20:24 -0400
Honestly, all these ideas just seem to be adding a lot more complication and confusion, trying to solve two problems at once. When people talk about wanting to store nil in a table, it seems like the
49. Re: How to correctly manage a multi-dimension array with LuaJIT FFI ? (score: 202)
Author: Mike Pall <mikelu-1102@...>
Date: Wed, 9 Feb 2011 18:27:54 +0100
This would work if you kept references to the cdata objects for all rows in parallel in a Lua table. Or only keep them in a Lua table -- starting indexing at 0 is efficient with LuaJIT. Arguably that
50. Re: tolua++, lua and array indexes (score: 192)
Author: "Ariel Manzur" <puntob@...>
Date: Sun, 25 Nov 2007 22:52:28 -0300
if C is 2, your array is [2] elements long, so you only have array[0] and array[1].. array[C] is, in fact, out of range (which is funny because C arrays never worked right on tolua++, but in this cas

Search by Namazu v2.0.21