[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: nCcalls in the global state keeps increasing in 5.2
- From: Roberto Ierusalimschy <roberto@...>
- Date: Sat, 6 Aug 2011 16:27:10 -0300
> Please consider moving nCcalls back into lua_State. I think the only
> way for me to continue using 5.2 right now is to disable the checking
> of the nCcalls variable.
Note that the change was the result of a bug in Lua 5.1:
http://www.lua.org/bugs.html#5.1.2-4
The way the bug was fixed in 5.1.3 was an ugly hack (with a new function
in the API 'lua_setlevel' that has no reasonable documentation). I do not
think that would be a good choice for 5.2.
As you are already using a non-standard Lua compilation, maybe you can
simply change the limit LUAI_MAXCCALLS in luaconf.h to a much higher
value.
-- Roberto
- References:
- nCcalls in the global state keeps increasing in 5.2, Markus Schmid
- Re: nCcalls in the global state keeps increasing in 5.2, Roberto Ierusalimschy
- Re: nCcalls in the global state keeps increasing in 5.2, Markus Schmid
- Re: nCcalls in the global state keeps increasing in 5.2, Roberto Ierusalimschy
- Re: nCcalls in the global state keeps increasing in 5.2, Markus Schmid
- Re: nCcalls in the global state keeps increasing in 5.2, Roberto Ierusalimschy
- Re: nCcalls in the global state keeps increasing in 5.2, Markus Schmid
- Re: nCcalls in the global state keeps increasing in 5.2, Roberto Ierusalimschy
- Re: nCcalls in the global state keeps increasing in 5.2, Markus Schmid
- Re: nCcalls in the global state keeps increasing in 5.2, Markus Willhelm Schmid