[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: lua_yield behaviour
- From: "Dan Partelly" <dan_partelly@...>
- Date: Wed, 7 Aug 2002 18:36:07 +0300
Please , what is the exact behavoiur in the next scenario:
A Lua script calls an external C function. This function schedules for
execution a
stack of actions, and imediately calls lua_yield() to stop the script from
running further.
Where exactly will LUA VM stop in this scenario ? (Execution of script will
be resumed
when a ListenerObject will be signaled upon the stack of actions is empty.)
Thx , Dan
----- Original Message -----
From: "Zimmermann, Maik" <Zimmermann@4d-Vision.de>
To: "Multiple recipients of list" <lua-l@tecgraf.puc-rio.br>
Sent: Wednesday, August 07, 2002 5:57 PM
Subject: Re: problem with lua_resume/lua_lock
> > So, your macros should be like
> >
> > #define LUA_USERSTATE CRITICAL_SECTION *cs;
>
> Many thanks for your answer.
> I will change my code according to your suggestion.
>
> regards
> Maik
>