News for hackers. Stuff that matters.
Re:In praise of Go or "Why I moved from Python and C++ to Go" by codexon on Wednesday November 17, 2010 @02:14AM (#1913270)
LuaJIT has a memory limit of 4gb. When it is compiled for x64, it has a limit of 1gb. You cannot use Lua lanes to bypass this, the Lua states must be in different processes.

http://lua-users.org/lists/lua-l/2010-11/msg00241.html

The lack of try/catch is also a nuisance.

Re:In praise of Go or "Why I moved from Python and C++ to Go" by silentbicycle on Wednesday November 17, 2010 @09:57AM (#1914400)
Lua has try/catch-like functionality, it's just called pcall ("protected call"), or xpcall (http://www.lua.org/manual/5.1/manual.html#pdf-xpcall) if you want to run a callback before the stack unwinds. Running debug.debug inside xpcall's handler will drop into a shell on error, which is particularly handy.

error("error tag") is comparable to raising an exception.

I wasn't aware of LuaJIT's 1gb limit, but it's neither hard nor unusual to run several Lua states in multiple worker processes.