Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Various Bugfixes #64

Merged
merged 4 commits into from
Nov 5, 2023
Merged

Various Bugfixes #64

merged 4 commits into from
Nov 5, 2023

Conversation

ptomato
Copy link
Member

@ptomato ptomato commented Oct 30, 2023

  • Documentation fix
  • Unit test runner improvement
  • Fix for not emitting start and stop notifications when Unix startup code fails
  • Fix for freeing Glk program args too early

The resource usage constants are Snd, Exec, Pict, and Data. The others are
chunk type constants.
Tests probably work fine without it but it's good to have it.
We would not run glk_main() but exit the Glk thread immediately if
glkunix_startup_code() returns FALSE, signifying failure. However, in this
situation, neither the ::started nor ::stopped signals would be emitted.
We need to emit at least ::stopped, because programs may be relying on it
to know when to call gtk_main_quit(). And if we emit ::stopped, we should
emit ::started before it.
Previously we would free the startup argument strings right after
executing the Unix startup function in the Glk program. However, the Glk
program may hold on to these strings; Glulxe does, for one. Move them to
the ChimaraGlkPrivate data structure to ensure they last for the lifetime
of the Glk program.
@ptomato ptomato merged commit 04ff30a into main Nov 5, 2023
4 checks passed
@ptomato ptomato deleted the bugfixes branch November 5, 2023 20:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant