Coroutines in gideros 2016.06

test29 · July 2016

If I have coroutine in one scene and after that scene is restarted, new coroutine call is added on each restart of scene to the existing one (something like timers), so after second restart I have two coroutines running, after third restart, three coroutines running, etc... Is this a case or something else is wrong in my code?

Is there I way to stop coroutine from executing?

SinisterSoft · July 2016

A coroutine will stop executing when it runs out of code to run.

test29 · July 2016

I have loop in my coroutine, that doesn't stop when the scene is ended (scene is ended by event rising). When that scene is restarted, logic of scene is behaving like there are more than one loop (more than one coroutine) is running. When scene is starting for the first time everything is working OK, problem is only when it is restarted.

SinisterSoft · July 2016

Have a global flag in the loop, change the flag to exit the loop.

test29 · July 2016

I know that I can make it work that way, but in my case it wont work, because in my coroutine I have many calls to different functions (and every function that is called from coroutine, behave itself like coroutine), and it seems that somehow coroutine remains active. So after every scene restart new coroutine is added while older are still active.

Is there a way to forcefully stop coroutine, something like 'StopCoroutine' in c#?

SinisterSoft · July 2016

So if you call a function in a co-routine, it starts a new co-routine for you? That doesn't sound right.

test29 · July 2016

No, if you call function in a coroutine, called function behaves like coroutine, you can use core.yield in it.

hgy29 · July 2016

@test29,

I understand what you need, when I coded corotuine based threads I didn't see the need of having a function to kill them because in most languages this is a bad thing to do.
However in lua and its GC, this is something possible and not that bad after all. So probably we'll add it soon.

test29 · July 2016

Thank you, that would be great. Also it would be usefull if it could be tested that coroutine is active or not.

SinisterSoft · July 2016

@test29 A function called by a coroutine doesn't start a new coroutine. It's still part of the original coroutine. When it returns then the coroutine will carry on until the end and then exit.

eg:

function test2()
	while true do
		print("only this will print")
	end
end
 
function test1()
	test2()
	while true do
		print("does this ever print?")
	end
end
 
Core.asyncCall(test1)

Howdy, Stranger!

Categories

In this Discussion

Top Posters

Coroutines in gideros 2016.06

Comments

Howdy, Stranger!

Quick Links

Categories

In this Discussion

Top Posters

Coroutines in gideros 2016.06

Comments