Elysian Shadows

This is at the moment a theoretical for me, but I remember in an AiGD Falco said something about having a continuous script running through the game with its only infinite loop. My question is, was this achieved with co-routines or is there a need for a sneaky alternative

it was done with co-routines. At the end of every iteration in the loop (in the script) it calls a yield function which returns control back to the C++ side of things.

M_D_K wrote:it was done with co-routines. At the end of every iteration in the loop (in the script) it calls a yield function which returns control back to the C++ side of things.

^ HOW DO YOU KNOW THIS!?

owait...

I don't recommend that approach, though. That stuff was way back when I was first learning Lua. Simply load a script with luaL_dofile() and manually invoke an update() function within the script from your C/++ main loop (as you would any normal function). There's no need to use coroutines.

that's cool But doesn't that mean no globals for scripts? or is that a good thing as its more OO?

sk1v3r wrote:that's cool But doesn't that mean no globals for scripts? or is that a good thing as its more OO?

Nope. Any variable you declare without explicitly using the "local" keyword is global. And any global logic (outside of a function) executes once upon loading of the script (for initialization/consruction, etc).

I meant like persisting globals between scripts, or is that what you were saying ?

sk1v3r wrote:I meant like persisting globals between scripts, or is that what you were saying ?

It was a matter of "persisting globals between INVOKATION of a single script" that was the issue addressed by that Adventures in Game Development video. To share globals between actual scripts (lua_States), you'd have to push and pop them into each other...

okay, thanks

GyroVorbis wrote:

sk1v3r wrote:I meant like persisting globals between scripts, or is that what you were saying ?

It was a matter of "persisting globals between INVOKATION of a single script" that was the issue addressed by that Adventures in Game Development video. To share globals between actual scripts (lua_States), you'd have to push and pop them into each other...

Invokation Edukation?

dandymcgee wrote:

GyroVorbis wrote:

sk1v3r wrote:I meant like persisting globals between scripts, or is that what you were saying ?

It was a matter of "persisting globals between INVOKATION of a single script" that was the issue addressed by that Adventures in Game Development video. To share globals between actual scripts (lua_States), you'd have to push and pop them into each other...

Invokation Edukation?

Already planned. That's nothing. We planned to show our entire implementation, which is 1000x deeper than our old, shitty "heartbeat" implementation previously.

GyroVorbis wrote:

dandymcgee wrote:

GyroVorbis wrote:

sk1v3r wrote:I meant like persisting globals between scripts, or is that what you were saying ?

It was a matter of "persisting globals between INVOKATION of a single script" that was the issue addressed by that Adventures in Game Development video. To share globals between actual scripts (lua_States), you'd have to push and pop them into each other...

Invokation Edukation?

Already planned. That's nothing. We planned to show our entire implementation, which is 1000x deeper than our old, shitty "heartbeat" implementation previously.

I'm all ways 1 step behind

N64vSNES wrote:

GyroVorbis wrote:

dandymcgee wrote:

GyroVorbis wrote:

sk1v3r wrote:I meant like persisting globals between scripts, or is that what you were saying ?

It was a matter of "persisting globals between INVOKATION of a single script" that was the issue addressed by that Adventures in Game Development video. To share globals between actual scripts (lua_States), you'd have to push and pop them into each other...

Invokation Edukation?

Already planned. That's nothing. We planned to show our entire implementation, which is 1000x deeper than our old, shitty "heartbeat" implementation previously.

I'm all ways 1 step behind

No ES is just one step ahead... maybe you should try researching other things? which reminds me... I have to research ruby as a scripting language....

GyroVorbis wrote:

dandymcgee wrote:

GyroVorbis wrote:

sk1v3r wrote:I meant like persisting globals between scripts, or is that what you were saying ?

It was a matter of "persisting globals between INVOKATION of a single script" that was the issue addressed by that Adventures in Game Development video. To share globals between actual scripts (lua_States), you'd have to push and pop them into each other...

Invokation Edukation?

Already planned. That's nothing. We planned to show our entire implementation, which is 1000x deeper than our old, shitty "heartbeat" implementation previously.

Actually I was just being a smart ass and making fun of the spelling, but that works too.

eatcomics wrote:

N64vSNES wrote:

GyroVorbis wrote:

dandymcgee wrote:

GyroVorbis wrote:

sk1v3r wrote:I meant like persisting globals between scripts, or is that what you were saying ?

It was a matter of "persisting globals between INVOKATION of a single script" that was the issue addressed by that Adventures in Game Development video. To share globals between actual scripts (lua_States), you'd have to push and pop them into each other...

Invokation Edukation?

Already planned. That's nothing. We planned to show our entire implementation, which is 1000x deeper than our old, shitty "heartbeat" implementation previously.

I'm all ways 1 step behind

No ES is just one step ahead... maybe you should try researching other things? which reminds me... I have to research ruby as a scripting language....

Don't bother. Unless you wish to embed one of the heaviest-weight, slowest scripting languages around.

Ruby is great, but it is NOT great as an embedded, real-time scripting language.

Ah, I see. I always liked Ruby... So I figured I might look into using it with my engine, but I believe the words you are speaking.