Elysian Shadows

Okay, I'm going through Lazy Foo's Tutorials, and in all of his tutorials he has this when he's handling events:
My question: Is that really necessary? When the application is closed, wouldn't it stop running?

In general, you want to manually clean things up. So if the user clicks "exit", you set quit to true and let it fall through so you can call SDL_Quit, etc. This way you can tell the difference between a clean exit and a not-clean exit.

MarauderIIC wrote:In general, you want to manually clean things up. So if the user clicks "exit", you set quit to true and let it fall through so you can call SDL_Quit, etc. This way you can tell the difference between a clean exit and a not-clean exit.

Oh. That makes complete sense now that you say it haha.

a somewhat easier thing to do this (no need to have an extra variable) would be: just as a thought

Yeah, that'd work well too

Ginto8 wrote:a somewhat easier thing to do this (no need to have an extra variable) would be:

Code: Select all

while(1)
{
    if([user quits])
        break;
}

just as a thought :)

This breaks structured programming rules (one entry, one exit), which you shouldn't just break all willy-nilly, but are rules that I regard as more breakable than other rules. Besides, [user quits] -- if that's not a variable somehow, why not just have while (![user quits]) ?