lua-l archive

Search lua-l

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

281. Re: [ANN] lua-icxx v1.01 (score: 2)

Author: oliver <oliver.schoenborn@...>

Date: Thu, 28 Jul 2011 12:22:07 -0400

Hi Patrick, I started working on this last fall (2010), and only recently decided to publicize it. Thanks for pointing out your project, always good to see alternative ways of doing things.  when you

282. Re: [ANN] Lua 5.2.0 (beta-rc1) now available (score: 2)

Author: David Manura <dm.lua@...>

Date: Tue, 14 Jun 2011 01:04:09 -0400

ooo When a single goto exists inside a conditional block, some of the JMP's are superfluous: local x = 1 @a: if x > 1e8 then goto e end x = x + 1 goto a @e: -- equivalent local x = 1 while not(x > 1e

283. Re: Difficulties with LuaRocks (score: 2)

Author: Jim Whitehead II <jnwhiteh@...>

Date: Mon, 13 Jun 2011 17:17:58 +0100

Indeed, and it solves the problem that Javier seems to be concerned with, as I've just responded in the other thread. - Jim

284. Difficulties with LuaRocks (score: 2)

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

Date: Mon, 13 Jun 2011 18:15:34 +0200

(quick new topic fork) That used to be the case, but since LR 2.0 modules are deployed on the usual Lua module path, at least if installed as superuser. It has really become quite painless, especiall

285. Lua JSON module dkjson 2.0 (score: 2)

Author: David Kolf <kolf@...>

Date: Mon, 30 May 2011 21:30:18 +0200

I have released version 2.0 of my JSON module. <http://www-users.rwth-aachen.de/David.Kolf/json-lua> dkjson aims to be a strict implementation of the JSON standard, using the original JavaScript impl

286. Re: Sandboxing in Lua 5.2 (score: 33)

Author: Lorenzo Donati <lorenzodonatibz@...>

Date: Sat, 07 May 2011 18:47:18 +0200

On 07/05/2011 14.45, Peter Cawley wrote: On Sat, May 7, 2011 at 1:41 PM, Roberto Ierusalimschy <roberto@inf.puc-rio.br> wrote: loadin(env, io.lines(file, "*L"), path) Is it mandated by the reference

287. Re: Sandboxing in Lua 5.2 (score: 33)

Author: Roberto Ierusalimschy <roberto@...>

Date: Sat, 7 May 2011 12:49:45 -0300

http://www.lua.org/manual/5.1/manual.html#pdf-file:lines file:lines () Returns an iterator function that, each time it is called, returns a new line from the file. -- Roberto

288. Re: Sandboxing in Lua 5.2 (score: 33)

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

Date: Sat, 7 May 2011 14:55:03 +0200

It appears not, since LuaJIT does not follow this pattern for io.lines: function: fast#118 file (0x68ea1650) steve d.

289. Re: Sandboxing in Lua 5.2 (score: 33)

Author: Peter Cawley <lua@...>

Date: Sat, 7 May 2011 13:45:35 +0100

Is it mandated by the reference manual that all implementations of Lua must return a single function rather than an iterator tuple for things like io.lines, string.gmatch, etc?

290. Re: Sandboxing in Lua 5.2 (score: 33)

Author: Roberto Ierusalimschy <roberto@...>

Date: Sat, 7 May 2011 09:41:51 -0300

You mean this? loadin(env, io.lines(file, "*L"), path) -- Roberto

291. Re: Sandboxing in Lua 5.2 (score: 34)

Author: Renato Maia <maia@...>

Date: Sat, 7 May 2011 09:03:21 -0300

local env = { foo = foo; bar = bar } local path = "users_code.lua" local loader = assert(io.open(path)):lines() local chunk = assert(loadin(env, loader, path)) local ok, result = assert(xpcall(chunk,

292. Sandboxing in Lua 5.2 (score: 35)

Author: Alexander Gladysh <agladysh@...>

Date: Sat, 7 May 2011 12:21:51 +0400

Hi, list! I apologize for being lazy, but can someone please summarize for me, how environment sandboxing is to be done in 5.2? (I assume that nothing is changed for CPU and memory sandboxing.) In my

293. Re: executing functions from file, without using luaL_dofile (score: 2)

Author: HyperHacker <hyperhacker@...>

Date: Sun, 1 May 2011 16:31:42 -0600

In Lua, writing "function foo() ... end" is really a shortcut for "foo = function() ... end". Just like any other variable assignment, that won't do anything until the statement actually gets execute

294. Re: advice needed: OO style (score: 2)

Author: Emmanuel Oga <emmanueloga@...>

Date: Wed, 27 Apr 2011 21:31:44 -0300

IMO there is just too much overhead in using a proxy "just in case the user modifies the values". It is different if you __need__ that proxy to implement before/after callbacks for __every__ function

295. Re: advice needed: OO style (score: 2)

Author: Lorenzo Donati <lorenzodonatibz@...>

Date: Wed, 27 Apr 2011 23:50:06 +0200

On 27/04/2011 21.55, Javier Guerra Giraldez wrote: On Wed, Apr 27, 2011 at 2:29 PM, Lorenzo Donati <lorenzodonatibz@interfree.it> wrote: - the actual object is stored in the proxy table using a "priv

296. Re: LuaJIT FFI __gc metamethod? (score: 2)

Author: Josh Haberman <jhaberman@...>

Date: Tue, 1 Mar 2011 00:39:43 +0000 (UTC)

Isn't every JavaScript enabled web browser in the world an example of such a sealed sandbox? It's not to say that sandboxes never have bugs (even process isolation can have bugs), but I don't think i

297. Re: LuaJIT FFI __gc metamethod? (score: 2)

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

Date: Mon, 28 Feb 2011 22:45:33 +0100

No, it applies to Lua in general. The advice in that page is incomplete and outright dangerous. E.g. string.find() can lock up your CPU and, nope, setting a hook won't help here: string.find(string.r

298. Re: LuaJIT FFI __gc metamethod? (score: 4)

Author: Josh Haberman <jhaberman@...>

Date: Mon, 28 Feb 2011 21:23:15 +0000 (UTC)

What you are saying applies only to FFI, right? Without FFI, can't either Lua or LuaJIT be very tightly sandboxed in-process with an approach like this? http://lua-users.org/wiki/SandBoxes This might

299. Re: LuaJIT FFI __gc metamethod? (score: 2)

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

Date: Mon, 28 Feb 2011 20:38:03 +0100

Well, why do you mistrust the users of your code? Document the public API and deny support if they use any undocumented parts. If you can't trust your fellow developers, then none of this protected/p

300. Re: Improved functions sandboxing in Lua and LuaJIT2 (score: 33)

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

Date: Mon, 21 Feb 2011 12:07:33 +0100

http://lua-users.org/lists/lua-l/2006-06/msg00133.html You can call error() from debug hooks. But debug hooks are not called from compiled code. There is an undocumented compile option LUAJIT_ENABLE_