Re: [wxlua-users] recursive calls runbuffer

2014-04-03 Thread John Labenski
On Wed, Apr 2, 2014 at 3:35 AM, klaas.holwerda wrote: > Hi John, > > Indeed if out commented, it works okay again. > So recursive calls is not the problem it seems, only the assert. > Don't know if the m_is_running is very important, but if yes or just handy > to have, i think the up/down counte

Re: [wxlua-users] recursive calls runbuffer

2014-04-01 Thread klaas.holwerda
Hi John, Indeed if out commented, it works okay again. So recursive calls is not the problem it seems, only the assert. Don't know if the m_is_running is very important, but if yes or just handy to have, i think the up/down counter would deal with the situation. Regards, Klaas On 04/02/2014

Re: [wxlua-users] recursive calls runbuffer

2014-04-01 Thread John Labenski
On Sun, Mar 30, 2014 at 7:11 PM, klaas.holwerda wrote: > Hi, > > Recursive calls to RunBuffer() is a problem, gives an assert. > > int wxLuaState::RunBuffer(const char buf[], size_t size, const wxString > &name, int nresults) > { > wxCHECK_MSG(Ok(), LUA_ERRRUN, wxT("Invalid wxLuaState")); >

[wxlua-users] recursive calls runbuffer

2014-03-30 Thread klaas.holwerda
Hi, Recursive calls to RunBuffer() is a problem, gives an assert. int wxLuaState::RunBuffer(const char buf[], size_t size, const wxString &name, int nresults) { wxCHECK_MSG(Ok(), LUA_ERRRUN, wxT("Invalid wxLuaState")); wxCHECK_MSG(!M_WXLSTATEDATA->m_wxlStateData->m_is_running, LUA_ERRR