Re: C++, pcall, and yield

[roberto@... (Roberto Ierusalimschy)]

> But then Lua can't restore its own state. See the (status != 0)
> cases in LuaD_pcall or lua_resume. So a catch(...) may be ugly,
> but at least it doesn't screw up the Lua state (with the
> LUA_ERREXC bug fix of course).
> 
> BTW to Roberto: I assume the LUA_ERREXC bug fix will be part of
> Lua 5.1.1-rc1?

The bug is only in 'luaD_seterrorobj', that increments top without
pushing a corresponding value, is that right?

-- Roberto