lua-l archive

Search lua-l

This index contains 143,615 documents and 1,774,615 keywords. Last update on 2023-03-09 .

141. RE: Lua and adding types (score: 18)

Author: Asko Kauppi <Asko.Kauppi@...>

Date: Wed, 5 Feb 2003 17:39:19 +0200

BOOLEAN TYPE The 5.0 boolean type is really just an addon. Even in 5.0, any non-nil Lua value _still_ works as 'true'. So the illusion of having a pure boolean type is -well- an illusion. [If I'm wro

142. The Year In Scripting Languages Lua/Perl/Python/Ruby/Tcl 2002 (score: 18)

Author: Mitchell N Charity et al <langyear02@...>

Date: Tue, 14 Jan 2003 10:48:25 -0500

This is a joint review of 2002 for the programming languages Lua, Perl, Python, Ruby, and Tcl. It was a cooperative effort by people from the five communities. An HTML version is available at http://

143. RE: Windows CE (score: 18)

Author: Anna Hester <annah@...>

Date: Tue, 20 Feb 2001 13:20:27 -0800

I disagree with the statement that UTF-8 is the best option for supporting Unicode characters. Best is to say that UTF-8 is a good choice for systems that cannot (or don't want to) be modified to use

144. Re: Why does string.format() limit width to two digits? (score: 16)

Author: Philippe Verdy <verdyp@...>

Date: Tue, 24 Jan 2023 10:48:32 +0100

I don't see at all why just this restriction would avoid a buffer overflow, given that there's not even an upper bound for the string length of the variable in parameter. This just limits the numbers

145. Re: [PATCH] Fix integer overflow when parsing hex numbers (score: 16)

Author: Lorenzo Donati <lorenzodonatibz@...>

Date: Sun, 5 Jun 2022 15:13:41 +0200

It's not a bug. The manual says "if the value overflows, it wraps around to fit into a valid integer." https://www.lua.org/manual/5.4/manual.html#3.1 Is this behavior new for Lua 5.4 compared with Lu

146. [BUG?] Re: The Lua utf8 library (Was: Issues: Character 160 ...) (score: 16)

Author: Viacheslav Usov <via.usov@...>

Date: Thu, 12 Jul 2018 12:59:01 +0200

On Wed, Jul 11, 2018 at 10:59 PM Gregg Reynolds <dev@mobileink.com> wrote: On Wed, Jul 11, 2018, 1:43 AM Dirk Laurie <dirk.laurie@gmail.com> wrote: ... of mapping a certain subset of strings (which I

147. Re: 1-based indexing in Lua or the one without zero (score: 16)

Author: Axel Kittenberger <axkibe@...>

Date: Mon, 23 Apr 2018 18:58:50 +0200

Totally ok, but I do not understand why you point we have several ways of counting when I stated that was measuring. About points 1..2 when indexing in fortran/c/lua/python you use that, when counti

148. Re: A proposal for the confusing pseudo table ? array concept (score: 16)

Author: Advert Slaxxor <adv3r7@...>

Date: Sat, 20 Jan 2018 02:15:10 +0000

A table is a table. There is no such thing as a sequenced table. If you have: t = {1, 2, 3, 4} print(#t) -- 4 t.foo = 2 print(#t) -- 4 print(t[4]) -- 4 print(t.foo) -- 2 -- continuing for below: t[5]

149. Re: A proposal for the confusing pseudo table ? array concept (score: 16)

Author: "Soni \"They/Them\" L." <fakedme@...>

Date: Fri, 19 Jan 2018 22:58:40 -0200

But wouldn't x.foo = 2 on a sequenced table also cause undefined? I feel like you think the table module is only defined for pure sequences. It's not. It's defined for sequences. That is, tables with

150. Re: A proposal for the confusing pseudo table ? array concept (score: 16)

Author: Elias Hogstvedt <eliashogstvedt@...>

Date: Sat, 20 Jan 2018 01:51:30 +0100

The length of the array should be dynamic and not fixed size. But wouldn't x.foo = 2 on a sequenced table also cause undefined? On Sat, Jan 20, 2018 at 1:39 AM, Advert Slaxxor <adv3r7@gmail.com> wrot

151. Re: [LPeg] How can I signal parsing errors with LPeg? (score: 16)

Author: Sean Conner <sean@...>

Date: Sat, 30 Jul 2016 17:43:44 -0400

It was thus said that the Great Soni L. once stated: Soni, I can't read your mind. You asked about UTF-8. Okay, I presented you with UTF-8. It errors out on invalid UTF-8. If you didn't care about th

152. Re: [ANN] Lift 0.1 looking for early adopters (score: 16)

Author: Hisham <h@...>

Date: Fri, 19 Feb 2016 13:00:22 -0200

Thanks for the explanation and pointers! I can definitely see how this simplifies things and I'm happy to see package management go in this direction. I do however see value in the centralized luaro

153. Re: Lua 5.3 and C++ exceptions (score: 16)

Author: Ahmed Charles <acharles@...>

Date: Fri, 13 Mar 2015 15:07:07 -0700

In my experience, compiling lua as C++ is sufficient to make it exception safe. Exceptions and setjmp/longjmp require the same considerations with regard to cleaning up resources. Besides, this shoul

154. Re: Lua 5.3 and C++ exceptions (score: 16)

Author: Colin Hirsch <lua@...>

Date: Fri, 13 Mar 2015 22:03:05 +0100 (CET)

We have multiple places where 32bit integers are not sufficient, for example time values (think microseconds since 1970), some statistics where 32bits can easily overflow, and some network protocols

155. Re: on the cost of non-blocking LuaSockets (score: 16)

Author: Valerio Schiavoni <valerio.schiavoni@...>

Date: Thu, 18 Dec 2014 11:50:43 +0100

Thanks to everyone for the interesting insights on the thundering herd issue, I surely learned more than expected from this discussion. However, i still have the doubt that there is an inherent perfo

156. Re: on the cost of non-blocking LuaSockets (score: 16)

Author: Sean Conner <sean@...>

Date: Fri, 12 Dec 2014 02:06:58 -0500

It was thus said that the Great William Ahern once stated: Okay, so it avoid the thundering herd problem if you call accept() or read() directly on a socket, but not through select()/poll()/epoll().

157. Re: ## operator (error) (score: 16)

Author: Axel Kittenberger <axkibe@...>

Date: Sun, 23 Nov 2014 13:03:13 +0100

From a human point of view numbers are (have always been) nothing more than strings of digits. Since you said "always",  it certainly was not always a string of decimal digits. There were 12 and 60 b

158. Re: omission in lua_yield docs (score: 16)

Author: John Belmonte <john@...>

Date: Sun, 27 May 2012 09:19:28 -0400

Of course-- thanks. I think it would still be helpful to clarify this in the yield docs, as is done e.g. for lua_error.

159. Re: omission in lua_yield docs (score: 16)

Author: Peng Zhicheng <pengzhicheng1986@...>

Date: Sun, 27 May 2012 11:18:09 +0800

? 2012-5-27 10:40, John Belmonte ??: I noticed that the lua_yield / yieldk docs in 5.1 and 5.2 don't define the return value of the function. (If I understand correctly it's the number of arguments p

160. Yieldable LPEG Parser (score: 16)

Author: William Ahern <william@...>

Date: Tue, 31 Jan 2012 22:01:23 -0800

Below is a _preliminary_ patch to make lpeg yieldable. It Works For Me(tm), but I haven't hammered it yet. Instead of passing a string to lpeg.match, you can pass an object (userdata or table). The o