lua-l archive

Search lua-l

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

361. Re: Lua 5.0 and 5.1 together (score: 1)

Author: John Belmonte <john@...>

Date: Mon, 03 Apr 2006 21:28:59 -0400

Patching Lua to take care of distribution details is not a big deal, we already do it for other things (e.g. patching luaconf.h to add /usr/... variants to search paths). Only one person need do the

362. Re: Lua 5.0 and 5.1 together (score: 1)

Author: John Belmonte <john@...>

Date: Tue, 04 Apr 2006 21:07:15 -0400

I would like to make both versioned and non-versioned variables available (with the versioned having precedence), as I explained. Each has its uses, and I don't see a point in breaking compatibility

363. Re: Lua 5.0 and 5.1 together (score: 1)

Author: John Belmonte <john@...>

Date: Sun, 09 Apr 2006 16:57:33 -0400

Attached is a backwards-compatible patch to check e.g. LUA_5_1_PATH before LUA_PATH when looking up Lua environment variables (LUA_PATH, LUA_CPATH, and LUA_INIT). If the versioned variable exists the

364. Re: Lua is about to become history (score: 1)

Author: John Belmonte <john@...>

Date: Mon, 01 May 2006 22:19:37 -0400

Skimming the paper I didn't notice it mentioned, but you might say something about how the Lua global scope has evolved from a special case with separate meta-mechanisms to yet another use of tables

365. Re: presentation slides (score: 1)

Author: John Belmonte <john@...>

Date: Wed, 06 Sep 2006 06:03:56 -0400

Here are the slides and presentation source for my Exception Patterns in Lua talk. http://memebeam.org/john/lua/exception_patterns.pdf http://memebeam.org/john/lua/exception_patterns.odp

366. Re: Patch to remove auto-casting between numbers and strings (score: 1)

Author: John Belmonte <john@...>

Date: Fri, 08 Sep 2006 21:01:21 -0400

Nice to know that I'm not the only one who dislikes the implicit coercion-- however I don't think the line you mention is that fine. The print function is intended for debugging (e.g. dumping a given

367. JavaScript gets bigger (score: 1)

Author: John Belmonte <john@...>

Date: Thu, 14 Sep 2006 20:07:57 -0400

Since I wasn't able to cause any controversy at the workshop... JavaScript is playing catch-up with Lua. New features from <http://developer.mozilla.org/en/docs/New_in_JavaScript_1.7>: * Generators a

368. Re: class system with token filters (score: 1)

Author: John Belmonte <john@...>

Date: Sat, 16 Sep 2006 09:31:57 -0400

I'd prefer that token filters use the convention of a $ prefix for any added keywords (e.g. $class). Rationale: * makes it clear that the keyword is an extension * avoids clash with identifiers in an

369. Re: luacom and excel (score: 1)

Author: John Belmonte <john@...>

Date: Fri, 22 Sep 2006 07:17:10 -0400

Hi David, Where you able to develop a LuaCOM patch for 5.1 and would you share it? --John

370. Re: destructors (score: 1)

Author: John Belmonte <john@...>

Date: Sat, 23 Sep 2006 12:46:09 -0400

Rici omitted the usage example: a+3 is 4 b+3 is 103 Almost done Closing: another precious resource Closing: some precious resource I think this solution is along the right lines. A good description o

371. Re: Function calls [was: Lua and Neko comparison] (score: 1)

Author: John Belmonte <john@...>

Date: Fri, 29 Sep 2006 07:19:03 -0400

Please understand that there are significant uses of Lua different than your own, such as implementing domain-specific languages. --John

372. Re: 5.2 feature list? (score: 1)

Author: John Belmonte <john@...>

Date: Mon, 02 Oct 2006 07:05:17 -0400

I'd like to see the first implemented by having lua_tostring honor __tostring, and perhaps adding a lua_rawtostring if there is really demand for it. --John

373. Re: 5.2 feature list? (score: 1)

Author: John Belmonte <john@...>

Date: Wed, 04 Oct 2006 07:29:07 -0400

A little searching of the list would avoid rehashing this every year. Mike Pall summed things up well in August 2005 [1]. If you read the Python PEP "Statically Nested Scopes" [2] carefully, you'll f

374. Re: Perl-like strings...? (score: 1)

Author: John Belmonte <john@...>

Date: Mon, 09 Oct 2006 06:52:27 -0400

... or this can be solved without changing Lua. (By the way, I believe Perl also allows function calls and arbitrary expressions inside strings, which you do not address.) http://lua-users.org/wiki/T

375. Re: Wiki Usage (score: 1)

Author: John Belmonte <john@...>

Date: Sat, 14 Oct 2006 08:53:29 -0400

Have you considered: 1) people who have already contributed material in the past 5+ years may not see this after-the-fact agreement (e.g. they are not active in Lua any longer), 2) there is no regist

376. Re: Wiki Usage (score: 1)

Author: John Belmonte <john@...>

Date: Sun, 15 Oct 2006 09:29:34 -0400

... Dealing with cooperative works is tricky business, and serious handling of these matters requires people to sign contracts. Witness the complexity of contributing to GNU projects [1]. If not cont

377. Re: Wiki Usage (score: 1)

Author: John Belmonte <john@...>

Date: Tue, 17 Oct 2006 08:44:18 -0400

For anyone so concerned about reuse (and perhaps attribution) of their work, especially for significant pieces of code, the wiki is not the place to house the authoritative copy. Publish your work an

378. Re: about lposix (score: 1)

Author: John Belmonte <john@...>

Date: Thu, 19 Oct 2006 06:51:40 -0400

Surely the environment would be represented by a Lua table. A thin binding to POSIX (and to whatever equivalent functionality on Windows) is useful. On top of such bindings you can write your cross-p

379. Re: Wiki Usage (score: 1)

Author: John Belmonte <john@...>

Date: Sat, 21 Oct 2006 11:11:31 -0400

My wording was poor. I meant "for any authors truly concerned about giving others the freedom to reuse their work". So what will happen if you post code on the wiki and mark it as "(C) Glenn Maynard"

380. Re: suggestion on error returns, especially in callbacks from C? (score: 1)

Author: John Belmonte <john@...>

Date: Sat, 02 Dec 2006 08:29:45 -0500

The criteria I developed for my Lua workshop presentation on exceptions [1] is to raise an exception when it's unlikely that the immediate caller of the function can handle the error. Exceptions beco