You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 7, 2020. It is now read-only.
Right now, core is functioning as a library that an application (like standalone) wraps around. Since this is the case, core should not call exit() unless there's an unrecoverable error (like memory allocation failure), which means that destroyGame() should not call exit(). Should alter the main game loop in standalone/main.c so that it says something like:
while (inGame()) {
...
}
And then implement inGame() so that it returns TRUE if the game is running and FALSE if the game has ended. Then, initGame() will set the variable this function returns to TRUE and destroyGame(), when we're done tearing down, will set this value to FALSE.
DO EET!
The text was updated successfully, but these errors were encountered:
Right now, core is functioning as a library that an application (like standalone) wraps around. Since this is the case, core should not call exit() unless there's an unrecoverable error (like memory allocation failure), which means that destroyGame() should not call exit(). Should alter the main game loop in standalone/main.c so that it says something like:
while (inGame()) {
...
}
And then implement inGame() so that it returns TRUE if the game is running and FALSE if the game has ended. Then, initGame() will set the variable this function returns to TRUE and destroyGame(), when we're done tearing down, will set this value to FALSE.
DO EET!
The text was updated successfully, but these errors were encountered: