lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

On Tue, Sep 13, 2011 at 8:53 AM, Graham Wakefield <> wrote:
Exactly. Start your script with lua_resume() rather than lua_call().

On Sep 12, 2011, at 1:36 PM, Wesley Smith wrote:

>> I know it is not that hard to add a "scheduler:run()" at the end of a main
>> script, but I would like the main thread to give up control before reaching
>> the end of the script:
> If you run the entire script as the body of a coroutine, it can yield
> at any point.
> wes

This is a good idea if you run a custom executable, which I don't (I want to use plain Lua).
Technically, what I want to do doesn't seem impossible (it's some kind of resumable goto)
and it would enable to completely hide the scheduling stuff. For example, I wrap
coroutine.yield(timeout) as "sleep(timeout)" which is very easy to grok and it worked fine
as long as I used real OS threads. If you do the same with coroutines you get errors. For
a total beginner, code "A" and "B" are the same, but "B" has some boilerplate code that
I would *love* to hide:

-- ========== A
sleep(500)  -- error

-- ========== B
  sleep(500)  -- ok


If there is no solution apart from altering the bytecode (a job for Peter Cawley...),
I can live with "B".