lua-l archive

Search lua-l

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

141. Re: split/join (score: 1)

Author: "John Belmonte" <jvb@...>

Date: Wed, 25 Jul 2001 10:34:41 +0900

"I am aware of the Lua wiki at http://lua.swiki.net/, but decided to set up this one because it requires no login, and hence makes participation easier." Many people share Jean-Claude's view and want

142. Re: Syntactic sugar cravings (score: 1)

Author: "John Belmonte" <jvb@...>

Date: Thu, 26 Jul 2001 12:20:26 +0900

I disagree, in most cases it is a technical concern. Lua is continually being improved. If you're using a distant fork that is not tracking those improvements, then you'll either miss out on the adva

143. [PROPOSAL] lua-users.org (score: 1)

Author: "John Belmonte" <jvb@...>

Date: Thu, 26 Jul 2001 19:59:10 +0900

I'd like to propose the creation of lua-users.org. After some discussion with the Lua authors (mainly lhf) I've written the following "mini charter" which lhf has seen and given an ok. LUA-USERS.ORG

144. Re: [PROPOSAL] lua-users.org (score: 1)

Author: "John Belmonte" <jvb@...>

Date: Fri, 27 Jul 2001 13:05:44 +0900

This is a digest responding to some of the feedback regarding lua-users.org. The reason is to keep a clear separation between the user-run site and the official Lua site. Right, lua-users.org is not

145. Re: Proper tail recursion (score: 1)

Author: "John Belmonte" <jvb@...>

Date: Fri, 27 Jul 2001 19:01:11 +0900

Coroutines are supposed to provide a nice solution to this, although I haven't tried them myself. -John

146. Re: Making Lua lexically scoped (was: Re: Proper tail recursion) (score: 1)

Author: "John Belmonte" <jvb@...>

Date: Fri, 27 Jul 2001 21:55:51 +0900

I don't agree about the "far more" part... if Lua had full lexcial scoping, my existing programs would immediately benefit as I could remove all those ugly manual closures I build with tables. Newcom

147. Re: Making Lua lexically scoped (was: Re: Proper tail recursion) (score: 1)

Author: "John Belmonte" <jvb@...>

Date: Fri, 27 Jul 2001 23:27:51 +0900

I understand Lua programs much better than scoping lingo. Lua upvalues cannot be said to be lexically scoped because the following program prints "5" instead of "10"? do local a = 5 local foo = funct

148. Re: Making Lua lexically scoped (was: Re: Proper tail recursion) (score: 1)

Author: "John Belmonte" <jvb@...>

Date: Mon, 30 Jul 2001 21:31:02 +0900

If you read the Python lexical scoping PEP, it states that the rebinding limitation is due to Python's default local semantics (that is, its lack of variable declarations). It doesn't seem to have be

149. Re: accessing upvalues (score: 1)

Author: "John Belmonte" <jvb@...>

Date: Wed, 1 Aug 2001 11:55:36 +0900

I wrote about this in "pushcclosure / tocfunction issue", 2000-Oct-7. Roberto said he'd consider it for 4.1. I made a 4.0 patch for it which only works for C functions, but can easily be changed to

150. Re: /usr/bin/env and the Lua bytecode format (score: 1)

Author: "John Belmonte" <jvb@...>

Date: Thu, 2 Aug 2001 21:39:22 +0900

Right, another option for John (and superiour in my opinion) is to use binfmt. With the recent release of binfmt-support it's easy to set this stuff up. It's possible to feed environment variables to

151. Re: /usr/bin/env and the Lua bytecode format (score: 1)

Author: "John Belmonte" <jvb@...>

Date: Thu, 2 Aug 2001 23:58:46 +0900

Don't all OS's have to deal with the issue of identifying binary files so the correct viewer or interpreter can be called?

152. Re: /usr/bin/env and the Lua bytecode format (score: 1)

Author: "John Belmonte" <jvb@...>

Date: Fri, 3 Aug 2001 01:18:28 +0900

By doing this, systems that are limited to detecting binary file types by just looking for a magic number at some offset in the file (such as binfmt) can no longer be used. This is breaking one thin

153. Re: Lua's symbol table (score: 1)

Author: "John Belmonte" <jvb@...>

Date: Fri, 3 Aug 2001 14:23:17 +0900

I think references provide what you are looking for. Check section 5.14 in the Lua 4.0 manual. -John

154. Lua-SS (score: 1)

Author: "John Belmonte" <jvb@...>

Date: Mon, 6 Aug 2001 10:55:03 +0900

This is an idea sparked by Erik's reminder about the "lua" program being a sample interpreter. Maybe those interested in Lua as a stand alone scripting language (that is, for system scripting) would

155. Re: Lua-SS (score: 1)

Author: "John Belmonte" <jvb@...>

Date: Wed, 8 Aug 2001 11:41:31 +0900

Just a clarification about my original message... I was thinking more along the lines of a platform-independent interpreter (like Python/Perl are if you limit yourself to use of certain libraries). T

156. lua-users.org status (score: 1)

Author: "John Belmonte" <jvb@...>

Date: Mon, 20 Aug 2001 00:53:17 +0900

Hello, The http://lua-users.org/ site is up, featuring a wiki. For the time being the hosting is provided by SourceForge.net. As far as what the site is now (serving web pages, files and a wiki) Sour

157. Re: getn (score: 1)

Author: "John Belmonte" <jvb@...>

Date: Sat, 25 Aug 2001 13:27:31 +0900

This is not entirely true. The VM deals with lists for the vararg stuff. It doesn't know how to compute n for an arbitrary table however. See http://python.sourceforge.net/peps/pep-0234.html for som

158. Re: Down with Upvalues (score: 1)

Author: "John Belmonte" <jvb@...>

Date: Sat, 1 Sep 2001 13:05:54 +0900

I think there is the ideal, which Roberto already has a handle on, and an optional stepping stone which is this: lexical scoping with read-only access. This is what John Ramsdell already suggested. R

159. Re: Down with Upvalues (score: 1)

Author: "John Belmonte" <jvb@...>

Date: Mon, 3 Sep 2001 10:21:08 +0900

No I think that may be different. The "upvalues" in your modification were still copies of the original variable right? In other words if the original value is changed it won't affect the closure. Th

160. luac output file (score: 1)

Author: "John Belmonte" <jvb@...>

Date: Tue, 4 Sep 2001 18:58:18 +0900

The 4.0 luac output on my embedded platform has never been correct (3.2 was ok). After investigation I found that luac doesn't close the output file. I know that it's perfectly within ANSI C to do th